Solutions for inaccessible network peers under WINXP

In the Windows XP system, network neighbors are not accessible. I believe many people have encountered such problems. I have used some cases for test analysis and found some information on the Internet, we have tested various common solutions provided on the Internet. Now let's sort them out and introduce them. the main phenomena are:
1. Unable to open the workgroup
2. Unable to open the computer
3. Prompt to enter the Guest user password (do not log on from the Network)
4. Prompt that the user has no permission
5. The computer is invisible to the Working Group.
6. Sharing cannot be set (the check box is gray)
Windows XP is installed by default. When there is a problem with sharing and access, consider the following steps:
1. Check whether the Guest account is enabled.
XP does not enable the Guest account by default. Therefore, enable the Guest account to allow others to browse your computer. To ensure security, set a password or corresponding permissions for guest.
2. Check whether the Guest user is denied access to the local machine from the network.
When you enable the Guest account but still cannot access it at all, check whether it is set to deny access to the computer from the guest network, because XP does not allow access from the network by default, therefore, even if guest is enabled, it cannot be accessed. When the system Guest user is enabled, remove the restrictions on the Guest account. Click "Start> Run" and enter "gpedit" in the "run" dialog box. MSC, open the Group Policy Editor, select Computer Configuration> Windows Settings> Security Settings> Local Policy> User Rights Assignment, and double-click the Deny access to this computer from the network policy, delete the "guest" account. In this way, other users can use the Guest account to access computers using Windows XP through the network.
3. Change the network access mode (optional steps, and 1 or 2 items may not be used at the same time ).
By default, Windows XP processes all users logged on from the network according to the Guest account. Therefore, even if the Administrator logs on from the network, the Administrator only has the guest permission, try to change the network access mode. Open the Group Policy Editor, select "Computer Configuration> Windows Settings> Security Settings> Local Policies> Security Options", and double-click the "Network Access: sharing and security modes of Local Accounts" policy, change "guest-Local User-initiated identity verification" to "classic: Local User Authentication" by default ".
In this way, even if you do not enable Guest, you can enter your local account and password to log on to the computer you want to access, the local account and password are your accounts and passwords in the computer you want to access. If you need an account and password to access the network, you can log on by entering the account and password in the computer you want to access.
If you do not change the access mode, you may not be able to enter the user name and password, // computername/guest is unavailable. Even if the password is empty, you cannot click confirm to log on without enabling guest. In Classic mode, you can enter the user name and password to log on to the computer, just as in the case that the Guest account is not enabled in section 2000.
4. Check whether the firewall is enabled.
By default, Windows Firewall (SP2) does not open the port used for file and printer sharing. Disable Windows Firewall or select file and printer sharing on the "exceptions" tab of firewall settings ". If the actual software firewall is installed, make sure that the firewall does not prohibit the following ports: UDP: 137,138, TCP: 139,445 (137/UDP-NetBIOS name server, 138/UDP-NetBIOS datagram, 139/TCP-NetBIOS Session Service)
You may encounter some special situations. Please refer to the following.
5. A noteworthy question.
We may also encounter another problem, that is, when the user's password is empty, the access will be rejected even if you have made all the above changes and still cannot log on. This is because the policy "Account: A local account with a blank password can only log on to the console" in the system "Security Options" is enabled by default, according to the Denial-of-priority principle in Windows XP security policy, users with blank passwords are prohibited from accessing Windows XP computers over the network. We only need to disable this policy to solve the problem. In the security options, find the "allow console logon only for a local account with a blank password" option and disable it. Of course, you can also set a password for guest. otherwise, you cannot log on even if you have enabled guest and changed it to the classic mode.

After the above changes, you can access them. You can try to select a method that suits you. Next we will add some other problems that may occur.
1. You may not be able to find the Working Group or computer (under Win2k) when starting the instance. Please try again in a few minutes.
2. You can see the shared folder but cannot access it. Please restart the server service.
3. Check whether the following services are enabled:
Computer Browser Service
Workstation Service
Server Service (unable to browse Working Group when not started)
TCP/IP NetBIOS Helper Service
Check whether the following protocols/clients are installed and enabled:
Microsoft network file and printer sharing protocol
Microsoft Network Client
In a LAN, network neighbors often encounter various problems.
7. Questions about the problem of no response or slow response from network neighbors.
When browsing network neighbors in WINXP and win2000, the system will be delayed by 30 seconds by default. Windows will use this time to find whether the remote computer has specified scheduled tasks, if the network does not respond during the search, there will be an unlimited wait, so it is not surprising that the latency of more than 10 minutes or even an error is reported. Specific solution:
Delete two subkeys in the Registry
Find the primary key HKEY_LOCAL_MACHINE/software/Microsoft/Windows/CurrentVersion/Explorer/remotecomputer/namespace in the registry"
Delete the following two child keys: {2227a280-3aea-1069-a2de-08002b30309d} and {D6277990-4C6A-11CF-87-00AA0060F5BF }.
Among them, the first child Jian decides whether to search for online printers (or even search for printers on the internet). If there is no shared printer on the network, the key can be deleted. The second child Jian decides whether to search for the specified scheduled task.
8. In addition, if you cannot set the share (Gray), Please reset "set the home or small office network" in the network connection, and select "enable file and printer sharing"

Inaccessible mainly because XP does not enable Guest by default, and even if guest is enabled, XP does not allow guest to access the computer from the network by default.
I have observed in my lan that it may also be related to the failure of routers and other computers, as well as other Windows versions in the LAN. the WINXP system itself is prone to problems in access to network neighbors. Restarting may solve the problem. I have also encountered a situation where everything has been set up, but the network is not accessible. I finally reinstalled the system to solve the problem.