Resolve the ultimate solution for a server-shared file that cannot be accessed

Method One

I think it is because of the XP Network Neighborhood access problem, XP's online neighborhood there are many passable places: slow access, unable to access other hosts ... In fact, these problems through simple settings can be well resolved.

Make sure you can ping each other before that. (Open Group Policy Editor: Start-run-gpedit.msc)

1. Open Guest account.

2. Allow guest users to access this computer: Open the Group Policy Editor, select "Computer Configuration →windows settings → security settings → local policy → user Rights Assignment", and delete the "GUEST" account in the "Deny access to this machine from the network" policy.

3. Change network access mode: Open the Group Policy Editor, select "Computer Configuration →windows settings → security settings → local policy → security options", double-click the "Network access: Sharing and security mode for local accounts" policy, change "Guest only-local users authenticate to guest" to " Classic: Local users authenticate as themselves.

4. Null password limit: Disable "account: Local account with blank password only allow console login" policy in System "security options".

5. Network neighbors do not see the computer: Open "Control Panel → performance and maintenance → management tools → services", the launch of the "Computer Browser" service.

6. Add permissions to share files options: Turn on the "My Computer → tools → folder properties → view → advanced settings", the "Simple File Sharing (recommended)" option before the cancellation, if there are "Mickey Mouse" items will also be canceled.

7. Network neighbors do not respond or react slowly, turn off the WinXP Scheduled task Service (task Scheduler) to open the Task Scheduler Properties dialog box in Control Panel/Administrative Tools/services, stop the service, and then set the startup type to Manual.

8. You need to add "NWLink Ipx/spx/netbios Protocol", and then windows with the firewall shut down, you can share files. (Open Network Connections, right-click the local area Connection, and then click Properties.) Click Install, select the protocol by adding, select "NWLink ipx/spx/netbios compitable Transport Protocol", and install it as determined. Windows has its own ipx/spx driver and does not need to find another program, except that ipx/spx is not the default protocol to install manually. )

Turn off the Web folders and printers that are automatically searched, and in My Network Places/File/Folder Options, click the last one to turn off the Web folders and printers that are automatically searched.

Method Two

Access to the Internet is definitely an intranet problem.

1 off Firewall

2 Open Guese Account

3 Enter the system with the same password as the same user

4 in Group Policy (run Gpedit.msc)-Computer Configuration-windows Settings-Local policy-User rights assignment-deny access to this computer from the network, and then delete all users inside

5 Set share permissions add everyone user

6 If the system's file format is NTFS and you want to set open permissions in a security entry, add everyone

There's a trick if you don't find security one can click on the folder menu Tools-Folder Selection---View-use a simple share of the itch surface to remove the hook to see and shared security one is the same as 2000 clear

7 Look at the TCP/IP NetBEUI protocol Ah, sharing service Ah, did you put it up?

8 There's a situation where you can't find it at first, but you can.

A way to run a computer name or IP to see if you can access

After a visit, you can see it in your online neighborhood.

Method Three

Discover that the local Area network share folder that the computer company made for it cannot be accessed, prompting the system: "You may not have permission to use network resources." Please contact the administrator of this server to find out ... "

Because originally in the unit local area network has also encountered this problem, just because of the time relationship, did not deep research, explore solutions. Considering that the Internet café users may use this function, so decided to solve the problem.

By the hint, it is obvious that the issue of permissions, the original 98 share without this problem, as long as the IP address and shared folder, can immediately access, and once encountered XP and 2003, this problem has repeatedly appeared, obviously with XP and 2003 security considerations.

The file share is related to the following settings, so I checked the following settings for the computer:

(1) NWlink Ipx/spx/netbios Compatible Transport Protocol protocol. This agreement has been installed and there is no problem.

(2) Open the Guest account: Right click My Computer Management user has a guest, double click to remove the "account has been deactivated" before the tick. This setting was not initially turned on and I turned it on.

(3) Unified computer workgroup name: Right-click My Computer name, view the name of the LAN workgroup that appears in the tab, and add all computers to the workgroup workgroup.

(4) Exceptions to the use of the WinXP Firewall: The WinXP Firewall is fully enabled by default, which means that all network connections to the computer are difficult to share. Also, because Windows Firewall defaults to "File to Printer Sharing", therefore, the firewall is enabled, often can not share printing, the solution is: go to the Local Area Connection window, click the "Advanced" "" "Exceptions" in the program and services to check "file and Printer sharing." Because the Internet Café computer uses a restore card, so I simply shut down the firewall.

(5) Delete the Guest account in the "Deny access to this computer from the network" item: Run Group Policy (gpedit.msc) Local computer Computer Configuration Windows settings security settings Local Policy user rights assignment denies access to this computer from the network. If there is guest, delete it. This is done to make it possible for guest to access the local computer from the network.

(6) Remove the "Use Simple File Sharing" method: Explorer Tools Folder Options View Remove the check before using simple File sharing (recommended).

(7) Check "File and Printer Sharing for Microsoft Networks".

(8) Run the service strategy "Services.msc". Start the "Clipbook Server" (folder servers): This service allows other users on your network to see your folders. I set this service directly to automatically start automatically.

(9) The Win98 computer cannot access the WIN2000/WINXP computer because the guest user on the WIN2000/WINXP computer is disabled or the WIN2000/WINXP is formatted with the NTFS partition to set permissions control. Generally to allow Win98 access, WIN2000/WINXP in the security controls do not remove everyone's account group.

Attention:

A, if you are not joined to the domain and you want to view the Security tab, the settings Display the Security tab: Explorer Tools Folder Options View Remove the tick before using simple file sharing (recommended).

b, to view valid permissions for files and folders: Explorer Right click to view valid permissions the file or folder properties click the Security tab, advanced effective permissions, select the name of the user or group in the Name box, and then click OK. A selected check box indicates the user or group has valid permissions to the file or folder.

C, you can only set permissions on drives formatted to use NTFS.

(10) Ways to solve the online neighborhood too slow: win98, assuming that there is no Novell network in the network, you can delete the Ipx/spx compatibility protocol installed for the Novell NetWare network; win2000/xp, delete system letter documents and Setting all files under the user name NetHood folder.

As a friend of Internet cafes in the future using XP system, so the latter two I do not care about it, need 98 system access to the shared folder friends may need to check the settings.

All of the above settings are checked, I found that access to the shared folder is still the original phenomenon, there is no improvement. What is the cause of this problem? The above method of setting up, many articles are addressed, it seems that there should be no problem. But since the problem remains, it means that there is still room for adjustment, and that is what we are ignoring.

So I checked the system services and security policies carefully.

When I select "Computer Configuration-→windows Settings-→ security Settings-→ Local policy-→ security options", the unit policy is found to have a "network access: local account sharing and security mode" policy, which is set by default to guest only-local users authenticate as guest. Another optional setting for it is "classic: Local Users authenticate themselves", which is suspected to be related to this setting, so this setting is modified.

The problem was not resolved when the test was re tested. To do here, I have been at my wits ' turn, so had to turn to the Internet, but find to find, most of the statements and the above set a number of lines coincide, and there is not much new things. Do you just give up? I really hate to throw in the towel.

As I still hold a gleam of hope in the online search, finally see the following paragraph of text:

However, we may also encounter another problem, when the user's password is empty, access will still be rejected. There was an account in security options: A local account with a blank password allows only console logon policy, which is enabled by default, and is prohibited when a user with a blank password accesses a computer using Windows XP over the network, based on the principle of denial of priority in Windows XP security policy. We can solve the problem by simply deactivating this policy.

It turns out so, no wonder my family XP access to 2003 shared folders must be accessed using a 2003 account password, and an account with XP itself prompts no access. According to this article, if the XP account has a password, then there is no problem with the password. In this case, I immediately found this strategy in Group Policy, it is hired, needless to say, disable it. Try again, the shared folder access is normal and fast.

conclusion, the problem of shared folder access is a common network failure, but everyone is not perfect about its correction, ignoring the "account: a local account with a blank password allows only the console to log on" policy. Naturally, this problem has not been solved completely. The reason is that it is not understood that "password-empty users will be banned from accessing Windows XP computers over the network." This is the setup for security considerations for the above XP system. This tells us that the usual study work must be in-depth and meticulous, so as not to ignore some of the details of the problem and make themselves trapped.