Network administrator to use a good hand-protocol analyzer

Protocol Analyzer is one of the most powerful tools in the network Administrator library. It can save the company a lot of time and money by turning problems that are difficult, time-consuming, annoying to CEOs and even having to restart all machines to be short-lived and easily reflected in weekly status reports.

However, just like any other complex tool, it must be properly used to achieve maximum benefit. When using the Protocol Analyzer to diagnose network failures, you should try to avoid ...

Error 1, parser mistakenly reset

The correct placement of analyzer plays a decisive role in diagnosing faults quickly. Imagine that the parser is placed in a network window, like a building window, where changes in vision depend on which window to look out. Looking from the south window, there is no traffic congestion on the North Highway of the building. Tracing often takes a long time when analyzing an analyzer that is placed in an improperly positioned network. So, how do we put the analyzer correctly? We can give an example.

The following are a few possible problems and cause analysis:

Imagine a: A host, Server A, the host cannot communicate with any other host. Possible causes:

1 Server A is not configured properly;

2 Server A configuration of the network card error;

3) Server A is on the local area network problem;

4) Server A has an error on the LAN segment.

Imagine B: A host, Server B, the host cannot communicate with any of the hosts in the remote Network X, and hosts on the LAN or other remote network have no faults (this means that the problem cannot occur on the LAN section of Server B or Server B).

Possible causes:

1 Server B has some configuration errors about network x;

2 The connection to the network segment of the router where the server B is connected to the net X is out of question;

3 The Server B local area network and the Web x of one or more links out of the problem;

4 The network x is used to connect to the network where the server B is located, and there is a problem on the network segment;

5 network x out of the question.