A client "The configuration and working conditions of the TCP/IP protocol on the 0th machine room can be directly ping the IP address of the machine on the machine, if the letter of success is returned
Information indicates that the IP address LB has been corrected. If it fails, check the configuration of the IP address. You can do it through the following steps: First, check the entire network, focus
Check whether the IP address is being used by other users, and then check whether the workstation is correctly connected to the network (in many cases, users are not logged into the network.
This situation will also occur in the network, which is a low-level error). Finally, check the I/0 address lIRQ and DMA values of network-E, whether these values occur with other devices.
There was a conflict. The last check is very important and is often overlooked by many users. This check must be performed even after the Ping is successful. Because when Ping
After the IP address of this machine is successful, it only means that there is no problem with the IP address configuration of this machine, but it does not mean that the network card configuration is completely correct. Although it is on this machine
You can see the computer name of the computer in "Online Neighbor", but it is impossible to connect with other users. I don't know where the problem lies. In fact, the problem is often the case.
On the network card.
Simply put, TTL's full time to Live means the survival cycle.
First of all, we need to explain that the ping command uses the network layer protocol ICMP, so TTL refers to the survival cycle of a network data packet (package) at a network layer. If you don’t understand this sentence, go back and review the OSI7 layer protocol first.
The first question is why there is a concept of survival cycle.
Obviously, a package takes a long path from one machine to another. Obviously, this path is not single, very complex, and there is a loop. If a packet enters the loop during transmission, if it does not terminate it, it will continue to loop. If many packets loop like this, then this is a disaster for the network. Therefore, it is necessary to set such a value in the package. Whenever the package passes through a node, the value is reduced by 1. Repeated operations may eventually lead to 2 results: the package reaches the destination when the value is still positive, or after passing a certain number of nodes, the value is reduced to 0. The former means that a normal transmission has been completed, and the latter means that the packet may have chosen a very long path or even entered the loop. This is obviously not what we expect. So when this value is 0, the network device will no longer pass the packet but will directly abandon it and send a notification to the packet's source address, saying that the packet is dead.
In fact, the TTL value itself does not represent anything. For users, the concern should be whether the package has reached the destination rather than after passing through several nodes. But the TTL value can still get interesting information.
Each operating system defines TTL value differently. This value can even be modified by modifying the network parameters of some systems. For example, Win2000 defaults to 128, and can also be modified through the registry. Linux is mostly defined as 64. However, generally speaking, few people will modify this value of their machine, which gives us the opportunity to roughly judge what operating system a machine is by echoing TTL.
Take two machines in our company as an example
See the following command
D:Documents and Settingshx>ping 61.152.93.131
Pinging 61.152.93.131 with 32 bytes of data:
Reply from 61.152.93.131: bytes=32 time=21ms TTL=118
Reply from 61.152.93.131: bytes=32 time=19ms TTL=118
Reply from 61.152.93.131: bytes=32 time=18ms TTL=118
Reply from 61.152.93.131: bytes=32 time=22ms TTL=118
Ping statistics for 61.152.93.131:
Packets: Sent = 4， Received = 4， Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 18ms， Maximum = 22ms， Average = 20ms
D:Documents and Settingshx>ping 61.152.104.40
Pinging 61.152.104.40 with 32 bytes of data:
Reply from 61.152.104.40: bytes=32 time=28ms TTL=54
Reply from 61.152.104.40: bytes=32 time=18ms TTL=54
Reply from 61.152.104.40: bytes=32 time=18ms TTL=54
Reply from 61.152.104.40: bytes=32 time=13ms TTL=54
Ping statistics for 61.152.104.40:
Packets: Sent = 4， Received = 4， Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Previous page123Next pageRead the full text