This example is a scenario where you have a problem connecting
to a network resource. Receiving only a "Network path not found"
error message and no further assistance, you have no idea where to
start troubleshooting the problem.
Assuming that the reason for the failure in this case is that
the DNS server is down, the solution can be found easily with
Network Connectivity Tester.
C:\Program Files\Support Tools>netdiag
.......................................
Computer Name: BDOVER
DNS Host Name: bdover.reskita.microsoft.com
System info : Windows 2000 Server (Build 2467)
Processor : x86 Family 6 Model 6 Stepping 0, GenuineIntel
List of installed hotfixes :
Q147222
Netcard queries test . . . . . . . : Passed
[WARNING] The net card 'Intel(R) PRO/100+ Management Adapter' may not be wor
king.
Per interface results:
Adapter : Local Area Connection
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : bdover
IP Address . . . . . . . . : 10.10.1.51
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 10.10.1.77
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Skipped
[WARNING] No gateways defined for this adapter.
NetBT name test. . . . . . : Passed
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Adapter : Local Area Connection 2
Netcard queries test . . . : Failed
NetCard Status: DISCONNECTED
Some tests will be skipped on this interface.
Host Name. . . . . . . . . : bdover
Autoconfiguration IP Address : 169.254.74.217
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . :
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{A2D04C22-3BB8-4FA0-B7DA-414DC1DD08A7}
NetBT_Tcpip_{56079E37-8246-4712-8B36-F503FF6F9873}
2 NetBt transports currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Failed
[FATAL] NO GATEWAYS ARE REACHABLE.
You have no connectivity to other network segments.
If you configured the IP protocol manually then
you need to add at least one valid gateway.
NetBT name test. . . . . . . . . . : Passed
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the name
'bdover.reskita.microsoft.com.'. [ERROR_TIMEOUT]
The name 'bdover.reskita.microsoft.com.' may not be registered in DNS
.
[WARNING] The DNS entries for this DC cannot be verified right now on DNS
server 10.10.1.77, ERROR_TIMEOUT.
[FATAL] No DNS servers have the DNS records for this DC registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{A2D04C22-3BB8-4FA0-B7DA-414DC1DD08A7}
NetBT_Tcpip_{56079E37-8246-4712-8B36-F503FF6F9873}
The redir is bound to 2 NetBt transports.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{A2D04C22-3BB8-4FA0-B7DA-414DC1DD08A7}
NetBT_Tcpip_{56079E37-8246-4712-8B36-F503FF6F9873}
The browser is bound to 2 NetBt transports.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Failed
Secure channel for domain 'RESKITA' is to '\\a-dcp.reskita.microsoft.com'.
[FATAL] Cannot set secure channel for domain 'RESKITA' to PDC emulator. [ERR
OR_NO_LOGON_SERVERS]
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC 'a-dcp.reskita.microsoft.com'.
[WARNING] Failed to query SPN registration on DC 'a-dc1.reskita.microsoft.com'.
[WARNING] Failed to query SPN registration on DC 'a-dc3.reskita.microsoft.com'.
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Passed
Service status is: Started
Service startup is: Automatic
IPSec service is available, but no policy is assigned or active
Note: run "ipseccmd /?" for more detailed information
The command completed successfully
When executed in this scenario, the tool shows that the network
adapter protocol, bindings, and IP address tests succeed. The DNS
ping test fails, and reports that the DNS server could not be
contacted. With this information, the user knows that either the
DNS server address is incorrect, or that the DNS server is not
responding for some unknown reason. Since the DNS address is also
displayed as output, it can easily be verified for correctness.
With the problem isolated, a Network Administrator can perform
additional troubleshooting to determine why the DNS server is
down.
