Bizarre ping times

[Noozer]

While troubleshooting a connectivity issue to a particular website I came
across something I have never seen before. During a traceroute I am seeing
HUGE response times reported, even though the packets come back quickly.

See the trace and ping below. Why am I getting packets coming up at
4294967268 ms (almost 50 days)???


C:\Documents and Settings\Steve>tracert stardock.com

Tracing route to stardock.com [66.28.242.200]
over a maximum of 30 hops:

1 <1 ms 4294967268 ms 4294967268 ms 10.0.11.1
2 * * * Request timed out.
3 4294967276 ms 4294967277 ms 10 ms rd1so-ge3-0-0-2.cg.shawcable.net
[64.59.142.82]
4 9 ms 4294967277 ms 4294967276 ms rc1so-ge6-0.cg.shawcable.net
[66.163.71.129]
5 25 ms 4294967293 ms 4294967295 ms rc2nr-pos13-0.wp.shawcable.net
[66.163.76.86]
6 4294967293 ms 4294967292 ms 5 ms rc1sc-ge12-0-0.wp.shawcable.net
[66.163.73.170]
7 58 ms 22 ms 22 ms rc1sh-pos1-0-0.mt.shawcable.net
[66.163.77.170]


C:\Documents and Settings\Steve>ping 10.0.11.1

Pinging 10.0.11.1 with 32 bytes of data:

Reply from 10.0.11.1: bytes=32 time=1ms TTL=255
Reply from 10.0.11.1: bytes=32 time=-29ms TTL=255
Reply from 10.0.11.1: bytes=32 time=-29ms TTL=255
Reply from 10.0.11.1: bytes=32 time=-29ms TTL=255

Ping statistics for 10.0.11.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = -29ms, Average = 1073741802ms

 

[Chuck]

While troubleshooting a connectivity issue to a particular website I came
across something I have never seen before. During a traceroute I am seeing
HUGE response times reported, even though the packets come back quickly.

See the trace and ping below. Why am I getting packets coming up at
4294967268 ms (almost 50 days)???


C:\Documents and Settings\Steve>tracert stardock.com

Tracing route to stardock.com [66.28.242.200]
over a maximum of 30 hops:

1 <1 ms 4294967268 ms 4294967268 ms 10.0.11.1
2 * * * Request timed out.
3 4294967276 ms 4294967277 ms 10 ms rd1so-ge3-0-0-2.cg.shawcable.net
[64.59.142.82]
4 9 ms 4294967277 ms 4294967276 ms rc1so-ge6-0.cg.shawcable.net
[66.163.71.129]
5 25 ms 4294967293 ms 4294967295 ms rc2nr-pos13-0.wp.shawcable.net
[66.163.76.86]
6 4294967293 ms 4294967292 ms 5 ms rc1sc-ge12-0-0.wp.shawcable.net
[66.163.73.170]
7 58 ms 22 ms 22 ms rc1sh-pos1-0-0.mt.shawcable.net
[66.163.77.170]


C:\Documents and Settings\Steve>ping 10.0.11.1

Pinging 10.0.11.1 with 32 bytes of data:

Reply from 10.0.11.1: bytes=32 time=1ms TTL=255
Reply from 10.0.11.1: bytes=32 time=-29ms TTL=255
Reply from 10.0.11.1: bytes=32 time=-29ms TTL=255
Reply from 10.0.11.1: bytes=32 time=-29ms TTL=255

Ping statistics for 10.0.11.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = -29ms, Average = 1073741802ms

You have an out of sync clock - those are negative ping times. By any chance,
is this a dual processor system?

 

[Noozer]

You have an out of sync clock - those are negative ping times. By any
chance,
is this a dual processor system?

AMD Opteron 165 dual core processor.

I sync my clock to an NNTP time server on a regular basis. Unfortunately the
Internet Time tab does not indicate how far off the clock was when it does a
sync.

 

[Chuck]

AMD Opteron 165 dual core processor.

I sync my clock to an NNTP time server on a regular basis. Unfortunately the
Internet Time tab does not indicate how far off the clock was when it does a
sync.

Here you are. Just a little Googling on "negative ping times amd".
<http://wiki.ljackson.us/Negative_Ping_Time>
http://wiki.ljackson.us/Negative_Ping_Time
<http://forums.pcper.com/showthread.php?t=430695>
http://forums.pcper.com/showthread.php?t=430695
<http://forums.whirlpool.net.au/forum-replies-archive.cfm/581332.html>
http://forums.whirlpool.net.au/forum-replies-archive.cfm/581332.html