Needing to run 'netsh int ip reset' frequently

Question

I've been having an issue where some days I will disconnect (briefly) from the internet every hour on the hour (for example, 12:05, 1:05, 2:05, etc etc).  After doing some research, I learned that going into cmd.exe and using 'netsh int ip reset' can fix it, and it does, at least for a time; the issue seems to come back fairly frequent (a few days to a week later).

My ISP told me that particular issue isn't on their end, as it has no function on the router or modem.  In short, what's causing this problem, and what can I do to fix it?

Answer 1

Yes.  The only thing that applies here is the "Local Area Connection".  DHCP is obviously enabled because you get an IP address at the onset.  Your problem seems to be centered around why it is not able to renew the IP Lease.

One work-around to your solution (i.e. does not fix your original problem but takes care of the effects) would be to place a home Router between your computer and your modem.  The router would handle the ISP IP address renewals  and you can set the router's local DHCP lease to weeks long or longer (or use a fixed IP address) which should all but eliminate your symptoms.

HTH,

  JW

Answer 2

I think what you're seeing indeed verifies that your problem is the inability to renew your DHCP IP lease.  If you have that error when doing it manually, the system will almost assuredly get the same error when trying to renew automatically.  You may see errors to that effect in the System Log.  From command prompt:

   eventwvr.msc  -> Windows Logs -> System

Your DHCP server should be listed in the "DHCP Server" line of the "ipconfig /all" command output.  You might try to ping that address and see if it responds.  The only thing I know to check is to verify that your "DHCP Client" service is still running.  (From command prompt:  'services.msc' and then find the "DHCP Client" line and verify that its status is "Started" and its Startup Type is "automatic". 

Another possibility is your Firewall Software.  Some problems like this have been attributed to firewall problems, but I would not expect than resetting your IP stack would clear this problem... but you can try temporarily disabling your firewall software and see if that helps.

Googling "Unable to contact DHCP Server" may lead to other solutions as well. 

One such response is:

  < http://forums.techguy.org/networking/1122889-unable-contact-your-dhcp-server.html >

where McAffe firewall was the problem and a special tool was needed to remove it.

HTH,

   JW

Answer 3

One possible explanation is the expiration of your DHCP IP address lease.  When you connect to your ISP, it assigns/leases you an IP address with an expiration date/time.  Since IP addresses are at a premium with ISPs, they often set a short lease -- one hour may be typical -- so that they may be able to more quickly recover addresses that weren't properly released.  If your computer is unsuccessful in renewing the lease before it expires, it is obliged to disconnect and stop using the internet until another lease can be negotiated.  Typical Windows behavior is to start negotiating a renewal of the lease when the lease is half-over.   If unsuccessful, it will continue to try to renew the lease up to the time it expires.

To verify:  If you enter the command:

    ipconfig  /all

you will see lines labeled "Lease Obtained" and "Lease Expires" in the listing with associated date/times.  If your connection drops at the "Lease Expires" time, then this may be your problem.  You should be able to manually renew your lease by entering the command:

    ipconfig  /renew

If this command succeeds, you should be able to enter another "ipconfig /all" command and see an updated "Lease Expires" line.  If that line doesn't update, then there may be a problem renewing your IP lease.  You can also try an "ipconfig /all" command when you are half-way to the time you originally saw and verify whether or not the Lease Expires time renewed automatically.

HTH,

  JW

Answer 4

Just so I'm working with the right information, under the Ethernet adapter Local Area Connection, it says DHCP is enabled.  Under the tunnel adapter isatap.home, it says it's not enabled; is that how it is supposed to be?

Answer 5

Thanks for the reply.

When trying to do the ipconfig /renew, I got the following message:

"An error occurred while renewing interface Local Area Connection : unable to contact your DHCP server.  Request has timed out."

Not entirely sure what that means, but I assume it doesn't fix the problem.

EDIT:

After running another reset, and trying the renew, I believe it functions properly; the Lease Expire time updates to an hour after I perform the renew command.  Not sure if this is what I want to see or not.