Hello, the downloadlink isn’t aktive, only the message “download#11#image” displays. Please can you send me a link to the tool pvetcpping. Thank you. Greeting, Werner
good question. In the code that connects to the tcp port, I’m – getting the current time, in milliseconds (begintime) – connecting & reading the returning packets – getting the current time, in milliseconds (endtime) – calculating the delta (endtime – begintime) The only cases where the delta would be 0 is – if the begintime equals the endtime – if the endtime is less than begintime (so delta < 0). This could be an internal clock issue... In my code, I'm setting negative delta's to 0. Perhaps I should leave them as a negative value, but it would look bad, wouldn't it - if the delta value returned by the function could not be converted to an integer. (it's just a safety precaution in my code - it should never happen) Anyways - the code should return any values, including values below 16ms... unless the internal clock cannot handle it or unless it really is 0ms (starttime = endtime)... So I guess it's not a code limitation, but it may be a system limitation
Hi, great tool – I really like it. One question – I am getting some results of “0 ms” mixed in with 30’s and 40’s. I doubt the “0” is accurate so I assume there is a minimal resonse threshold that is accurately reported. I’ve seen exactly that with other similar utilities as well… anything under 16ms for example is just reported as zero. do you know what is the lowest time in ms that will be accurately reported?
there’s got to be a different reason for the behaviour you are seeing Results of a tcpping to my webserver, also on gigabit network : ——————————— PVE TCP Ping Utility Written by Peter Van Eeckhoutte http://www.corelan.be:8800 Version 1.0 ——————————— [+] Connecting to tcp port 8800 on host http://www.corelan.be... [+] Number of pings : Unlimited [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 114ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 2ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 1ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 1ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 2ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 1ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 1ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 2ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 1ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 1ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 1ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 1ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 4ms. [+] Probing host http://www.corelan.be on port tcp/8800 – Connect OK – 1ms. TCP Ping statistics for http://www.corelan.be port tcp/8800 Connects : 14, Success : 14, Failed : 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 114ms, Average = 9ms As you can see, the tcpping does report latency of less than 16 ms…
Right, thanks. I doubted it was a limitation in your code itself, but maybe there is an underlying limitation with the .Net stuff – how often it can get the cpu time or execution. I will be the first to tell you I don’t know enough to do more than ask silly questions so I will defer to you as the guru. I’ve tried it on several systems (PC’s and servers, XP, 2003, 32 & 64bit etc.) and get the same thing- never a result between 1-15 ms. Even when on the same Gb segment, 0 or 17+ and over the router where I expect 5-10 ms is the exact same results. Just curious, because what I really need to do immediately is quantify the latency through the firewall on 1433 is between 1-15ms. I can’t find anything that will do it. I like the tool and will keep it for use in other situations however!!! Cheers!
