A 'ping' is a basic network test that will send messages across a network to a computer and measure the time elapsed from sending to receiving the messages. It will record any packet loss and average trip times. The ping test is testing the UDP protocol of the TCP/IP stack. UDP compared to TCP does not re-transmit as when a package is lost or dropped, this can tell us something. A very small percentage of packet loss may not be something to worry about. Large amounts of packet loss could be a symptom of a hardware or network configuration issue.
How to execute a Ping Test
- Open the command prompt found using the Windows start button then select Run.
- Enter the word 'cmd' into the Run box and click OK.
- Note the date/time, workstation and server role along with IP's you are testing from and to.
- Type the command ping server -t -l 2000 where server is the IP or name of the server to test against.
- Let the test run for several minutes (or hours if you have time) or until a software event takes place such as System Five locking up. You will have to hit CTRL and C on the keyboard to stop the test.
- Note the date/time of test completion and collect the Ping statistics.
In a successful test:
- The same number of packets received as has been sent.
- There should be 0% or minimal packet loss. If there is sizable packet loss based on the time of the test then there could be a networking issue that needs further diagnosis.
- The ping latency should also not have large differences in minimum and maximum times.
- The ping test also measures time. Pinging a computer on the local network should show a response time less than 1 millisecond.
- In the screen shot below this server is located on a fast internet connection and has an average ping time of 19 ms.
Possible causes of Request timed out
If you are seeing Request timed out messages this indicates packet loss. A small percentage of packet loss is typically not something to worry about. Ensure you are testing with a large enough packet size as a standard ping test may not show a network issue as 32 bytes is a tiny packet as seen below.
3/20/2020 12:30:37 PM - Reply from 184.108.40.206: bytes=32 time=430ms TTL=43 3/20/2020 12:30:38 PM - Reply from 220.127.116.11: bytes=32 time=470ms TTL=43 3/20/2020 12:30:39 PM - Reply from 18.104.22.168: bytes=32 time=458ms TTL=43 3/20/2020 12:30:43 PM - Request timed out. 3/20/2020 12:30:45 PM - Reply from 22.214.171.124: bytes=32 time=456ms TTL=43 3/20/2020 12:30:46 PM - Reply from 126.96.36.199: bytes=32 time=498ms TTL=43
- The port on a switch (Try a different port or replace the switch)
- Unstable Switch or Power Supplies (Replace the switch)
- Routing tables (Incorrectly configured routers or switches)
- Network cables (Mice can chew on cables causing intermittent packet loss; replace with store-bought cables)
- Incorrect 10/100/1000 auto-detection of network speed on the server, workstation or switch (verify detection or manually set detection on the network card and switch)
- Failing network card that broadcasts and saturates the network with a packet storm for a duration of time. (Replace the network card with a different brand to ensure a different driver is being used)