Ping Test

Run a Ping Test

Run a Ping Test on Windows OS

To run an advanced ping on a Windows XP Machine:

1. Click on START -> RUN...
2. Type "cmd" (For older windows versions, type in "command")
3. Type "ping -l 600 -n 100" followed by an address that is able to respond to pings
   • Examples: "ping -l 600 -n 100 62.54.44.34" or "ping -l 600 -n 100 64.54.44.34"
   • The option -l sets the buffer size in bytes for the ping command
   • The option -n sets the number of echo request to send
   

Above is an advanced ping to www.yahoo.com. In this example, all pings resulted in a successful reply. When troubleshooting dropped audio, you will be looking for a "Request Timed Out" in place of the reply. Sustained periods of timeouts, will result in sustained periods of audio dropout. Timing is important when troubleshooting dropped audio, so it is best to troubleshoot while the customer is experiencing this issue.

Run a Ping Test on Mac

1. Click on the Finder Application.
   
2. Locate the Network Utility. This program can usually be found by double clicking on Application -> Utilities -> Network Utility in the Finder Application NOTE: If the network Utility can not be found by this method, entering "Network Utility" in the search field of the finder will locate the program.
   
3. Click on the Ping button on the Network Utility. You will have to specify the Domain or IP address to ping. You can also specify the amount of pings that you would like to run or run a constant ping. The results will be returned in the text box.
   
   NOTE: The PING functionality in "Network Utility" will only check connections that are Ethernet based. If the connection is wireless based, this utility will not work

Run the Trace Route Command

1. The Tracert command can be used in Windows XP to diagnose latency and packet loss issues between a specific source (computer on customer local network) to a destination (outside web address, such as www.yahoo.com).
2. Tracert command identifies each router or subnet between a specific source and destination and displays any latency or packet loss issues that exist between each one of these routers and the source computer.
3. From the tracert results you should be able to determine if the latency and/or packet loss issues are occurring on:
   • Customers local network (Modems, Routers, Switches, Hubs)
   • Internet Service Providers Network
4. When troubleshooting audio issues, you should always trace route to the media relay IP address
   1. Open up a command prompt window.
      1. Click on the 'Start' button.
      2. Select the 'Run...' option.
      3. When prompted to open a program type cmd .
      4. Click on the OK button.
   2. On the command line type tracert Domain Name.
      Example: tracert 64.54.44.34

The following describes the test result:

1. Command Line:
   • tracert: executable command
   • 64.54.44.34: parameter to execute command upon
2. Tracert Results:
   • Column 1: Shows the numbers assigned to each hop returned from the trace.
   • Column 2, 3 and 4: Each column shows the results of the one ping that is run from the source computer to each hop returned from the trace. A total of 3 pings are run to each hop.
   • Column 5: Shows the details, such as IP Address and/or Domain Name, of each hop returned from the trace.
3. Example of Good Tracert Results with no latency or packet loss:

 

4 .   Example of Bad Tracert Results with high latency and packet loss: