Wierd ping reply from 2000sp4

Anyone seen this before? It only happens when ping from this device to any
other device on the network.

From this device to the switch it is directly connected to:
C:\>ping 10.208.65.1
Pinging 10.208.65.1 with 32 bytes of data:
Reply from 10.208.65.1: bytes=32 time=172063320ms TTL=255
Reply from 10.208.65.1: bytes=32 time=-172063321ms TTL=255
Reply from 10.208.65.1: bytes=32 time=-172063322ms TTL=255
Reply from 10.208.65.1: bytes=32 time=-172063323ms TTL=255

Ping statistics for 10.208.65.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 172063320ms, Maximum = -172063321ms, Average = 987710162ms


THIS DEVICE IS ACROSS THE WAN: (as you can see it is not consistant)
C:\>ping 10.208.6.1
Pinging 10.208.6.1 with 32 bytes of data:
Reply from 10.208.6.1: bytes=32 time=148ms TTL=247
Reply from 10.208.6.1: bytes=32 time=172083565ms TTL=247
Reply from 10.208.6.1: bytes=32 time=171ms TTL=247
Reply from 10.208.6.1: bytes=32 time=148ms TTL=247

Ping statistics for 10.208.6.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 148ms, Maximum = 172083565ms, Average = 43021008ms

C:\>ping 10.208.6.1
Pinging 10.208.6.1 with 32 bytes of data:
Reply from 10.208.6.1: bytes=32 time=172083971ms TTL=247
Reply from 10.208.6.1: bytes=32 time=149ms TTL=247
Reply from 10.208.6.1: bytes=32 time=-172083819ms TTL=247
Reply from 10.208.6.1: bytes=32 time=172084128ms TTL=247

Hi Robert,

This looks like a CPU issue. Obviously, the ping times are being calculated
incorrectly. I would run some diagnostic tests on the CPU and the BIOS.
Also, try pinging the server's own IP address and see if it happens.

I hope this helps!

--
Greg Lindsay [MSFT]

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

"Robert Gray" <Robert (E-Mail Removed)> wrote in message
news:0EB29B71-118D-464D-871B-(E-Mail Removed)...
> Anyone seen this before? It only happens when ping from this device to
> any
> other device on the network.
>
> From this device to the switch it is directly connected to:
> C:\>ping 10.208.65.1
> Pinging 10.208.65.1 with 32 bytes of data:
> Reply from 10.208.65.1: bytes=32 time=172063320ms TTL=255
> Reply from 10.208.65.1: bytes=32 time=-172063321ms TTL=255
> Reply from 10.208.65.1: bytes=32 time=-172063322ms TTL=255
> Reply from 10.208.65.1: bytes=32 time=-172063323ms TTL=255
>
> Ping statistics for 10.208.65.1:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 172063320ms, Maximum = -172063321ms, Average = 987710162ms
>
>
> THIS DEVICE IS ACROSS THE WAN: (as you can see it is not consistant)
> C:\>ping 10.208.6.1
> Pinging 10.208.6.1 with 32 bytes of data:
> Reply from 10.208.6.1: bytes=32 time=148ms TTL=247
> Reply from 10.208.6.1: bytes=32 time=172083565ms TTL=247
> Reply from 10.208.6.1: bytes=32 time=171ms TTL=247
> Reply from 10.208.6.1: bytes=32 time=148ms TTL=247
>
> Ping statistics for 10.208.6.1:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 148ms, Maximum = 172083565ms, Average = 43021008ms
>
> C:\>ping 10.208.6.1
> Pinging 10.208.6.1 with 32 bytes of data:
> Reply from 10.208.6.1: bytes=32 time=172083971ms TTL=247
> Reply from 10.208.6.1: bytes=32 time=149ms TTL=247
> Reply from 10.208.6.1: bytes=32 time=-172083819ms TTL=247
> Reply from 10.208.6.1: bytes=32 time=172084128ms TTL=247
>