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)

Started by jimboa24 , Aug 25 2014 09:11 PM

  • Please log in to reply

#1
jimboa24
Posted 25 August 2014 - 09:11 PM

jimboa24

    New Member

  • Member
  • Pip
  • 8 posts

So any program I use refuses to stay connected to the internet. Battlenet (the app Blizzard uses for WoW, Hearthstone, Diablo 3, etc) is in a never-ending state of connecting and disconnecting and trying to play WoW and Hearthstone is impossible. Skype keeps disconnecting and reconnecting too, and I've completely given up on AOL and yahoo messengers. Using an ethernet cable or connecting wirelessly yields the exact same results. My computer is the only computer using the network that is experiencing problems; my roommate is connecting to Battlenet wirelessly and is having NO connection problems at all. Plus, I've only had issues for the past 2-3 weeks. Malwarebytes and Spybot have found no viruses on my computer, but something is very wrong and it's driving me insane.

 

What might be the source of my issues?? I've made no major changes to my PC in the past 3 weeks, but something is disrupting any program that requires a constant connection!


  • 0

Advertisements

#2
Artellos
Posted 25 August 2014 - 11:57 PM

Artellos

    Tech Secretary

  • Global Moderator
  • 3,915 posts

Welcome Jimboa24,

 

Sounds like you already did a fair bit of troubleshooting yourself. Is there anything that you know of that you installed in the past 2-3 weeks?

 

Can you open a new command prompt for every command below?

 

ping -t 127.0.0.1
ping -t 8.8.8.8

 

Let them run for a while and try to connect to WoW for example. After WoW has given you issues, go back to 1 of the command prompts and press "CTRL + C" to stop the running Ping. Then right click the command window and choose "Select All" then hit Enter. Then come back to this post and paste the information into the post. After you've posted the first one, rince and repeat for the leftover command prompt.

 

I would also like the output of one other command, namely;

 

ipconfig /all

 

Please copy and paste this information into the post just like you should with the ping commands.

 

Regards,

Olrik


  • 0

#3
jimboa24
Posted 26 August 2014 - 12:25 PM

jimboa24

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts

Thanks! Here's the results of ping -t 127.0.0.1:

 

C:\windows\system32>ping -t 127.0.0.1

 
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
 
Ping statistics for 127.0.0.1:
    Packets: Sent = 260, Received = 260, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\windows\system32>
 
And here's the results for ping -t 8.8.8.8 :
 
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=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=40ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=61ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=41ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=39ms TTL=48
Reply from 8.8.8.8: bytes=32 time=41ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=57ms TTL=48
Reply from 8.8.8.8: bytes=32 time=89ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=103ms TTL=48
Reply from 8.8.8.8: bytes=32 time=86ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=39ms TTL=48
Reply from 8.8.8.8: bytes=32 time=63ms TTL=48
Reply from 8.8.8.8: bytes=32 time=75ms TTL=48
Reply from 8.8.8.8: bytes=32 time=296ms TTL=48
Reply from 8.8.8.8: bytes=32 time=40ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=63ms TTL=48
Reply from 8.8.8.8: bytes=32 time=42ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=38ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=71ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=40ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=38ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=35ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
Reply from 8.8.8.8: bytes=32 time=36ms TTL=48
 
Ping statistics for 8.8.8.8:
    Packets: Sent = 123, Received = 123, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 296ms, Average = 41ms
Control-C
^C
C:\windows\system32>
 
Lastly, here's the results for ipconfig /all :
 
Microsoft Windows [Version 6.2.9200]
© 2012 Microsoft Corporation. All rights reserved.
 
C:\windows\system32>ipconfig /all
 
Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : owner
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : gateway.pace.com
 
Ethernet adapter Bluetooth Network Connection:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : BC-85-56-F0-AE-E0
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Wireless LAN adapter Local Area Connection* 11:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : BC-85-56-F0-AE-D9
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Ethernet adapter Ethernet:
 
   Connection-specific DNS Suffix  . : gateway.pace.com
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 78-E3-B5-C2-D4-B1
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a0fc:1138:658f:668f%13(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.71(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, August 25, 2014 10:50:48 PM
   Lease Expires . . . . . . . . . . : Wednesday, August 27, 2014 11:17:47 AM
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCP Server . . . . . . . . . . . : 192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 393798581
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-52-D8-AA-78-E3-B5-C2-D4-B1
 
   DNS Servers . . . . . . . . . . . : 192.168.1.254
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
Wireless LAN adapter Wi-Fi:
 
   Connection-specific DNS Suffix  . : gateway.pace.com
   Description . . . . . . . . . . . : Ralink RT3290 802.11bgn Wi-Fi Adapter
   Physical Address. . . . . . . . . : BC-85-56-F0-AE-DF
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::51b0:c2cc:7cd4:981c%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, August 25, 2014 11:06:39 PM
   Lease Expires . . . . . . . . . . : Wednesday, August 27, 2014 11:06:38 AM
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCP Server . . . . . . . . . . . : 192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 297301567
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-52-D8-AA-78-E3-B5-C2-D4-B1
 
   DNS Servers . . . . . . . . . . . : 192.168.1.254
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
C:\windows\system32>

  • 0

#4
Artellos
Posted 29 August 2014 - 05:55 PM

Artellos

    Tech Secretary

  • Global Moderator
  • 3,915 posts

Hello again,

 

From what I can see, you have your WiFi and a cable connected, is this true?

 

If the answer is yes, can you disable the WiFi adapter for troubleshooting purposes?

 

Regards,

Olrik


  • 0

#5
jimboa24
Posted 29 August 2014 - 07:27 PM

jimboa24

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts

Well, no. My computer can either connect directly to my router via ethernet cable, or it can connect wirelessly. It can't do both at once. It's only connected via ethernet cord. My router/modem combo was provided via AT&T. It started to have this problem, so they sent me a new one. It didn't help.


  • 0

#6
Artellos
Posted 30 August 2014 - 07:35 AM

Artellos

    Tech Secretary

  • Global Moderator
  • 3,915 posts

Hello again,

 

Your "ipconfig" output shows me different. It shows me that your wireless is connected as well as your ethernet connection. This can cause issues when your computer doesn't know when to send it out of what interface. Can you disconnect your ethernet cable completely and run an ipconfig again?

 

Regards,

Olrik


  • 0

#7
jimboa24
Posted 31 August 2014 - 10:53 PM

jimboa24

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts

Here ya go:

 

C:\Users\user>ipconfig /all
 
Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : owner
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : gateway.pace.com
 
Ethernet adapter Bluetooth Network Connection:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : BC-85-56-F0-AE-E0
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Wireless LAN adapter Local Area Connection* 11:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : BC-85-56-F0-AE-D9
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Ethernet adapter Ethernet:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : gateway.pace.com
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 78-E3-B5-C2-D4-B1
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Wireless LAN adapter Wi-Fi:
 
   Connection-specific DNS Suffix  . : gateway.pace.com
   Description . . . . . . . . . . . : Ralink RT3290 802.11bgn Wi-Fi Adapter
   Physical Address. . . . . . . . . : BC-85-56-F0-AE-DF
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::51b0:c2cc:7cd4:981c%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, August 31, 2014 2:29:48 AM
   Lease Expires . . . . . . . . . . : Monday, September 1, 2014 8:32:05 PM
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCP Server . . . . . . . . . . . : 192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 297301567
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-52-D8-AA-78-E3-B5-C2-D4-B1
 
   DNS Servers . . . . . . . . . . . : 192.168.1.254
   NetBIOS over Tcpip. . . . . . . . : Enabled

  • 0

#8
Artellos
Posted 01 September 2014 - 02:29 AM

Artellos

    Tech Secretary

  • Global Moderator
  • 3,915 posts

Please shut down the wireless connection completely, and then connect the ethernet cable back in the PC. Then please run another ipconfig.

 

It does look like your wireless automaticall takes over the connection, and that can cause routing/switching problems.

 

Regards,

Olrik


  • 0

#9
jimboa24
Posted 01 September 2014 - 03:45 AM

jimboa24

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts

How do I do that? I don't know how to force the router to stop broadcasting wirelessly. Also, I'm still experiencing the disconnect/reconnect issues even when only using the wireless connection.


  • 0

#10
Artellos
Posted 01 September 2014 - 03:52 AM

Artellos

    Tech Secretary

  • Global Moderator
  • 3,915 posts

Hello again,

 

You don't have to stop the router broadcasting the wireless. In the bottom right corner of your Windows screen, you can see the action tray. There should be something where you can see your network connections. When connected by wireless it is shown to be 5 bars of signal strength indicating how strong the signal is. If you click on that you can disconnect the wireless connection.

 

Also, the disconnections might be caused by the wireless signal itself. Wireless has a tendency to cause packet-loss in an environment where there is a lot of interference.

 

Regards,

Olrik


  • 0

Advertisements

#11
jimboa24
Posted 02 September 2014 - 01:02 AM

jimboa24

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts

Ok, I made sure that my computer doesn't have the wireless password so it can't be connecting to my router. An odd thing: after connecting my computer to my ethernet and disabling its ability to connect to my router, it started to work fine for about an hour, but then it went right back its disconnect/reconnect pattern. Here's the ipconfig results:

 

C:\Users\user>ipconfig /all
 
Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : owner
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : gateway.pace.com
 
Ethernet adapter Bluetooth Network Connection:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : BC-85-56-F0-AE-E0
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Wireless LAN adapter Local Area Connection* 11:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : BC-85-56-F0-AE-D9
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Ethernet adapter Ethernet:
 
   Connection-specific DNS Suffix  . : gateway.pace.com
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 78-E3-B5-C2-D4-B1
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a0fc:1138:658f:668f%13(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.71(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, September 2, 2014 12:40:16 AM
   Lease Expires . . . . . . . . . . : Wednesday, September 3, 2014 12:40:15 AM
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCP Server . . . . . . . . . . . : 192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 393798581
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-52-D8-AA-78-E3-B5-C2-D4-B1
 
   DNS Servers . . . . . . . . . . . : 192.168.1.254
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
Wireless LAN adapter Wi-Fi:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : gateway.pace.com
   Description . . . . . . . . . . . : Ralink RT3290 802.11bgn Wi-Fi Adapter
   Physical Address. . . . . . . . . : BC-85-56-F0-AE-DF
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Edited by jimboa24, 02 September 2014 - 01:10 AM.

  • 0

#12
Artellos
Posted 02 September 2014 - 11:45 PM

Artellos

    Tech Secretary

  • Global Moderator
  • 3,915 posts

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


  • 0

#13
Intalex
Posted 05 September 2014 - 09:16 PM

Intalex

    Member

  • Member
  • PipPip
  • 16 posts

My two suggestions would be to:

 

a. Check from the device manager to see if the computer's network adapters are functioning properly. Assuming that they are then

b. Try entering manually the ip address from your network settings. http://www.wikihow.c...s-on-a-Computer


Edited by Intalex, 05 September 2014 - 09:17 PM.

  • 0

#14
Artellos
Posted 06 September 2014 - 02:09 PM

Artellos

    Tech Secretary

  • Global Moderator
  • 3,915 posts

Intalex,

 

With all due respect. If a network adapter would be working improperly, it would show in the ping test that we've performed. And changing the way you get your IP address (from DHCP to static) will not make a difference in actual network connectivity. That will only make sense if your computer is getting an APIPA address because the DHCP server is not functioning properly.

 

Regards,

Olrik


  • 0

#15
Intalex
Posted 07 September 2014 - 12:36 PM

Intalex

    Member

  • Member
  • PipPip
  • 16 posts

Artellos- You are correct about the network adapter. I missed that part. :)

 

As far as the statically assigning an ip. I have seen this work when two or more computers are "fighting" for the same ip (ip conflict) causing network drops. But I don't think this is the issue here either.

 

I think that you might be on to something with the ping tests. Possible even do a traceroute as the problem might be internet/network related.


  • 0
Back to Networking · Next Unread Topic →




Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Geeks to Go Community
  2. → Hardware
  3. → Networking

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP