3Com 3C10402B Administrator's Manual page 489

(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
■
(Ping times can differ because the network often routes individual
packets along different internal routes depending on congestion.)
4 Use on the command line:
tracert
tracert <192.168.1.190>
5 Interpret trace results:
The command lists every IP gateway it encounters as it tries to
tracert
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
across a network, it can be useful for comparing the performance of
alternative internet service providers.
NetMeeting Connections
You can also check H.323 voice packets that are sent between systems
that are running Microsoft NetMeeting. ConneXtions software requires it
to run G.711 (CCITT mu-law) or G.723.1 compression. NetMeeting is
available on the Resource Pack CD, or it is available as a free download
from
www.microsoft.com
You can conduct the NetMeeting connect test from the operating system
that runs the ConneXtions software, or from another PC on the LAN.
You must run NetMeeting and ConneXtions on different PCs.
In addition to the NetMeeting software, participating computers need an
audio card with a headset (or speakers) and a microphone. The audio
card must support full-duplex 64 Kbps transfers.
but preferably less than 300 ms.
10 ms
(example IP address)
command reveals the chain of logical connections
.
Checking Connections 489