Windows XP operating system frequently encounters network failure Analysis (2)

Second, the LAN problem

1. Windows XP cannot exchange visits

In fact, there are many kinds of solutions on the Internet, but we still have some netizens are not very clear about this problem, I now go to some forums to visit, but also often see people ask such questions, the following gives you a summary of the two different environments to resolve the Windows XP exchange of visits methods.

• Family environment and office environment

1, in this environment, Windows XP accounts are generally set up a password, you can start-settings-control Panel-management tools-local Security policy-local policy-security options, find and double-click the "Network access: local account sharing and security mode", the default " Guest only-local user authenticate as guest "change to classic-local users authenticate as themselves," Restart the computer after setting is complete to make the settings apply successfully.

2, to access a computer only need to know a computer account password can be accessed, first look up the computer, in the pop-up dialog box to enter a computer account and password can be.

3, if you still do not have access to your network Neighborhood, check your workgroup and firewall settings.

• Network Room environment

Because users in the network room are unsure, the Windows XP account does not normally have a password set, and you can change access by following these steps

1, right click on "My Computer" selection--management-Local Users and Groups-users, right-click Guest, select Properties, the "account has been deactivated" before the check out.

2, start-Settings-control Panel-management tools-local Security policy-local policy-User rights Assignment, locate and double-click "Deny access to this computer from the network" to delete the guest user in the pop-up window.

3, start-Settings-control Panel-management tools-local Security policy-local policy-security options, locate and double-click Network access: Sharing and security mode for local accounts, and change the default guest only-local user authenticate as guest to classic-Local users authenticate themselves

4, start-Settings-control Panel-management tools-local Security policy-local policy-security options, disable "account: Users can only access the console login with null password"

5, if you still do not have access, click Start-run ――gpedit.msc―― Computer Configuration ――windows Settings-Local policy-User rights Assignment, locate and double-click "Deny access to this computer from the network" to remove the guest user.

6), after the setup is complete restart the computer to make the settings apply successfully.

2. Windows 98/2000/XP/2003 user authentication issues accessing Windows XP

First questions about why guest cannot access:

• By default, the Guest account is disabled

• By default, Windows XP's local Security policy prohibits guest users from accessing the network

• By default, local Security policy-security option, account: User with null password can only be used for console login is enabled, that is, no account of the null password can only log on from the network access, the guest default blank password.

So, if you need to use a guest user to access XP, go to the three settings above: Enable guest, modify security policy to allow guest to access from the network, disable security policy in 3, or add a password to guest.

Sometimes there is another situation: when you visit XP, the user name in the logon dialog box is dimmed, always the guest user, and you cannot enter another user account.

The reason is that this security policy is at Mischief (Administrative Tools-> Local Security Policy-> security options-> "Network access: Sharing and security mode for local accounts"). By default, the way XP is accessed is "Guest only", then you access it, and of course it is fixed to guest and cannot be entered into another user account.

So the easiest way to access XP is to simply modify the security policy above to "classic" without having to enable guest. Other systems Access XP can enter account information on their own.

As for Access 2003, by default 2003 disables guest, but without XP's annoying default, contradictory guest way to share, you can enter the username password directly.

A small office LAN, are WinXP system, can be on the network, can also see the other computer, but can not see the other side of the computer to share a hint of the network path is incorrect, or you do not have the right to use the network is probably this meaning I do not remember very clearly!! Guest account I also enabled the!WINXP firewall is also closed, the IP address is no problem!! I hope you can give analysis!! Thank you so much!

Reason: Security policy restrictions exist in WIN2000/XP.

Sometimes, win2000/xp "smart" over the head, although we have enabled the Guest account, from the Win98 still can't access win2000/xp, such as the use of such as rising firewall vulnerability fixes, it will modify the "Deny access to this computer from the network" policy, Modify it in the following ways:

Start-> run-> gpedit.msc-> Computer Configuration-> Windows Settings-> Local policy-> user Rights Assignment-> delete the Guest user in Deny access to this computer from the network.

3, the LAN "network Impassability" how to Do

In a local area network, found that a certain computer networks are faulty, how to do? Let's talk about the problem of network failure. In the exclusion of the local system core failure caused by the reasons, the network is often caused by the following factors.

(1) Network configuration is not normally the case, the IP address of each machine in the same campus network must be unique, the subnet mask of all machines must be the same in the same subnet, the default gateway must be the IP address of the network card on which the subnet and other subnets can exchange information. To resolve this type of problem, you can open the desktop's Network Neighborhood properties menu, check the TCP/IP protocol configuration data, analyze the IP address, subnet mask, the default gateway configuration is correct, and, if not correct, reconfigure.

(2) Network interface failure machine can not be online is often caused by the crystal head on the network cable and the interface of the network card is bad, especially the laptop J that often needs to move. Encountered such a failure is the first crystal head from the NIC interface dial again, in order to ensure that the network interface has been plugged in the case, with the Pi ng command to test, first ping this machine, and then see if you can ping other machines. For example, the IP address of this machine is 192.168.0.2, and the 1P address of the other working machine is 192.168.0.3, ping 192.168.0 in command line input after the computer restarts.

(3) If the information returned on the screen is information such as reply from 192.168.0.3:bytes=32 time<10mstt1=128, the problem has been resolved; if it is "requested time out", it means that the network is not available. Then enter the command ping 192.168.0.2 connect this machine, if the information is still "requested time out", indicating that the work of the Machine network card has a physical failure. Need to be replaced or repaired; If the information returned is "Reply fr6m 192.168.0.2:bytes=32 time<10ms ttl=128", there is no problem with the native NIC. At this point can be removed from the connector, to observe whether the crystal head has been rusty or dust, wipe it clean, and then remove the dust in the interface of the network card, after a good test after the law, in most cases can solve the problem.

4, network neighbors do not see the computer

Open "Control Panel → performance and maintenance → management tools → services", start inside the "Computer Browser" service.

5, network neighbors do not respond or slow response

Turn off Winwindows XP's 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.