Limited connectivity on restart/NIC reset

[Celeras]

Any time I restart windows 7 or reboot my NIC, my connection comes back with Limited Connectivity. I can solve this(the only "solution" ive found) by rebooting my router once everything is on and get my connection, but its becoming quite the nuisance. The router shouldnt be the problem, as there are other computers/boots connected that dont have this issue.

Event log (Microsoft-Windows-DHCP Client Events/Admin) : Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x001A4D4F62E8. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

Please note that is NOT the error from DHCPv6(just DHCP under log name, not DHCPv6). The message is identical from what I can see, but thats not the source. And yes Ive already tryed disabling IPv6 without any success.

I've tryed pretty much everything the first 20 pages of google has suggested to me. I dont think its too much to ask, being able to access the DHCP server and have internet after rebooting, without having to reboot the router afterwards. Any ideas?

 

[iseeuu]

Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x001A4D4F62E8. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

A DHCP error with one computer should not require you to reset the router. What happens when you "release" then "renew" the network ip address from the mis-behaving computer?

 

[Celeras]

A DHCP error with one computer should not require you to reset the router. What happens when you "release" then "renew" the network ip address from the mis-behaving computer?

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig /release

Windows IP Configuration

An error occurred while releasing interface Local Area Connection : An address h
as not yet been associated with the network endpoint.

An error occurred while releasing interface Loopback Pseudo-Interface 1 : The sy
stem cannot find the file specified.


C:\Windows\system32>ipconfig /renew

Windows IP Configuration

An error occurred while renewing interface Local Area Connection : The data is i
nvalid.

An error occurred while releasing interface Loopback Pseudo-Interface 1 : The sy
stem cannot find the file specified.

[edit] Obviously, the above is when attempting this while I have the limited connectivity. It works fine when the net is connected after rebooting the router. Should be obvious, but wanted to make sure that was clear

 

[iseeuu]

Have you already tried flushing the arp cache?

In an elevated command prompt type arp -d*

I found this and more at Technet.

 

[Celeras]

Gave it a shot, whatever that was intended to do didn't work, and I believe it caused a step backwards.

Usually to test for solutions, I just reboot and get my limited connectivity on an 'Unidentified Public Network'. From here, rebooting the router would fix the problem. However after issuing the arp -d * command, I degraded to limited connectivity on a perpetually 'Identifying......' network. Rebooting the router from here didn't fix anything, and I was stuck. To resolve this, I had to reboot my NIC, which got me back to the 'Unidentified Public Network'. Then I rebooted the router again, got my connection back, and typed this reply to you

Thank you for the effort thus far, any other suggestions?

 

[Celeras]

SOLUTION

Alright, explain this. I'm messing around with game installations, not concerned with this problem at the time. I have to reboot, ok. Limited Connectivity, Unid'd network, same as its been.

I look over at the other PC connected to the router. I dont know why, but I turn it off. I must've read something on google somewhere that sparked this thought. Follow these chains of events.

-I reboot. I have limited connectivity, unid'd network.
-Instead of rebooting the router to get my connection back like usual, I think to turn the other PC off.
-I reboot my NIC, connected.
-I reboot my PC to see if it was a fluke, connected.
-I turn the other PC back on, it connects fine over there, and im still connected.
-I reboot my NIC, limited connectivity, unid'd network.
-I reboot my PC, limited connectivity, unid'd network.

At this point, I think I get what's going on. Rebooting the router was the only way I could fix the problem I was having because my connection was being established at the same time as the other PC. Once that other PC got a connection, if anything happened to mine.. it was gone and I couldnt get it back without starting fresh or loading first.

So now I'm wondering wtf is going on with this other PC, and it takes me all of 10 seconds of sitting on it (it's not mine) to see a potential problem. Nintendo Wifi Connector, and a Local Area Connection(2).

-Limited Connectivity, unid network.
-Reboot nic x2, still limited connectivity.
-Kill the Wifi thing and disable Local Area connection(2).
-Reboot nic, tada.

I mean.. it makes sense. Maybe not in computer speak, but logically. To me anyway, lol. But I think back to pre-7 installation (when the problem began) and wonder why this didn't happen before? I dont have an answer for that. Do you? Because i'd love to hear it. Ive rebooted a million times with that PC on(its always on), and ive never had this issue.

Deep down, is it a Windows 7 problem? You tell me. But that's how I fixed it, by playing with the computer across the room running XP SP2

 

[iseeuu]

-Kill the Wifi thing and disable Local Area connection(2).
-Reboot nic, tada.

Deep down, is it a Windows 7 problem? You tell me. But that's how I fixed it, by playing with the computer across the room running XP SP2

Good morning Celeras (it is morning for me!). I would like to thank you for explaining how you solved your problem. Doing so may assist many others coming here for help. Reading your solution may lead them to a fix of their own.

I am glad you were able to resolve the router DHCP name corruption issue. I believe the problem is with the router, though. Routers should be able to communicate and provide DHCP to all computers. Mine does. As I don't know what router you are using, I can't say definately it is the problem. You could check with the manufacturer for a firmware update. Or it could just be the Win XP's multiple nics causing the confusion?

By way of explanation, Microsoft says this about arp cache: "Flush ARP cache Sometimes, an ARP cache entry can become stale and communication cannot occur again until the bad ARP cache entry expires."

Similar steps would include flushing the DNS as well. There are many steps to diagnosing network issues and MS Technet is very helpful there.

It has been a pleasure working with you, come back any time. Remember, you get better help when you supply as many details as you can. Check my computer specs at the lower left for an example.

Robert

 

[SquonkSC]

I am still trying to figure out what he meant by "rebooting my NIC".?:shock:

Well, what ever, he solved it more or less.

 

[zigzag3143]

I am still trying to figure out what he meant by "rebooting my NIC".?:shock:

Well, what ever, he solved it more or less.

He must have rebooted his Nic in safe mode

K

 

[TGSoldier]

If you're on desktops and not moving around.. Hit up everyone with a static ip.. Pretty sure no more problems there anymore

 

[iseeuu]

If you're on desktops and not moving around.. Hit up everyone with a static ip.. Pretty sure no more problems there anymore

Good suggestion. Solution has some advantages.

 

[Celeras]

I am still trying to figure out what he meant by "rebooting my NIC".?:shock:

Well, what ever, he solved it more or less.

Enable/disable the NIC in Device Manager. Sorry if I described it poorly

Good morning Celeras (it is morning for me!). I would like to thank you for explaining how you solved your problem. Doing so may assist many others coming here for help. Reading your solution may lead them to a fix of their own.

I am glad you were able to resolve the router DHCP name corruption issue. I believe the problem is with the router, though. Routers should be able to communicate and provide DHCP to all computers. Mine does. As I don't know what router you are using, I can't say definately it is the problem. You could check with the manufacturer for a firmware update. Or it could just be the Win XP's multiple nics causing the confusion?

Just for conclusiveness for people searching with similar problems, the PCs in questioned are wired to a DAP-1522(Firmware 1.02) working as a bridge, receiving a wireless signal from a DIR-615(B2, Firmware 2.25). I don't believe either to be a problem, though their are probably some firmware updates available.

It also should be noted that while I was experiencing this problem, it persisted through when I booted to Vista, not just on the Windows 7 drive. However I still feel it was something I did during the 7 installation that triggered the problem as it was fine prior, even if that something was merely turning off the PC to mount my new HDD. (I recall reading somewhere that the Win7 drivers broke the internet for someone dual booting 7/vista before too, and that using the XP 64bit drivers was the solution. Trigger could be anything at this point)

Regardless, glad I got it fixed. And hopefully others having problems may get a light bulb from reading this. Thanks for the assistance~

 

[iseeuu]

Regardless, glad I got it fixed. And hopefully others having problems may get a light bulb from reading this. Thanks for the assistance~

You are most welcome!

Robert

 

[shaneh20]

Possible fix that worked for me

For anyone else having this annoying problem, here's how I solved it for my setup...

I've got an Intel 6230 mini-pci Wifi card in my laptop and was getting this same error whenever i resumed from hibernation. I noticed in my network adapters there is a 'Microsoft Virtual Wifi Miniport Adapter' which I thought looked suspicious/odd/useless, so I disabled it and viola! Problem went away and everything still works ok.

From reading around, it seems this is used to allow your pc to act as a wifi access point. I'd never need this, so no harm done.