Strange Pinging Results

Printable View

February 26th, 2004, 06:20 AM
walugi

Strange Pinging Results

For a while now i've been having problems with my home lan, and i was stuffing around with netstat earlier and i did a

ping www.google.com -t

on Command Prompt. It came up with these results:

Reply from 169.254.123.84: bytes=32 time<1ms TTL=64
Reply from 169.254.123.84: bytes=32 time<1ms TTL=64
Reply from 169.254.123.84: bytes=32 time<1ms TTL=64
Reply from 169.254.123.84: bytes=32 time<1ms TTL=64
Reply from 169.254.123.84: bytes=32 time<1ms TTL=64
Reply from 169.254.123.84: bytes=32 time<1ms TTL=64
Reply from 169.254.123.84: bytes=32 time<1ms TTL=64
Reply from 169.254.123.84: bytes=32 time<1ms TTL=64
Reply from 66.102.7.104: bytes=32 time=248ms TTL=240
Reply from 66.102.7.104: bytes=32 time=356ms TTL=240
Reply from 66.102.7.104: bytes=32 time=275ms TTL=240
Reply from 66.102.7.104: bytes=32 time=206ms TTL=240
Reply from 66.102.7.104: bytes=32 time=1344ms TTL=240
Reply from 66.102.7.104: bytes=32 time=459ms TTL=240
Reply from 66.102.7.104: bytes=32 time=338ms TTL=240

The TTL is inconsistent and i was wondering how i could fix this because as it turns out when the TTL is 64 i am cut off from the internet. :(

The twist to this is that although browsing and email etc don't work games like Counter Strike do :confused:

Any help would be greatly appreciated!

Thanks,
Walugi
February 26th, 2004, 06:26 AM
TeeDub

Re: Strange Pinging Results

Quote:

Originally posted by walugi
Reply from 169.254.123.84: bytes=32 time<1ms TTL=64
Reply from 169.254.123.84: bytes=32 time<1ms TTL=64
Reply from 66.102.7.104: bytes=32 time=248ms TTL=240
Reply from 66.102.7.104: bytes=32 time=356ms TTL=240

What have you posted? 1) Servers to not change IP address mid-ping and 2) 169.254.xxx.xxx is not a "real" IP address.
February 26th, 2004, 06:44 AM
walugi

Oops sorry, the "other" ip is actaully the ip of the host computer, i didn't realise i forgot to post it. :confused:

That seems to be the actual problem. I did the same ping and the host had no problems with the consistency, they were all

Reply from 66.102.7.104: bytes=32 time=248ms TTL=240
Reply from 66.102.7.104: bytes=32 time=356ms TTL=240

Sorry about that guys :rolleyes: