Open network connection on the crash _ Internet surfing

Failure Phenomenon

The author of a colleague will use the notebook computer back to the company, ready to connect the company's local area network, the results do not know what the reason, not connected to the local area network, notebook computer startup speed has slowed. Now the problem with this laptop is that it feels very slow to boot and run, and it crashes as soon as a network connection is turned on. However, through the Windows Task Manager view, found that the CPU usage is only about 2%, is normal, and did not find a larger program running in the system background.

　　 Diagnostics Process

The author will connect the notebook computer power, boot, and really feel the speed is simply unbearable, originally launched a fast Windows Professonal is like the installation of Active Directory (active directories) of Windows 2000 Server, there is even a time when the hard drive does not seem to react at all.

Finally started, through the observation of the whole start-up process, you can be sure that the system is not met with viruses, Trojans and the like, but the author or a few popular anti-virus software scanned a bit, in this process system performance is normal, the result of course is nothing.

The author then opens "My Computer" → "Control Panel" → "Network and dial-up Connection", on the double click "Local Connection" icon, the system suddenly "stiff", no response. But still can through the "Alt +tab" key to switch between the windows, so the author right click on the taskbar, in the Pop-up shortcut menu select "Task Manager" command. Take a closer look at the processes table and the application task List and find no exceptions, CPU usage is only 2%, because the local connection state is not counted as a process in the application task sheet.

Patiently waiting for a while, the system looks back to normal, the author also found the "culprit." Originally, click the Properties button in the Local Connection Status dialog box that is normally displayed, after you go to the Local Area Connection Properties dialog box, look at the properties of Internet Protocol (TCP/IP) and find out that you are using "Automatically obtain IP address", but you have specified a default gateway of 192.168.0.10.

I think, is not in this notebook computer access to the company's local area network, according to the company's internal computer set. So, back to the "Control Panel", double-click the "System" icon, the results of the "System Properties" in the "network ID" to see that this notebook computer is subordinate to the domain, is the company's internal LAN domain. Finally found the fault.

The author clicks on "Properties", changes the network identification, change it to subordinate to the work level, meanwhile, enters the Advanced dialog box of Internet Protocol (TCP/IP) properties, "192.168 in the default gateway". 0.10 Delete. After both changes are correct, reboot the system and solve the problem successfully.

　　 excluding Experience 　　

Wndows 2000 checks the network connection status when it starts. If the network card has not yet set an IP address, the system will automatically search and assign an IP address to it, the process may take up to about 10s. If the system setup uses a DHCP server to automatically assign IP addresses, the wait process may be longer if the server does not start. Therefore, it is recommended that the RFC 1597 specification be used to specify the private IP address directly:

10.0.0.0~10.255.255.255

176.16.0.0-172.31.255.255

192.168.0.0~192.168.255.255

Similarly, if a computer joins a domain, but the domain server is not started or even on the network, it can take a long time to search for a domain server at startup. If you are sure that your computer is not in a domain, it is a good idea to set up your computer to belong to a workgroup.