Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Connection Issues (Skype, AOL, Battlenet, etc)


  • Please log in to reply

#16
jimboa24

jimboa24

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts

Sorry for the late response, but life's been crazy the past week!

 

 

That does sound odd. Can you please execute the ping commands again? Just like in the first post. When using two connections like you probably did at the start, the IP network knows which link to use for ping's so that you don't see packetloss. I'd like to verify the connection again but with pings.

ping -t 192.168.1.254
ping -t 8.8.8.8

Awaiting your response. :)

 

Regards,

Olrik

 

 

here's the first results:

 

C:\windows\system32>ping -t 192.168.1.254
 
Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=2ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=9ms TTL=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
 
Ping statistics for 192.168.1.254:
    Packets: Sent = 45, Received = 45, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 9ms, Average = 0ms
 
Here's the second one:
 
C:\windows\system32>ping -t 8.8.8.8
 
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=40ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=38ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
 
Ping statistics for 8.8.8.8:
    Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 40ms, Average = 35ms
 

  • 0

Advertisements







Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP