Differences

This shows you the differences between two versions of the page.

--- ping_test [2020/01/07 10:57 (4 years ago)] – kevin
+++ ping_test [2021/02/27 11:32 (3 years ago)] (current) – tanya
@@ Line 1: / Line 1: @@
 ====== Performing a Ping Test ======
-A 'ping' is a basic network test that will send messages across a network to a computer and measure the time lapsed from sending to receiving the messages.  It will recorder any packet loss and average trip times.
+See [[https://support.windwardsoftware.com/a/solutions/articles/66000475754]]
-To start the ping test, open the command prompt found using the Windows start button then select Run.  Enter the word 'cmd' into the Run box as shown in Figure 1.
-{{info_qa:databases:run_cmd.jpg|}}\\
-To perform the 'ping' test the word ping followed by the name of the server needs to be entered.  For example, if the server is named 'server' then **'ping server -t -l 2000'** will send a continuous test messages to the server with a packet size of 2000.  Let the test run for several minutes (or hours if you have time). You will have to hit CTRL and C on the keyboard to stop the test.
-In a successful test:
-  * The same number of packets received as 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 issues 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.
-{{::pingtest.jpg?700|}}
-<note tip>Increasing the buffer size of the ping test in the -l parameter will increase the load of the test.  Using a continuous ping test with a larger packet size could help identify a network issue.  Such as **ping -t -l 20000**
-</note>
-===== Possible causes of packet loss =====
-  - 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