Limited connectivity on restart/NIC reset

TGSoldier said:

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.

squonksc said:

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

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

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

iseeuu said:

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~

Celeras said:

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

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.