Ping Tool - Request Timeouts

Discussion in 'Colasoft Free Network Tools' started by Groots, Feb 2, 2010.

Thread Status:
Not open for further replies.
  1. Groots
    Offline

    Groots Registered Member

    I have just installed the Colasoft Ping Tool V 1.1 build 265 on Windows 7 and have noticed that I am seeing "Request timed out" for ping tests agains hosts on a subnets where it would be impossible for this to happen and the ping times are normally < 10ms. If I adjust the Option/Ping timeout from the default of 500 to >=1000 the tool reports no timeouts. This issue makes it impossible to check for packet loss with confidence. True packet loss would imply that a response to a ping is "lost" rather than the time it takes to get a response (round trip times) being exceeded. However for the purpose of a ping test, a measure of a round trip time exceeding the nominated timeout period would be considered a measure of packet loss. In any case, if the latter is the method for determining packet loss, there is a problem.
    Below is the result when pinging www.google.com:
    Colasoft Ping Tool:
    [2010-2-2 22:47:41]Reply form www.google.com: bytes = 64 time = 239ms TTL = 48
    [2010-2-2 22:47:43]Reply form www.google.com: bytes = 64 time = 239ms TTL = 48
    [2010-2-2 22:47:44]Reply form www.google.com: bytes = 64 time = 238ms TTL = 48
    [2010-2-2 22:47:46]Reply form www.google.com: bytes = 64 time = 238ms TTL = 48
    [2010-2-2 22:47:47]Reply form www.google.com: bytes = 64 time = 239ms TTL = 48
    [2010-2-2 22:47:49]Reply form www.google.com: bytes = 64 time = 239ms TTL = 48
    [2010-2-2 22:47:50]Reply form www.google.com: Request timed out.
    [2010-2-2 22:47:52]Reply form www.google.com: Request timed out.
    [2010-2-2 22:47:54]Reply form www.google.com: bytes = 64 time = 239ms TTL = 48
    [2010-2-2 22:47:55]Reply form www.google.com: bytes = 64 time = 239ms TTL = 48
    [2010-2-2 22:47:57]Reply form www.google.com: bytes = 64 time = 240ms TTL = 48
    [2010-2-2 22:47:58]Reply form www.google.com: bytes = 64 time = 240ms TTL = 48
    [2010-2-2 22:48:00]Reply form www.google.com: bytes = 64 time = 240ms TTL = 48
    [2010-2-2 22:48:01]Reply form www.google.com: bytes = 64 time = 239ms TTL = 48
    [2010-2-2 22:48:03]Reply form www.google.com: Request timed out.
    [2010-2-2 22:48:04]Reply form www.google.com: Request timed out.
    [2010-2-2 22:48:06]Reply form www.google.com: bytes = 64 time = 239ms TTL = 48

    From a command prompt:
    Pinging www.l.google.com [74.125.127.147] with 64 bytes of data:
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=238ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=240ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=238ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48
    Reply from 74.125.127.147: bytes=64 time=239ms TTL=48

    Ping statistics for 74.125.127.147:
    Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 238ms, Maximum = 240ms, Average = 238ms
  2. Colasoft Support
    Offline

    Colasoft Support Colasoft Moderator

    For Colasoft Ping Tool, as you see, the default setting of timeout is 500 ms. The Command Prompt default setting of timeout is 1000 ms. That makes the diffrence.
    You can manully change and save the setting if you want it keep the same with CMD.

    We also appreciate you mentioned it, and you are really a diligent guy. We will consider to adjust the default setting in future version.
  3. Groots
    Offline

    Groots Registered Member

    I apologise that I was not diligent enough to include the comand line use to perform the ping to verify that I had set the time out to the 500

    ping www.google.com -t -l 64 -w 500

    As I mentioned in the previous comment, if the time out of the Colasoft ping tool is set to a value greater than 500 and closer to 1000 then there is no packet loss.

    I also performed some test with a well known tool called Ping Plotter and can confirm that I do not get any dropped packets when using a time out of 500ms.
  4. Colasoft Support
    Offline

    Colasoft Support Colasoft Moderator

    Actually, you are really diligent and careful man, you test it with so many tools and post it as a problem here to discuss. Your attitude is worth emulating for us.

    Well, I suppose you ignored that the testing environment may quite not as the same each time. To be exact, you ping the domain at a different time, so the result is different.
  5. leadit
    Offline

    leadit Registered Member

    Hiya,

    I can also confirm that there is a problem I've run tests on both window XP, Vista, and 7
    Tested on 6 different machines (2 on xp, 2 on vista and 2 on 7)

    Both vista and 7 have this issue... I've tested this with 3 machines ( XP Vista and 7) pinging the same host at the same time with identical config and the only machine that doesn't drop packets is the XP install

    To extend on this I have also tested using the ping with Colasoft running concurrently with FREE IP Tools and then with tping... while running at the same time with the same settings (all with 1024 byte pings) the others have 0% loss from over 1000 pings but colasoft has 10% +

    I only discovered this after upgrading from XP to 7 and encountering loss to an address I checked frequently that always used to be flawless
Thread Status:
Not open for further replies.