How to Use Ping and tracert commands to detect packet loss

Note: Some time ago, I talked to my friends about how to monitor the packet loss rate in the WAN performance test. However, there is no mature idea.
Perhaps, although the ping method described in this article is not very mature, you can also consider it.
 

It is very difficult to test the packet loss of a broadband network connection from home. Packet Loss can occur on the line between your computer and the destination you are connecting to on the Internet.

Where is it. Possible causes of packet loss include: network congestion, router or switch overload, slow signal return time, and service provider or website hosting.

The company's communication priority.

No active measurement of the actual repeated transmission of TCP traffic (for home broadband network connections, such products are too expensive), it is difficult to determine whether repeated transmission has occurred. What you pointed out

The Mechanism Ping and tracking routing is the most useful tool to help home users determine where the speed of the Internet is slow. Ping to measure the signal between your computer and the IP address you want to connect

Round-trip time. Tracking routing is to measure the channel response time between the router on your computer and the IP address of the route you are tracking.

Use Ping

The best way to use ping to measure packet loss is to send a large number of ping commands to an IP address, and then check the ping commands that are not answered. If you send a pin 50 times quickly

G command,

You can check the number of times no response is returned and the number of times no response is returned as a packet loss. It may be worth worrying that no response is answered more than 5% times.

On a Windows computer, enter the following command after the command prompt to complete the task:

The "-n" switch in the Ping-N 50 (IP address or domain name, such as www.website.com) Command tells the number of times the ping command is sent. "50" indicates the number of times the ping command is sent.

Then you will get a test summary. This summary includes the number and percentage of lost items:

199.181.132.250:

Packet: Sent = 6, received = 6, lost = 0 (0%)

The approximate round-trip time is displayed in milliseconds (MS:

Min = 26 Ms, max = 29 Ms, average = 27 Ms

If you see a high average round-trip time (over 100 ms), this will also reduce your network download speed.

One way to eliminate faults in some parts of the network that cause packet loss is to ping each part of the channel. First, the local"

Default Gateway ". This is the first router to transmit all your data to the network. If the packet loss rate in this part is high, the problem lies in the network of your service provider.

.

Enter the "ipconfig" command after the Windows command prompt to find the IP address of your default router. The result is as follows:

Local Ethernet interface connection:

DNS suffix of the specific connection: domainname.com

IP address ......: 192.168.2.189

Subnet Mask...: 255.255.252.0

Default Gateway...: 10.10.0.1

Here you want to view the IP address of the default gateway. In the preceding example, 10.10.0.1 is used.

Use tracking Routing

You can use the tracking routing command at the end of the Windows command prompt to implement tracking routing. In Windows xp zh, this command is: tracert (IP address or host name)

Although the result does not show you packet loss, it can show you how the router response speed slows down in the path.

The output shows the response time of all routers. The following is an example:

5 MS 2 MS 3 MS malibu.domain.com [10.10.0.1]

10 MS 6 MS 7 MS 10.60.0.6

9 MS 7 MS 7 MS 10.20.0.1

6 MS 7 MS 7 MS x130.cd9e68.sj.concentric.net [205.158.104.130]

7 MS 7 MS 8 MS ge9-0.dcr2.dc-fremont-ca.us.xo.net [205.158.60.169]

7 MS 7 MS 7 MS ge2-0.dcr1.dc-fremont-ca.us.xo.net [65.106.2.205]

10 MS 7 MS 8 MS p5-1-0-2.rar2.sanjose-ca.us.xo.net [65.106.2.153]

10 MS 9 MS 11 MS Co., p1-0.ir1.paloalto-ca.us.xo.net. [65.106.5.178]

9 MS 10 MS 15 MS 206.111.12.114.ptr.us.xo.net [206.111.12.114]

9 MS 10 MS 10 MS svl-core-03.inet.qwest.net [205.171.205.29]

29 MS 28 MS 29 MS stl-core-02.inet.qwest.net [205.171.5.85]

30 MS 29 MS 29 MS sea-edge-03.inet.qwest.net [205.171.26.42]

* ** Request timed out.

* ** Request timed out.

28 MS 28 MS 29 MS sam.abcnews.go.com [199.181.132.250]

If you see that the route tracking round-trip time in the path exceeds 100 ms (10 s), this may cause the network transmission time to slow down.

In the above example, you can see that data is transmitted on many different networks (XO, qwest, ABC. This is a wonderful part of the Internet. The disadvantage is that a user cannot

Solve the problem of slow response time. The best starting point is to confirm that there is no packet loss between you and your service provider.