This article has been archived. It is offered "as is" and will no longer be updated.
This article describes how to use the Network Diagnostics Tool (Netdiag.exe) on a computer that is running Microsoft Windows 2000. Netdiag.exe is a command-line tool that you can use to test the network connectivity of the computer. Netdiag.exe performs a series of tests to determine the state and functionality of your network client computer. You can use the results of these tests, and the network status information that is provided by Netdiag.exe, to isolate network and connectivity problems on your Windows 2000-based workstation or server.
Netdiag.exe is included with the Microsoft Windows 2000 Support Tools. To install the Windows 2000 Support Tools, you must run Setup.exe from the Support\Tools folder on the Windows 2000 CD-ROM. To download Netdiag.exe, visit the following Microsoft Web site:
You can use the following parameters with Netdiag.exe:
/q: Use this parameter to specify quiet output and display errors only.
/v: Use this parameter to run Netdiag.exe in verbose mode and to display information about the actions that are performed.
/l: Use this parameter to write output to the Netdiag.log file. The Netdiag.log file is created in the same folder in which you run Netdiag.exe.
/debug: Use this parameter to run Netdiag.exe in debug mode. This parameter specifies a more verbose output than when you use the /v parameter.
/d:domain_name: Use this parameter to locate a domain controller in the specified domain.
/fix: Use this parameter to correct issues with Domain Name System (DNS), domain controller tests and other issues, such as the following:
DNS Test If the computer is a domain controller, Netdiag.exe verifies all the DNS entries in the Netlogon.dns file to determine whether they are correct. Additionally, Netdiag.exe updates the appropriate entries if there is a problem.
Domain Controller Tests If the domain GUID that is cached in a local computer which is on your primary domain is different from the domain GUID that is saved in a domain controller, Netdiag.exe will try to update the domain GUID that is cached on the local computer.
/dcaccountenum: Use this parameter to enumerate the computer accounts of the domain controller.
/test:test_name: Use this parameter to specify the test or tests that you want to run, where test_name can be any one of the following values:
Autonet: Automatic Private IP Addressing (APIPA) address test Bindings: Bindings test Browser: Redir and Browser test DcList: Domain controller list test DefGw: Default gateway test DNS: Domain Name Service (DNS) test DsGetDc: Domain controller discovery test IpConfig: IP address configuration test IpLoopBk: IP address loopback ping test IPSec: Internet Protocol security (IPSec) security test IPX: Internetwork Packet Exchange (IPX) test Kerberos: Kerberos Test Ldap: Lightweight Directory Access Protocol (LDAP) test Member: Domain membership test Modem: Modem diagnostics test NbtNm: NetBIOS over TCP/IP (NetBT) name test Ndis: Netcard queries test NetBTTransports: NetBT transports test Netstat: Netstat information test NetWare: NetWare test Route: Routing table test Trust: Trust relationship test WAN: Wide Area Network (WAN) configuration test WINS: Windows Internet Naming Services (WINS) service test Winsock: Winsock test
To specify two or more tests, separate each /test:test_name item with a space. Note that the tests that you cannot skip will still be run.
/skip:test_name: Use this parameter to specify the test or tests that you do not want to run, where test_name can be any one of the tests listed earlier in the /test:test_name list.
To specify two or more tests, separate each /skip:test_name item with a space.
For more information about Netdiag.exe, see the W2rksupp.chm file. In a default installation of the Windows 2000 Support Tools, W2rksupp.chm is located in the Drive:\Program Files\Support Tools folder. In that folder, Drive is the drive on which Windows 2000 is installed.
For additional information about how to use Netdiag to troubleshoot network and connectivity issues, click the following article numbers to view the articles in the Microsoft Knowledge Base:
265706 DCDiag and NetDiag in Windows 2000 facilitate domain join and DC creation
257225 Basic IPSec troubleshooting in Windows 2000
216899 Best practice methods for Windows 2000 domain controller setup
250842 Troubleshooting Group Policy application problems
For additional information about how to install the Windows 2000 Support Tools, click the following article number to view the article in the Microsoft Knowledge Base:
301423 How to install the Windows 2000 Support Tools to a Windows 2000 Server-based computer