standerr
Well-Known Member
Hhhmm, that's a bit weird.
What happens when you ping 169.1.5.52?
Look if we leave the ping going for a little longer
Code:
C:\Windows\system32>ping 169.1.5.52 -t
Pinging 169.1.5.52 with 32 bytes of data:
Reply from 169.1.5.52: bytes=32 time=29ms TTL=60
Reply from 169.1.5.52: bytes=32 time=28ms TTL=60
Reply from 169.1.5.52: bytes=32 time=28ms TTL=60
Reply from 169.1.5.52: bytes=32 time=28ms TTL=60
Reply from 169.1.5.52: bytes=32 time=28ms TTL=60
Reply from 169.1.5.52: bytes=32 time=41ms TTL=60
Reply from 169.1.5.52: bytes=32 time=29ms TTL=60
Reply from 169.1.5.52: bytes=32 time=244ms TTL=60
Reply from 169.1.5.52: bytes=32 time=234ms TTL=60
Reply from 169.1.5.52: bytes=32 time=425ms TTL=60
Reply from 169.1.5.52: bytes=32 time=30ms TTL=60
Reply from 169.1.5.52: bytes=32 time=58ms TTL=60
Reply from 169.1.5.52: bytes=32 time=29ms TTL=60
Reply from 169.1.5.52: bytes=32 time=52ms TTL=60
Reply from 169.1.5.52: bytes=32 time=29ms TTL=60
Reply from 169.1.5.52: bytes=32 time=46ms TTL=60
Reply from 169.1.5.52: bytes=32 time=28ms TTL=60
Reply from 169.1.5.52: bytes=32 time=40ms TTL=60
Reply from 169.1.5.52: bytes=32 time=174ms TTL=60
Reply from 169.1.5.52: bytes=32 time=149ms TTL=60
Reply from 169.1.5.52: bytes=32 time=141ms TTL=60
Reply from 169.1.5.52: bytes=32 time=265ms TTL=60
Reply from 169.1.5.52: bytes=32 time=138ms TTL=60
Ping statistics for 169.1.5.52:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 425ms, Average = 99ms
Control-C