[Introduction] In this article, we will start from the three aspects of diagnosing the causes of network failures, quickly eliminating minor faults, and completely solving network faults, to help you understand and master the method of eliminating the network "stricken disease" …… [Text] Since we have put the network "娶" into the house, we have been troubled since then, and sometimes the network is unstable, and sometimes there is a problem with transmission. In the face of network failures that may occur at any time, Dr. e will introduce the ideas and methods of using some Windows XP built-in tools to eliminate the network “disease”. Due to the unique complexity of the network itself, the location and elimination of many network faults requires a great deal of knowledge and rich networking experience, as well as a range of software and hardware tools. In this article, Dr. e will lead you from the three aspects of diagnosing the causes of network failures, quickly eliminating minor faults, and completely resolving network faults, to help you understand and master the method of eliminating the network “disease”. Questioning the pulse of the doctor Just as the doctor must first have a certain understanding of the patient's condition in order to prescribe the drug, it is also necessary to first perform the initial "diagnosis" to eliminate the network failure. This diagnosis process will often play a role in troubleshooting the next step. Crucial role. Only when the cause of the fault is clarified can the accurate use of the corresponding tool achieve the effect of “drug to disease”. 1. "Automation" Network Diagnostics Click “Start → Programs & Rarr; Attachments & Rarr; System Tools & Rarr; System Information & rdquo;, click on the "System Information" window in the "Open & ldquo; Tools & Rarr; Network Diagnostics & rdquo ;, then go to the Network Diagnostics Run window of the Help and Support Center & click on “Scan Your System” and the Network Diagnostic Tool will begin to diagnose the entire network. In this process, the system will call Ping and other commands to detect and troubleshoot the gateway, DNS server, and so on. Once this process is complete, expand all items marked with a red "failure" to quickly diagnose where the failure is (Figure 1).
2. The TCP/IP troubleshooting tool IPConfig uses the information provided by IPConfig to determine some configuration issues that exist in the TCP/IP properties. For example, use “IPConfig /all” to get detailed configuration information of the host, including IP address, subnet mask and default gateway, DNS server and other information. Through the obtained information, it is possible to quickly determine the fault of the network. For example, if the subnet mask is 0.0.0.0, it means that the IP address in the LAN may have a duplicate phenomenon; if the returned local IP address is displayed as 169.254.*.* and the subnet mask is 255.255.0.0, it means This IP address is assigned by the Windows XP's automatic private IP addressing feature. This means that TCP/IP failed to locate the DHCP server or did not find a default gateway for the network interface. If the returned local IP address is displayed as 0.0.0.0, it may be caused by a DHCP initialization failure that causes the IP address to be unassigned, or because the network card detects a lack of network connection or TCP/IP detects a conflict in the IP address. 3. Connection troubleshooting tool Ping You may be familiar with the Ping command. There are also many applications for Ping. Here, Dr. e only talks about how to detect the connection failure by detecting the remote IP address and domain name through the Ping command. Assume that the method of using the Ping domain name fails, but the Ping IP method succeeds. Then the problem is obviously on the host name resolution service. At this time, you should check whether the DNS server set in the native TCP/IP property can be parsed normally. . 4. “Network Path” Diagnostic Tool Tracert Tracert helps us determine the path (including routers and gateways) from one host to another in the network. Through the feedback from Tracert, we can initially determine the location of the fault. Assuming that the network from the department A to the workshop is not available, we can use the “Tracert Workshop IP” command to check the location of the fault. When there are three asterisks in the line that indicate that the communication has failed, then the communication will fail. You can send people to the fault location to check the line and equipment. Micro-self-therapy In the network application, there are often some troublesome small problems, such as the network when the time is broken, can only be on the QQ but can not open the web page. After the results of the previous "diagnostics", are you willing to wait for the master to troubleshoot, or are you willing to use some of the "quick effect" approach to the emergency "self-treatment"? In general, you still want to troubleshoot it yourself.