WINDOWS PING Command Detailed
For Windows under the ping command, I have been familiar with it, but it is not a lot of people who can play the function of ping. Of course, I don't say that I can let Ping play the biggest function. I only use it. Ping this tool, also summarizes some little experience, now share it with you. Now I will tell you about the help of ping commands to tell you how I use ping, and ping can only be used after installation of the TCP / IP protocol: ping [-t] [-a] [-n count] [-l length] [-f] [-i ttl] [-V TOS] [-r count] [-s count] [[-j computer-list] | [-k computer-list]] [- w timeout] destination-list options: -t ping the specified host unchiL stopped.to see statistics and continuous - type control-break; to stop - type control-c. Do not stop Ping Local host until you press Control-C . This feature does not have special skills, but it can be used with other parameters will be mentioned below. -A resolve address to hostnames. Resolve the computer NetBIOS name. Example: c: \> ping -a 192.168.1.21 pinging iceblood.yofor.com [192.168.1.21] with 32 bytes of data: reply from 192.168.1.21: bytes = 32 TIME <10ms TTL = 254 reply from 192.168.1.21: Bytes = 32 TIME <10ms TTL = 254 reply from 192.168.1.21: bytes = 32 TIME <10ms TTL = 254 reply from 192.168.1.21: bytes = 32 TIME <10ms TTL = 254 ping statistics for 192.168.1.21: Packets: SENT = 4, Received = 4, Lost = 0 (0% Loss), Approximate Round Trip Times in Milli-Seconds: minimum = 0ms, Maximum = 0ms, Average = 0ms From above, IP is 192.168.1.21 Computer NetBIOS name Iceblood.yofor.com. -n count number of echo requests to send. Send count specified by the ECHO packet.
By default, only four packets are usually sent. You can define the number of sent by this command. It is very helpful to measure the network speed. For example, I want to test the average time of the return of 50 packets, how much time is How much is the fastest time, the slowest time can be learned by: C: \> ping -n 50 202.103.96.68 pinging 202.103.96.68 With 32 bytes of data: reply from 202.103.96.68: BYtes = 32 TIME = 50ms TTL = 241 Reply from 202.103.96.68: bytes = 32 time = 50ms TTL = 241 Reply from 202.103.96.68: bytes = 32 time = 50ms TTL = 241 Request timed out .................. Reply from 202.103.96.68:. bytes = 32 TIME = 50ms TTL = 241 reply from 202.103.96.68: BYtes = 32 Time = 50ms TTL = 241 ping statistics for 202.103.96.68: Packets: SENT = 50, Received = 48, LOST = 2 (4% loss), Approximate Round Trip Times In Milli-Seconds: Minimum = 40ms, Maximum = 51ms, Average = 46ms From the above I can know that in the process of sending 50 packets to 202.103.96.68, returning 48, two of which are unknown The reason is lost, and the return speed is the fastest speed is 40ms in the 48 packets, the at least 51ms, the average speed is 46ms. -l size send buffer size. Define the Echo packet size. In the default case, the packet size sent by Windows is 32byt, and we can also define its size, but there is a size limit, that is, the maximum can only send 65500byt, maybe someone will ask why it is 65500Byt, because The Windows Series systems have a security vulnerability (perhaps other systems) is that when the data packet sent by the other party is greater than or equal to 65532, the other party is very likely to block, so Microsoft has restricted this security vulnerability. Ping's packet size.
Although Microsoft has made this limit, this parameter is still very powerful after this parameter is still very powerful. For example, we can implement an aggressive command by mating -t parameters: (The following introduction is dangerous, only In the test, please do not easily apply to the other machines, otherwise the consequences are at your own risk) C: \> ping -l 65500 -t 192.168.1.21 pinging 192.168.1.21 with 65500 BYtes of data: reply from 192.168.1.21: bytes = 65500 time < 10ms TTL = 254 reply from 192.168.1.21: bytes = 65500 Time <10ms TTL = 254 ................ This will send a size of 65500BYT to 192.168.1.21 computers, if you only have one There may be no effect on the computer, but if there are many computers, you can make the other party completely paralyzed, I have done such a test, when I use more than 10 computer PING PING, less than 5 minutes, less than 5 minutes The network has been completely paralyzed, the network is severely blocked, and the HTTP and FTP services are completely stopped, and the power is not as small. -f set don't fragment flag in packet. Send "Do not segment" in the packet. In the general packet you send, you will be sent to the other party via routing segmentation, plus the route will not reside again. -i TTL TIME TO LIVE. Specifies the time for TTL values to stay in the other party. This parameter also helps you check the network operation. -V TOS TYPE OF Service. Set the Service Type field to the value specified by TOS. -r Count Record Route for Count HOPS. Record the route from the "Record Routing" field. In general, the packet you sent is to the other party through a route, but what is the route? Through this parameter, you can set the number of routes you want to detect, but the limit is 9, that is, you can only track 9 routes. If you want to detect more, you can implement it through other commands, I will Explain to everyone in future articles.
