Windows 7 DHCP fails. With static IP I can ping but HTTP fails.

[njs]

I am having a VERY strange problem and I am at a complete loss for how to fix...

We recently had a power outage and after my PC rebooted it had no Internet access. Upon investigating I found DCHP had failed to get an address. I rebooted PC and router but problem persisted.

I finally tried a static IP (192.168.15.101) and then things got much stanger. I could ping the router (192.168.15.1) however I could NOT access its web interface (Chrome reports ERR_INTERNET_DISCONNECTED).

I've also tried:
disabling and re-enabling the interface.
deleting and re-adding the NIC.
turning off IPv6
safemode with networking.
netsh int reset all
netsh winsock reset

 

[njs]

Thanks for the further suggestions.

chkdsk reports 0 kb in bad sectors. "windows has checked the file system and found no problems."

msinfo32 lists afd as follows:

started=no, start mode=system, state=stopped, status=ok, error control=normal, accept pause=no, accept stop=no

Any idea how to make it start?

I will also look into trying a system restore...

 

[Saltgrass]

Open regedit and go to this location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\AFD

Then check and see if the BootFlags, Start, and Type are all shown as 1

You have also checked the Network Store Interface Service and the TCP/IP Protocol Driver?

Edit: I just noticed the listing for AFD shows the "Accept Stop" option shows as NO, where mine shows as yes. Pause shows as NO. Maybe this happened in some troubleshooting step, but it does show the settings are not default.

 

[Saltgrass]

Does anyone think re-registering the dhcpcore.dll would help?

 

[Trouble]

At this point I suspect that earlier suggestions with respect to a system restore (not likely, but maybe), a repair install (far more likely), or my own personal favorite a clean install would like resolve the issue much sooner and actually with less effort probably.
This seems to be one of those cascading problems were you address and fix an issue immediately in front of you only to find the the next layer under that one needs repair also, and on and on, like peeling back an onion. You may get lucking in short order or it may be a long, arduous and frustrating journey.

 

[njs]

Network Store Interface Service and TCP/IP Protocol Driver are both running.

AFD BootFlags, Start, and Type are all set to 1

I only have one restore point from 8/11/13 not long before the power outage. I can try it but it may be that the corruption occured before then and just did not manifest until the reboot from power outage as PC typically runs weeks without rebooting.

How do I reregister dhcpcore.dll? Any other ideas?

Thanks!

 

[njs]

system restore crashes with BSOD

 

[Saltgrass]

You would register the dhcpcore.dll with the following command in an administrative command prompt.

regsvr32.exe dhcpcore.dll

If you get an error, there are some comments about starting the command from another folder for a x64 bit system.

http://support.microsoft.com/kb/249873#method1

The fact a restore attempt will cause a Blue Screen is not a good sign.