On Mon, 13 Feb 2006 09:32:52 -0000, "Roger Mills \(aka Tiscali Tim\)"
<(E-Mail Removed)> wrote:
It could be your MTU settings giving the problem or it could be slow
dns resolve. I would try the MTU first. see
http://help.expedient.net/broadband/mtu.shtml
>In an earlier contribution to this discussion,
>themillman <(E-Mail Removed)> wrote:
>
>> I've noticed problems with my bb connection. I can get online no
>> probs but when I play any online game it really stutters and ends
>> with me being kicked from the server, even though my ping is very
>> low. I've raised this with my ISP and have done several tests and
>> the results are very strange - look below:
>>
>> Reply from 195.149.33.68: bytes=32 time=-15ms TTL=61
>>
>> Reply from 195.149.33.68: bytes=32 time=-15ms TTL=61
>>
>> Reply from 195.149.33.68: bytes=32 time=14ms TTL=61
>>
>> Reply from 195.149.33.68: bytes=32 time=16ms TTL=61
>>
>> Reply from 195.149.33.68: bytes=32 time=47ms TTL=61
>>
>> Reply from 195.149.33.68: bytes=32 time=15ms TTL=61
>>
>> Reply from 195.149.33.68: bytes=32 time=15ms TTL=61
>>
>>
>>
>> Ping statistics for 195.149.33.68:
>>
>> Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
>>
>> Approximate round trip times in milli-seconds:
>>
>> Minimum = 14ms, Maximum = -14ms, Average = 8ms
>>
>>
>>
>> Tracing route to www-v.nildram.net [195.149.33.68]
>>
>> over a maximum of 30 hops:
>>
>>
>>
>> 1 31 ms 31 ms 31 ms my.router [192.168.1.1]
>>
>> 2 17 ms 17 ms 17 ms lo1-lon3-adsl20.nildram.net
>> [195.112.5.29]
>> 3 17 ms 17 ms 17 ms lon3-14.nildram.net [84.12.224.29]
>>
>> 4 4294967282 ms 17 ms 16 ms lon1-13.nildram.net
>> [84.12.224.18]
>> 5 4294967284 ms 18 ms 17 ms www1-v.nildram.net
>> [195.149.33.68]
>>
>>
>> Trace complete.
>>
>>
>>
>> I've never seen minus numbers in ping rate or such a high number. I'm
>> using a router (Draytek Vigor 2600G) and all was well until a few
>> days ago. Any suggestions would be appreciated.
>
>Very odd. You obviously can't have negative ping times! Chances are that
>it's a larger *positive* time than the software can handle, and is displayed
>as negative due to its twos-complement value.
>
>It's still odd though - because I would expect it to time out rather than
>report a very large (or negative) value. Have you set a timeout value with
>the -w parameter, rather than using the default? When it reports these large
>values, how long does it *actually* take to respond - assuming that you're
>watching it?