Product specifications

Network and Switch Troubleshooting
34
where [System Name] is the network name of the remote system to which you are testing connectivity
or
ping [IP Address]
where [IP Address] is the IP address of the remote system to which you are testing connectivity.
To run the ping command:
1. Open an MS-DOS
®
command prompt window (click Start > Run and type cmd ).
2. At the command line, type the ping command (for example,
ping 192.168.10.5 ).
The ping result should resemble the following:
Reply from 192.168.10.5: bytes=32 time<10ms TTL=255
Reply from 192.168.10.5: bytes=32 time<10ms TTL=255
Reply from 192.168.10.5: bytes=32 time<10ms TTL=255
Reply from 192.168.10.5: bytes=32 time<10ms TTL=255
Four responses of “Reply from…” indicate the network is configured correctly and the originating and
destination hosts can see each other on the network.
If any one of the responses in the ping result says:
Request timed out.
or
Destination host unreachable.
it indicates the network is not configured correctly or there are other network problems. Some items that can
cause network problems are:
- Bad, loose, or incorrectly connected cables
- An incorrectly configured IP address or subnet mask on a local or remote system
- Excessive network traffic
Tracert
While ping can test for connectivity between two network hosts, tracert (short for “trace route”) can verify the
network path that the data uses to travel between the two hosts.
Because Avid editing applications are data intensive, it is important that large amounts of data be transferred
between the Avid ISIS and its clients in a timely fashion. An incorrectly configured network might get the data to
its destination, but be too slow for your application to work effectively.
You can use the tracert command to confirm that the data is traveling along an optimal path. In an Avid ISIS
workgroup, the Avid ISIS and its clients should send traffic directly to each other. Routers should not be used to
direct traffic between them.
It is possible for network traffic to take one path going to a system and a different path coming back. Therefore, it
is important to run tracert from both the Avid ISIS and its clients to test the data path in both directions.
As with ping, you can use many options with tracert. This section discusses two types of tracert syntax:
tracert [System Name]