Internet disconnects and won't reconnect until restart

I've been having this problem for only the last week or so where my internet will stop working until I restart my computer, even though it says I am connected and internet is available.

The problem is not with my modem or my router. The internet works fine on every other computer.
I've run multiple antivirus scans on multiple programs. Clean.
Drivers are up to date.

Sometimes it disconnects after five minutes, sometimes forty, sometimes hours.
I'm at a loss. Any ideas?
 
"I've run multiple antivirus scans on multiple programs. Clean"... How many "antivirus" programs do you have installed. What are these programs... the names?
 
When it disconnects get us some information:

get a command prompt (start->search, enter CMD and press return)
then enter
ipconfig /all >myTCP.txt
open that file, copy all the content and paste it back into your follow-up reply.

I suspect you're loosing the DHCP server
 
Avast and microsoft security essentials. and aight I'll try that next time it goes down. I also just rebuilt my computer from scratch and that didn't solve it. :(
 
"Avast and Microsoft security essentials"... Pick one only and completely un-install the other! Then do what jobeard said
 
I only had one installed at a time.

Windows IP Configuration

Host Name . . . . . . . . . . . . : KENJUMMA
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Qualcomm Atheros AR8161/8165 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
Physical Address. . . . . . . . . : 94-DE-80-A8-EC-D4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::20c3:1458:35ac:6532%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, February 24, 2014 6:20:37 PM
Lease Expires . . . . . . . . . . : Monday, February 24, 2014 7:50:38 PM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 177528448
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-9C-26-CB-94-DE-80-A8-EC-D4
DNS Servers . . . . . . . . . . . : 65.32.5.111
65.32.5.112
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{9072C21D-9687-477D-9320-56373BA1C6E9}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:2c77:2cad:9fc5:2ef2(Preferred)
Link-local IPv6 Address . . . . . : fe80::2c77:2cad:9fc5:2ef2%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
 
Code:
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
those are quite normal - - pointing to your router.

Have you power-cycled that router {recently or ever}? Do so. wait at least 30 seconds before restarting it.

When the symptom reoccurs, get the command prompt again and enter
IPCONFIG
you should get back
Code:
IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, February 24, 2014 6:20:37 PM
Lease Expires . . . . . . . . . . : Monday, February 24, 2014 7:50:38 PM
Default Gateway . . . . . . . . . : 192.168.0.1

THEN FOLLOW with
IPCONFIG /RELEASE
IPCONFIG /RENEW
and lastly
IPCONFIG /ALL

you should have the default gateway dhcp & dns addresses again.

If not, then there's a problem in the router
 
"should fix it permanently?" Hmm. Even when you have a hair permanent, you still go back again - -
The Rock of Gibraltar might be, but I would never call anything with computers permanent :sigh:
 
Last edited by a moderator:
Ok so, when I did that I got up to ipconfig /renew but when I entered that command, a line popped up and said "Windows IP Configuration" and I couldnt enter anything else.
 
Oops, and then a few minutes after that it says "An error occured while renewing interface Local Area Connection : unable to contact your dhcp server. Request has timed out."
 
Fpfpffpffft ok I reset my winsock and then tried it again when I lost the internet and it worked this time. everything is the same as it was before soooo, does that mean the problem isnt fixed?
 
I was one tab of youtube and google when it shut down that time. Why would it be the memory? I've never had a problem before this last week and a half.
 
NO! it's not memory.

You have two different issues
  1. frequent disconnects
  2. failure to honor a release/new cycle
Let's talk about your ISP connection - -
WHO is it and what type {Dsl, Cable, Satellite} ?

DSL has special considerations which requires a filter on every device connected to the phone line OTHER than the modem. This is a direct contributor to the disconnect problem (*IF* you're using dsl)

You ought to get the make/model number of the router and look for a firmware update (regardless of {Dsl, Cable, Satellite} as you ought to be able to renew).

Here's a test you can run to determine if your router needs to reassemble packets:

get the command line and enter:
ping -f -l 1500 google.com​
the character between the -F and google is an ELL in lower case.

My results are:
C:\Users\Jeff>ping -f -l 1500 google.com
Pinging google.com [74.125.224.168] with 1500 bytes of data:
Packet needs to be fragmented but DF set.​

Now repeat that test by reducing the 1500 by -8 until it replies
C:\Users\Jeff>ping -f -l 1440 google.com
Pinging google.com [74.125.239.0] with 1440 bytes of data:
Reply from 74.125.239.0: bytes=1440 time=18ms TTL=53​

My test of the value just above that produced:
C:\Users\Jeff>ping -f -l 1448 google.com
Pinging google.com [74.125.239.0] with 1448 bytes of data:
Request timed out.​

When packets get fragmented, the router needs to do extra work and not only is that a performance hit, but also a vector for network virus' - - so help the poor thing along by setting the MTU in the router itself.

Set the MTU to the highest value that replies with times and does not timeout.
 
Thanks jobeard! That works beautifully! It even seems like the internet is faster!!! I'm a networking study monger now! :)
 
Jobeard,I was having the same issue.Internet disconnecting for no apparent reason.Tried your solution (ipconfig commands) and it worked! Thanks very much.
 
NO! it's not memory.

You have two different issues
  1. frequent disconnects
  2. failure to honor a release/new cycle
Let's talk about your ISP connection - -
WHO is it and what type {Dsl, Cable, Satellite} ?

DSL has special considerations which requires a filter on every device connected to the phone line OTHER than the modem. This is a direct contributor to the disconnect problem (*IF* you're using dsl)

You ought to get the make/model number of the router and look for a firmware update (regardless of {Dsl, Cable, Satellite} as you ought to be able to renew).

Here's a test you can run to determine if your router needs to reassemble packets:

get the command line and enter:
ping -f -l 1500 google.com​
the character between the -F and google is an ELL in lower case.

My results are:
C:\Users\Jeff>ping -f -l 1500 google.com
Pinging google.com [74.125.224.168] with 1500 bytes of data:
Packet needs to be fragmented but DF set.​

Now repeat that test by reducing the 1500 by -8 until it replies
C:\Users\Jeff>ping -f -l 1440 google.com
Pinging google.com [74.125.239.0] with 1440 bytes of data:
Reply from 74.125.239.0: bytes=1440 time=18ms TTL=53​

My test of the value just above that produced:
C:\Users\Jeff>ping -f -l 1448 google.com
Pinging google.com [74.125.239.0] with 1448 bytes of data:
Request timed out.​

When packets get fragmented, the router needs to do extra work and not only is that a performance hit, but also a vector for network virus' - - so help the poor thing along by setting the MTU in the router itself.

Set the MTU to the highest value that replies with times and does not timeout.

I'm having the same problem. However, when I try this process above, I get "Packet needs to be fragmented but DF set" when I ping 1394, but "Request timed out" when I ping 1394.
I'm also getting a DCLhelper error message when I restart my computer. Don't know if it related.
 
I'm having a similar problem and would like to ask if the same methods can be used here as described before. The thing I'm getting is that when I'm playing online game randomly my Internet cuts out. The strange thing is that the icon on the work bar says that the Internet is still coming in and even the connection with the game remains normal. However opening pages in browsers, loging in to steam or other launchers or basically a tempting to create new Internet connections fails even if whatever games I connected to before this randomly happens still remain open. I tried to switch my connection from my virgin media router to a hotshot on my phone that is network 3 but it won't create any new connections and the pc has to be restarted. This makes me wonder if doing anything to the router would help if switching connections has no effect until restart.
 
Back