Another method for tcp ip Network Fault Diagnosis

In the previous sections, we summarized the traditional tcp ip protocol Network Fault Diagnosis Methods and summarized some key issues related to tcp ip protocol network fault diagnosis. Now let's learn another method-the structured method. Now let's take a look at this author's painstaking efforts. The author's structured Diagnosis Method for tcp ip protocol network faults consists of three key parts:

1. factors that determine the problem

That is to say, consider the following:

Client: the client with the problem

Server: the server, printer, or other network resources (such as the Internet) that the customer cannot access ｡

Network in the meantime: cables (if not wireless), hubs, switches, routers, firewalls, proxy servers, and other network architectures between clients and servers ｡

Environment: may affect the external conditions of your network, such as fluctuations in power supply and maintenance of buildings ｡

Range: one or more related clients/servers ｡

Period: continuous, intermittent, or occasional, start time, etc ｡

What is the connection type? physical layer, network layer, transmission layer, or application layer? Authentication or access control? And so on ｡

Symbolic information: error messages on the client machine, logon dialog box, and so on ｡

2. Determine the fault diagnosis measures to be applied

These measures include:

Verify the physical media related to the client, server, and network architecture hardware. That is to say, check the cables, ensure that the network adapter is correctly installed, and further find and verify the network connection that can display the media disconnection status ｡

Verify the TCP/IP protocol configuration of the client, server, and network architecture hardware. On the client, this means checking the IP address, subnet mask, default gateway, DNS settings, and so on. For Network Architecture hardware, that is, the route table and Internet gateway on the vro ｡

Verify the connectivity of the route selection between the client and the server. That is to say, ping, pathping, tracert, or other similar tools are used to verify the connectivity of the end-to-end TCP/IP at the network layer; packet sniffing is used to monitor transport layer sessions. nslookup, telnet, and other tools are used to diagnose Application Layer problems, such as domain name resolution and identity authentication ｡

3. Understanding, inquiry, and testing

The following describes how to work, how to use data packages, and how to use netdiag.exe. Successful TCP protocol network fault diagnosis is based on understanding how TCP/IP works and related test tools. strive to understand the network monitor tracking mode, then you will encounter difficulties in diagnosing some problems ｡

It is also critical to ask some appropriate questions for successful fault diagnosis. It is essential to learn how to step by step and when to go straight to the topic of the art of fault diagnosis, this also involves making full use of your mind, that is, you must have full imagination and careful thinking ｡

Finally, it is critical to test and isolate the problem in a down-to-earth Manner. Therefore, you need a toolbox for fault diagnosis, and there is nothing to help you solve complex problems better than the rich experience ｡

4. Summary

It may be frustrating to diagnose tcp ip network faults, but it is also fun. In future articles, we will elaborate on the measures and tools for fault diagnosis, to help you solve problems in the network ｡