Win2k "secret weapon" connectivity test tool

Network connectivity diagnostics (Netdiag.exe)

Since CW2KP support for the network has been greatly enhanced than the previous version of Windows, support tools are also equipped for network failures. There is a corresponding diagnostic test tool. Netdiag.exe introduced this time is quite convenient and practical.

This tool uses only the command line (so that the overhead of system resources is small) to help you diagnose and troubleshoot network connectivity. The main method used is to test the network by executing a specific program. The state, step by step to separate the fault area, and finally determine the exact location of the fault. The core of the test is to get the critical state information of the network. It is intuitive to expose the problem, so that technical support personnel and network administrators can troubleshoot and analyze the problem to decide which direct and effective means to take. What's even better is that this tool is easy to use, uses few parameters and switches, but is powerful, so that technical support staff or network administrators can concentrate on analyzing the output status without having to worry about it. Oh, so it is loved by the above people.

Since the tool contains too much content, I intend to introduce it into two parts. This time I will introduce the syntax and test name first, and the rest will be included in the next article.

First of all, it is pointed out that in most of the following cases, or when the tool is actually applied, the system must have been "bound" to the TCP/IP protocol and network adapter. This network connectivity test tool has the following characteristics:

1. Take the command line execution method, it is more convenient to write script files.

2 After using Windows Management Instrumentation (WMI) and the corresponding dynamic link library and MSINFO, you can use the GUI login pointer.

3. Collect network status information, detect network drivers, protocol drivers, receive/send capabilities, etc.

4Test the method of accepting input or return information generated by an application or service.

5. Run on Win32 operating system.

6. The network administrator can use the scheduler to automatically generate reports every time interval. The following describes the syntax first, followed by an example analysis.

Netdiag's full syntax:

netdiag [/q] [/v] [/l] [/debug] [/d:DomainName] [/fix] [/DcAccountEnum] [/Test:testname] [/skip:testname]

Parameters and meaning:

/q

Specify static output. (Only for error messages)

/v

Specify detailed output.

/l

Send output to the NetDiag.log file.

/debug

Specify more detailed output information, which may take a few minutes to complete.

/d:DomainName

Find the domain manager in the specified domain.

/fix

Repair local problems.

/DcAccountEnum

List the computer account in the domain manager (in).

/test:TestName

Execute the test or general test of the listed project. Before testing, check to make sure the TCP/IP protocol is "bound". Of course, the network adapter must also Can work normally. If you do not specify a test to skip, the default is to do all the tests, the tool will name all the tests that can be done, regardless of the test you want to perform or the test you want to skip. For the sake of easy searching, I will list these test names with a simple description below (the "test" and "test" in the following sections can be understood as the same meaning):

* Autonet - Automate APIPA check, ie Automatic "private" IP address verification.

* Bindings - Binding Verification

* Browser - Browser Verification

* DcList - Verification Domain Controller List

* DefGw - Default Gateway Verification

* DNS - DNS Checking

* DsGetDc - Domain Controller "Discovery" Checking

* IpConfig - IP Address Configuration Checking

* IpLoopBk - IP Address loopback ping check

* IPX - IPX check

* Kerberos - Kerberos check

* Ldap - LDAP check

* Member - domain membership check

* Modem - Modem Diagnostic Test

* NbtNm - NetBT Name Check

* Ndis - Netcard Query Test

* NetBTTransports - NetBT Transfer Verification

* Netstat - Netstat Status Information Verification

* Netware - Netware Verification

* Route - Routing Verification

* Trust - Trust Relationship Verification
>

* WAN - WAN Configuration Checker

* WINS - WINS Service Checker

* Winsock - Winsock Test

/skip:Te stName

* Skips the tests for the specified names. The names of these tests are exactly the same as those listed above, so they are not listed again.

Execute this program, you can open "Start -> Run", then type "cmd" in the edit box, that is, open the command line execution tool interface (speaking is the dos interface), type at the cursor Netdiag/xx, where xx is the option part, then press Enter, for example type netdiag/? After the carriage return, you can get all the help information, including the naming information of the test project.