Strange Pinging Results
Results 1 to 3 of 3

Thread: Strange Pinging Results

  1. #1
    Join Date
    Jun 2003
    Posts
    142

    Question 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

    Any help would be greatly appreciated!

    Thanks,
    Walugi

  2. #2
    Join Date
    Apr 2000
    Location
    Tulsa, OK
    Posts
    657

    Re: Strange Pinging Results

    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.

  3. #3
    Join Date
    Jun 2003
    Posts
    142
    Oops sorry, the "other" ip is actaully the ip of the host computer, i didn't realise i forgot to post it.

    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

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •