ping_test
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
ping_test [2020/03/23 10:37 (4 years ago)] – kevin | ping_test [2021/02/27 11:32 (3 years ago)] (current) – tanya | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Performing a Ping Test ====== | ====== Performing a Ping Test ====== | ||
- | A ' | + | See [[https://support.windwardsoftware.com/a/solutions/articles/66000475754]] |
- | + | ||
- | ===== How to execute a Ping Test ===== | + | |
- | - Open the command prompt found using the Windows start button then select Run. | + | |
- | - Enter the word ' | + | |
- | - 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**. | + | |
- | <note tip>The -t tells ping to perform | + | |
- | </note> | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | + | ||
- | {{:: | + | |
- | + | ||
- | <note tip> | + | |
- | </note> | + | |
- | + | ||
- | ===== 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. | + | |
- | + | ||
- | < | + | |
- | 3/20/2020 12:30:37 PM - Reply from 172.217.160.100: | + | |
- | 3/20/2020 12:30:38 PM - Reply from 172.217.160.100: | + | |
- | 3/20/2020 12:30:39 PM - Reply from 172.217.160.100: | + | |
- | 3/20/2020 12:30:43 PM - Request timed out. | + | |
- | 3/20/2020 12:30:45 PM - Reply from 172.217.160.100: | + | |
- | 3/20/2020 12:30:46 PM - Reply from 172.217.160.100: | + | |
- | </ | + | |
- | + | ||
- | - The port on a switch (Try a different port) | + | |
- | - Unstable Switch or Power Supplies (Replace switch) | + | |
- | - Routing tables (Incorrectly configured routers or switches) | + | |
- | - Network cables (Mice can chew on cables causing intermittent packet loss) | + | |
- | - Incorrect 10/100/1000 auto-detection of network speed on the server, workstation or switch | + | |
- | - Failing network card that broadcasts and saturates the network with a packet storm for a duration of time | + | |
- | + | ||
- | + |
ping_test.txt · Last modified: 2021/02/27 11:32 (3 years ago) by tanya