Solving the problem of network packet loss and fault judgment method

Let's start by recognizing what a packet loss is, and what kind of phenomenon is being lost to the network:

Data is transmitted on the Internet on a packet-by-unit basis, with a packet of NK, no more, no less. That is to say, no matter how good the network line is, how strong the network equipment, your data will not be linear (like a telephone) transmission, there is always a hollow in the middle. Packet transmission, it is impossible to complete, because of a variety of reasons, there will always be a certain loss. In this case, the Internet automatically allows both computers to replenish and retransmit the package according to the protocol. If the network line is good and fast, the loss of the package is very small, and the work of the replenishment and retransmission is relatively easy to complete, so it is possible to approximate the transmitted data as lossless. However, if the network line is poor, the amount of data loss will be very large, the replenishment of the work is not 100% completed. In this case, the data transmission will be empty, resulting in packet loss.

The speed of opening a Web page is very slow, sometimes there will be some content or the whole page can not show the problem; QQ, such as instant messaging tools such as frequent drop line or prompt landing timeout, has been set to automatically obtain IP address, but not every time the normal access to download files slow ... A large part of these failures are caused by the loss of packets.

[Next]

Let's take a look at how to confirm, detect, and resolve the packet loss problem:

The common way to test the loss of a packet is to test it by using the ping command, as shown in the Request timed out. Indicates that a packet loss is occurring at this time. Reply from 220.181.6.19:bytes=32 time=10ms ttl=55 Similar display indicates a normal data transfer. In addition, some tool software can also be tested, the specific test methods can be seen in the software use of the documentation, this does not do too much elaboration.

As mentioned earlier, loss of packet failure is mostly caused by the following problems: Worm, network cable Connection is too long (indoor theory of effective transmission distance of 100 meters, but the actual application is generally not more than 50 meters), network cable failure (including crystal head metal oxidation and other failures), operating system itself failure, network card failure ( Because the network card working frequency does not match the work frequency of the net equipment caused the fault, such as Gigabit network card with hundreds of devices, etc., may also be a physical failure of the network card, such as equipment, such as natural aging or encounter lightning, network equipment failure (equipment work environment impact, such as the environment is too humid, dry or electromagnetic interference serious, etc., It may also be due to device hardware failure), network operators line problems.

The workaround does not compare to the following failures: After disconnecting from the network in Safe mode, check the virus, appropriate to reduce the length of the network cable, checking the network cable and the production of Crystal Head, reinstall the operating system, adjust the network card or networking equipment to work at the same frequency, replace the network card, change the use of networking equipment environment or replace network equipment,