About Windows XP network failure

Power outage, virus, misuse, too many factors may cause file corruption, you do not have a dream of "time package skin", so if you want to restore the file to normal I have to do it myself. If the system file is damaged or lost, the system function cannot be used, and the whole system is paralyzed. Therefore, the system file has three lengths and two shorts, which directly means system failure. Today, we will explain the small classification network failures in the system failure, let's learn together.

Windows XP failure 1. Local connection is restricted or no connection

[Windows XP failure Phenomenon] Each time you enter Windows XP, a prompt will appear, “Local connection is restricted or no connection”, and there is a yellow exclamation point on the network connection.

[Windows XP failure analysis] If it is an intranet, check if the intranet server has assigned IP to the computer, or do you want to specify the IP manually? If it is ADSL dial-up, then the network settings in the network card are “ In case of automatic IP address, if you can't get IP, it will be like this. Because the network server of the network service provider will only allocate one IP to the virtual network card of ADSL, it will not be assigned an IP to that network card.

[Windows XP Troubleshooting] The easiest way is to right-click the NIC on the system tray and click the “Status → Attributes” button to open the Local Connection Properties dialog box, in the “General” dialog box. ” Remove the tab from “ notify me when this connection is restricted or no connection & "√” in front of the option. But doing so will cause Windows XP to search the DHCP server every time it is booted to get a dynamic IP, which affects the speed of booting the system. The best way is to remove “ notify me when this connection is restricted or no connection, “√” in front of the option, then <;this connection uses the following items>; double-click "Internet Protocol (TCP/IP) & rdquo;, select “ use the following IP address & rdquo;, then enter for example 192.168.1.1 (IP address), 255.255.255.0 (subnet mask), manually specify the IP to speed up Windows XP startup speed.

Windows XP failure 2. Windows XP can not establish the correct connection

[Windows XP failure phenomenon] When establishing a network connection under Windows XP, the connection error is prompted.

[Windows XP failure analysis] This kind of failure is generally considered from the login password error, the software and hardware of the network card.

[Windows XP Troubleshooting] First, launch IE browser, click "Tools/Internet Options", switch to the "Connections" tab, enter the password to complete; if the fault persists, then view Network card software and hardware. Right click on the desktop "My Computer", select "Attributes/Hardware", click "Device Manager", and check whether the network card has a yellow exclamation point in the opened interface. If there is a yellow exclamation point, reinstall the network card. If the fault cannot be solved again, uninstall the NIC driver and reinstall it. After the installation is completed, if the connection still cannot be completed normally, you can double-click the connection and set the IP address and subnet mask of the Internet Protocol (TCP/IP) in the “Properties” property. The hardware and system are normal. Underneath, it should be able to connect properly.

These two Windows XP failures are common network failures for users, and the solution is also simple and feasible. I hope that the fault solution described in this article can be helpful to users.