To do a ping test in Windows (10), please follow some steps below:
Open the Windows Search Bar. You can do this by clicking the magnifying glass icon in the bottom-left corner of your screen.
Then type CMD into the search bar and click Open. This will open a Command Prompt window with a black background, white text, and a flashing cursor.
Type ping followed by a space and the DNS address
Finally, hit Enter on your keyboard and wait for the ping test results.
When you do a ping test on a Windows PC, you will see the results for four different ping tests. Each test will tell you the ping time in milliseconds (ms) and how many packets were received or lost. You will also see the minimum, maximum, and average ping response times.
Here are the most common error messages you will see if your ping test returned failed results:
Request timed out: This means the ping test took longer than the default limit of 4,000 milliseconds (4 seconds). This could be caused by network congestion, a firewall set to stop specific traffic, defective cables or ports, and more.
Unknown host: This error message means that the requested host name is not recognized. Check that the name is entered correctly and that your router is functioning properly. If you are having problems with your router, check out our guide on how to reset your router here.
TTL expired in transit: The TTL you see after your ping time for each test refers to the number of “hops” that your packet is allowed to make before being discarded. So, this error message means that your packet exceeded the maximum number of allowable hops.
General failure: This either means your computer does not have the proper TCP/IP settings or that there might be a problem with your local area network (LAN) adapter or drivers, such as your router or WiFi card.
<destination> is unreachable: This message means that there is no route to the destination. If the message says, “Reply from <destination>: Destination Host Unreachable,” that means that there was a routing problem at the remote router, not with the <destination> itself.
If you see one of these error messages, you might need to troubleshoot network issues. You can try to ping other devices or other domains to see if the problem persists. This will help you determine whether the problem is with your device or with your network connection.