Meru Technical Note - How to overcome the delay in Windows trying the next ping
How to overcome the delay in Windows trying the next ping.
Scope
KB ARTICLE TYPE: Troubleshooting
RELATED PRODUCTS: - MC1500, MC1550, MC3000, MC3200, MC4100, MC4200
RELATED SOFTWARE VERSIONS: 4.x, 5.x
KEYWORDS: loss, performance
Solution
By default windows waits for 4000(4seconds) for the Echo Reply message that corresponds to a given Echo Request message to be received. If the Echo Reply message is not received within this time-out, the "Request timed out" error message is displayed.
This setting can be changed using the –w switch. The timeout can be set to 999 milliseconds or lower, but windows will never try more frequently than once per second.
ping x.x.x.x –t –w 999
This can be helpful while troubleshooting performance issues and Ping is the basic tool to check the percentage loss.
While testing with ping command, the odd missing ping is acceptable. However the frequency of miss should not be greater than 1 per second. But by default, on a windows machine this stretches to 1 per four seconds due to the fact windows waits for a response to timeout before sending the next ping.
In such scenarios, the above command can be used to reduce the timeout value.
