3Com NBX 100 Administrator's Manual - page 431
Checking Connections
431
To check a connection:
1 Access the DOS command prompt from the DOS shell in Windows.
2 Enter
ping
on the command line:
ping <192.168.1.190>
(sample IP address)
3 Interpret ping results:
a
Request timed out
(all four times)
■
Ping reached the network but couldn’t connect to the host
■
(No such address; or the device is down.)
■
Initial request timed-out
■
(It is normal for a first ping to fail and subsequent pings to
succeed.)
■
Subsequent requests timed-out
■
(Indicates some packet loss. Rerun using the “-n 100” option. The
“request timed out” number represents the percentage of lost
packets. These packets could have been lost in either direction.)
b
Destination host not reachable
■
Ping couldn’t negotiate a path to the specified address
(
PC is not plugged into LAN, incorrect gateway address in route,
or a firewall blocked the ping.)
c
Approximate round-trip times in milliseconds
■
Ping time greater than
10 ms
but preferably less than 300 ms.
(Ping times can differ because the network often routes individual
packets along different internal routes depending on congestion.)
4 Use
tracert
on the command line:
tracert <192.168.1.190>
(example IP address)
5 Interpret trace results:
The
tracert
command lists every IP gateway it encounters as it tries to
reach the specified destination. It also includes the number of times (3)
required to reach each intermediate gateway. If a network connection
failure occurred in route, this command indicates where it occurred.
Because the
tracert
command reveals the chain of logical connections
across a network, it can be useful for comparing the performance of
alternative internet service providers.