WINDOWS2000 Secret weapon Connectivity testing tool

Network Connectivity Diagnostics (Netdiag.exe)

As the CW2KP support for the network than the previous version of Windows has been greatly enhanced, so the support tools, network failures are equipped with the corresponding diagnostic testing tools, the introduction of the Netdiag.exe, is quite convenient and practical one.

The tool takes only a command-line form (such that the overhead of system resources is very small), used to help you diagnose and troubleshoot network connectivity failures, the main method used is to test the state of the network by executing a specific program, separating the fault area one step at a point where the fault occurs. The core of the test is to get the key state information of the network, it is obvious that the problem is exposed, to facilitate the technical support personnel, network management personnel to conduct problems investigation and analysis, to determine what direct and effective means to take. The better thing is: This tool is simple and easy to use, the parameters and switches are very small, but powerful, so that both technical support personnel or network managers can concentrate on the analysis of the output state without the heart of the next Mo, so much the above people's favorite.

Because the tool contains too much content, I intend to be divided into two parts, this time mainly introduces the grammar and test name, the rest are put in the next article.

First of all, the system must already "bind" the TCP/IP protocol and the network adapter in most of the following cases, or when the tool is actually applied. This network connectivity testing tool mainly has the following characteristics:

1. It is easier to write script files by taking command line execution.

2 with Windows Management Instrumentation (WMI) and the corresponding dynamic connection library and MSInfo, you can use the GUI login pointer.

3. Collect network status information, detect network drivers, protocol drivers, receive/transmit capabilities, and so on.

4 test methods that accept input or return information generated by an application or service.

5. Running on the WIN32 operating system.

6. Network administrators can use the scheduler, each interval a certain amount of time to generate reports automatically. The following is an introduction to syntax, followed by an example analysis.

Complete syntax for Netdiag:

Netdiag [/q] [v] [l] [/debug] [/d:domainname] [/fix] [/dcaccountenum] [/test:testname] [/skip:testname]

Parameters and Meanings:

/q

Specifies the static output. (Error message only)

/V

Specifies the verbose output.

/L

Sends output to the NetDiag.log file.

/debug

Specifies more detailed output information, which may take several minutes to complete.

/d:domainname

Finds the domain manager in the specified domain.

/fix

Maintenance of local problems.

/dcaccountenum

Enumerates the computer accounts in the domain Manager (in).

/test:testname

Perform tests or generic tests that have already been listed, and test before testing to ensure that the TCP/IP protocol is "bound" and that the network adapter must work properly. If you do not specify a test to skip, then by default for all tests, the tool names all of the tests that can be performed, regardless of whether you specify a test to be performed or a test that you specify to skip. To facilitate the lookup, I enclose these test names in a simple description listed below ("Test" and "test" in the following sections are understood to be of the same meaning):

* Autonet-Automatic APIPA inspection, that is, the automatic "private" IP address test.

* Bindings-binding test

* Browser-Browser inspection

* Dclist-Verify domain controller list

* DEFGW-Default gateway Test

* Dns-dns Inspection

* DSGETDC-domain Controller "discovery" test

* IPCONFIG-IP address configuration test

* IPLOOPBK-IP address loopback ping test

* IPX-IPX Inspection

* Kerberos-kerberos Inspection

* LDAP-LDAP Inspection

* Member-domain membership test

* MODEM-MODEM (Modem) Diagnostic test

* NBTNM-NETBT Name Inspection

* Ndis-netcard Inquiry Inspection

* NETBTTRANSPORTS-NETBT Transmission Inspection

* Netstat-netstat State Information Inspection

* Netware-netware Inspection

* Route-routing test

* Trust-confidence Relationship test

* Wan-wan Configuration Inspection

* Wins-wins Service Inspection

* Winsock-winsock Inspection

/skip:testname

* Skip the test with the specified name, which is identical to the name listed above, so it is no longer repeated.