Solve the local area network can not visit each other's full strategy

Visit | The solution is generally simple settings and physical reasons, in which XP can not access each other is the most recent problems frequently encountered. This article is to solve these problems. Divided into two parts

One: Set

Now, there are many people using Win2000 and WinXP to connect, but in the specific use of many users reflected in Win2000 and WinXP browsing the network of neighbors is very slow, especially in the network Win9x and WinME workstation is particularly obvious, Sometimes it takes more than 10 minutes to open a network neighborhood, and it often complains. So what is the slow speed of the people? According to the author to infer the main reason is two.
Network protocol configuration issues,
WinXP the problem of planning tasks.
However, if other Windows computers do not see the WinXP computer at all in their network Places, it is possible that the user lockout and security policy is not set. At this point, we need to start from the following aspects, the author has encountered similar problems before, but in a large number of networking experiments summed up a set of effective solutions, now one by one professors to everyone.

I. Installation and setup of network protocols
1. Install NetBEUI protocol in WinXP
Right, you are not wrong, is to install the NetBEUI protocol in the WinXP. Microsoft only supports the TCP/IP protocol and the NWLink Ipx/spx/netbios compatibility protocol in WinXP, officially announcing that it no longer supports the NetBEUI protocol. But in the actual use of a small LAN, the two protocols that Microsoft supports are less than satisfactory. For example, in the process of solving the problem of slow online neighbors, the author uses a lot of methods after the speed of the network Neighborhood although better, but still slow as a snail; In addition, the Protocol, customers and services set up multiple network adapters, the two protocols also exist bugs, multiple network adapters must be bound all the protocols (except NWLink NetBIOS), customers, and services, even if you cancel some of the binding reboot system will automatically add, this is obviously not very good to meet the actual needs of network construction. And when the author installs the NetBEUI agreement in the WinXP, all the above two questions are solved satisfactorily.
There are 3 files in the "\valueadd\msft\net\netbeui" Directory of the WinXP installation disc, where "NETBEUI. TXT "is the installation instructions, the other two are the files required to install the NetBEUI protocol. The specific steps to install are as follows:
Copy "NBF. SYS "to the"%systemroot%\system32\drivers\ "directory;
Copy "NETNBF. INF "to the"%systemroot%\inf\ "directory;
Click the Install button in the network connection properties to install the NetBEUI protocol.
Note:%systemroot% is the WinXP installation directory, such as the author's WinXP installed in the F:\Windows directory, you should use F:\Windows to replace%systemroot%.

2. Set up other network protocols in WinXP
I suggest that if your LAN is not on the Internet, you just need to install the NetBEUI protocol. In a small LAN (a network with 200 or so computers), NetBEUI is a protocol that consumes the least memory and is the fastest, and NWLink Ipx/spx/netbios compatible protocols should be deleted.
If your LAN is on the Internet, you must install the TCP/IP protocol. However, for fast access to the network, it is recommended to specify the IP address of each workstation (unless there is a DHCP server on the network), or the workstation will always look for a DHCP server to slow down the Internet.
Of course, if the network only install TCP/IP protocol can also achieve the local area network exchange, but in the online neighborhood to see other machines directly is more difficult, you must first search a machine to access it, which in many practical network use is very inconvenient.
3. Other Windows computer network protocol settings
Careful users may have discovered a "set up a home or small office network" wizard in WinXP's online neighborhood, which makes it easy to set up LAN shares, Internet connections, and small LANs. The wizard also provides a network installation floppy disk for other Windows computers that connect to WinXP.
However, the author does not advocate the use of this network installation floppy disk. On other Windows computers that connect to WinXP, just install the NetBEUI protocol and set the network flag; To connect to the Internet, you just have to install the TCP/IP protocol and specify a good address. This is exactly the same as the traditional LAN setting, and it is recommended that you use less ipx/spx compatibility protocol.


Two, completely disables the WinXP the plan task
When browsing Network Places in WinXP and Win2000, the system defaults to 30 seconds, and Windows uses this time to find out whether a remote computer has a scheduled task (or even a search on the Internet). It is no surprise that more than 10 minutes of delay or even an error is not surprising if the network does not respond to an infinite number of waits when the search is made. The following are the specific solutions.
1. Turn off the WinXP Mission Service (Task Scheduler)
You can open the Task Scheduler Properties dialog box in Control Panel/Administrative Tools/Services, click the Stop button to stop the service, and then set the startup type to manual so that the service does not start automatically the next time you start.


2. Delete Two subkeys in the registry
To locate the primary key in the registry
Hkey_local_machine\software\microsoft\windows\currentversion\explorer\remotecomputer\namespace "
Delete the following two sub-kin
{2227a280-3aea-1069-a2de-08002b30309d}
{D6277990-4C6A-11CF-87-00AA0060F5BF}
Among them, the first Zijian determines whether the network Neighborhood to search for the printer on the Internet (even to the internet to search), if there is no shared printer on the Internet can delete this key. The second Zijian determines whether the specified scheduled task needs to be found, which is the culprit of slow network Neighborhood and must be removed.

Third, troubleshoot other Windows computers can not access the WinXP computer problems
Some netizens installed the network, but found that installed with Win9x or WinME operating system of the computer can not access the WinXP computer, even in the online neighborhood can not see each other. If you are experiencing this kind of trouble you can do the following checks.
1. Check if guest user is enabled
By default, the guest user in Win2000 and WinXP is disabled. To enable guest users to remove the "account deactivated" tick in the Control Panel/Administrative Tools/Computer Management/Local Users and Groups/users. This user is best not to set a password and select "Users cannot Change password" and "Password Never Expires", which makes it easy for users to access and reduce the likelihood of trouble. But the premise is that the guest user must set the right and the group, otherwise endless.

2. Check whether the guest user is denied access to this computer from the network
In WinXP, the guest user is denied access to the native from the network by default. You can view the Control Panel/Administrative Tools/Local Security Policy/local Policy/User rights Assignment/deny access to this computer from the network and delete it if it includes the guest user. If you are building a domain-Win2000 server or winxp.net server, you must also remove the guest user from the corresponding project in the domain security policy, and note that it takes several minutes for the deletion to work.

3. Set a password for the guest user
If the guest user has a password, other Windows workstations will be prompted to enter the password when accessing the WinXP computer, and entering the guest user's password can also enter the WinXP computer. When you enter a password, you can select the "Save Password to password list" item below, and the password will no longer be prompted the next time you enter (unless the user's password has changed). Of course, if you are already set to a logon domain on a Windows workstation and you log on to the domain with a domain user, you will not be affected by the password for the guest user.

Two: In particular, XP exchange visits if the settings are no problem that's basically the strategy.

On a computer with Windows XP installed, even if the network connection and sharing settings are correct (for example, if the IP address is on the same subnet and the NetBIOS on TCP/IP is enabled, the firewall software does not prohibit the ports of 135, 137, 138, 139, etc.) for file sharing, and other systems ( Users, including Windows 9X/ME/2000/XP, are still unable to access the computer. What should we do to solve the problem?

By default, the local security settings for Windows XP require that all users who have access to the network use the Guest method. Also, the user rights Assignment of Windows XP Security policy prohibits guest users from accessing the system through the network. Such conflicting security policies have led to the inability of other users in the network to access computers using Windows XP over the network. You can use the following methods to solve the problem.

method to remove the restrictions on the Guest account

Click "Start → run" and type "GPEDIT" in the "Run" dialog box. MSC, open Group Policy Editor, select Computer Configuration →windows settings → security settings → local policies → user rights Assignment, double-click the "Deny access to this computer from the network" policy, and delete the "GUEST" account. This allows other users to access the computer using the Windows XP system over the network using the Guest account.

Method two change network access mode

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

Now, when other users are accessing a computer that uses Windows XP over the network, they can log on with their identity (if this account is already in Windows XP and the password is correct).

When this policy changes, the way in which files are shared is also changed, and after the classic: Local users are authenticated by themselves, we can limit the number of users who simultaneously access shared files and set different access rights for different users.

However, we may also encounter another problem, when the user's password is empty, access will still be denied. There is an "account" in the security options: Local accounts with blank passwords only allow console logon policy is enabled by default, and users who have blank passwords are prohibited from accessing a computer that uses 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.