Since we have put the network into the home, 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 lot of knowledge and rich networking experience, as well as a series 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”.
Troubleshooting often plays a 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;, in the "System Information" window that opens, click “Tools & Rarr; Network Diagnostics, then go to the Network Diagnostics Run window of the Help and Support Center and click on “Scan Your System” to diagnose the entire network.
In this process, the system will call Ping and other commands to detect and troubleshoot gateways, DNS servers, etc. Once this process is complete, expand all items marked with a red "failure" to quickly diagnose where the failure is. 2. TCP/IP Troubleshooting Tool IPConfig
The information provided by IPConfig can be used to determine some configuration problems 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 information obtained, you can 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.
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.
1. “Repair"Features
“Repair" function uses a "batch" method, the system will automatically call the built-in near ten network repair commands each time the function is executed, from Some aspects help users solve network problems. It can be seen in the context menu of “Local Connections”.
This feature allows the network to re-allocate DHCP dynamic IP, refresh the address resolution protocol and NetBIOS name cache. This unobtrusive "fix" function eliminates the need to manually enter "ipconfig /renew", "arp –d", "nbtstat – R", "nbtstat – RR", “ Ipconfig /flushdns” and many other commands can help us solve minor problems in many networks very quickly.
2. Suspend service
In Windows XP, many system services are closely related to the network. If you find some unstable settings after performing some settings, you may want to temporarily close the related services to see if you can Solve the problem.
It is well known that using IPSec technology can improve the security of the network. However, in some cases, the IPSec policy will require network communication to adopt the "security mode", which may make some network connections unstable. So, after setting up the IPSec policy, the 环 榷ㄊ ? 环 环 环 环 环 诵 诵 诵 诵 诵 诵 诵 诵 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 惺淙搿皊 服务 服务 服务 服务 服务 服务 服务 服务 服务 服务 服务 服务 服务 服务Temporarily shut down to see if the fault can be resolved. If the problem disappears after stopping the IPSec service, it indicates that the fault is caused by some of the IPSec policies. After the approximate scope of the fault is determined, the fault can be eliminated. For example, check or disable the suspicious IPSec policy one by one and observe them. Is there a problem with the settings?
If some faults are caused by defects in the design of the system itself, it must be solved by the method of “patching”, and those caused by the messy protocol settings need to be reinstalled to solve the problem completely.
1. Patchwork
Many network failures that are difficult to solve and often difficult to solve are often caused by defects in the design of the system itself. For this situation, we only have one thing to do with —— download the patch to fix it. .
Microsoft's help and support URL is "http://support.microsoft.com/default. asp x”, at this site, we can download patches for all Windows products including Windows XP SP2.
2. Reloading the Protocol
For some of the obvious problems caused by incorrect installation and configuration of the network protocol, reloading the protocol may be the best solution. In Windows 98, you can reinstall all protocols and services by deleting the NIC in the Properties window of "My Network Places"; use "Netsh int ip reset c:\\123." in Windows 2000/XP/2003. The txt” command allows the TCP/IP protocol to be restored to its original state (without any settings) and then re-set.
There are many kinds of network failures, but they are not irregular. With the continuous enrichment of experience, the ability to eliminate network failures will be higher and higher. I hope that the network troubleshooting ideas and methods introduced by Dr. e in this issue can be a useful assistant for preventing and eliminating network failures, and can improve everyone's ability to manage and maintain the network.