mikeymikec
Lifer
I've worked around the issue with a script that runs on every boot but it's an odd one and I hope that someone has an idea for what might be going on.
One thing I know for certain is that the problem is not a hardware related; I've tried two different NICs and different drivers. Both NICs are Intel ones (the current one is an Intel Gigabit CT Desktop adapter).
When I boot the machine, Windows starts fine, I log in, the network icon looks normal, I do ipconfig /all asap and the configuration is as it should be, but within about a minute the configuration is lost. It was then acquiring a DHCP address but I responded to that with a registry tweak to disable acquiring an address via DHCP (mainly out of curiosity), to which it responded by simply having no IP configuration at all.
The script I wrote (as a last resort) uses netsh to set the IP configuration a minute after bootup and it appears to work flawlessly. I wish I had spotted and troubleshooted this issue through to completion earlier (ie. before I had started domain migrations between a 2000 Server and an interim test Win2008 Server while having the 2012 Server serve company files, then migrating domain control until the 2012 Server), but once I had tried all my options driver wise I figured that a new NIC ought to solve the problem, except it didn't). In short, with the amount of work I've put into this server and the fact that it's live I don't intend to reinstall it in the hope that a reinstall fixes the problem. Any other ideas would be appreciated.
Nothing else is running/installed on the server except Windows.
One thing I know for certain is that the problem is not a hardware related; I've tried two different NICs and different drivers. Both NICs are Intel ones (the current one is an Intel Gigabit CT Desktop adapter).
When I boot the machine, Windows starts fine, I log in, the network icon looks normal, I do ipconfig /all asap and the configuration is as it should be, but within about a minute the configuration is lost. It was then acquiring a DHCP address but I responded to that with a registry tweak to disable acquiring an address via DHCP (mainly out of curiosity), to which it responded by simply having no IP configuration at all.
The script I wrote (as a last resort) uses netsh to set the IP configuration a minute after bootup and it appears to work flawlessly. I wish I had spotted and troubleshooted this issue through to completion earlier (ie. before I had started domain migrations between a 2000 Server and an interim test Win2008 Server while having the 2012 Server serve company files, then migrating domain control until the 2012 Server), but once I had tried all my options driver wise I figured that a new NIC ought to solve the problem, except it didn't). In short, with the amount of work I've put into this server and the fact that it's live I don't intend to reinstall it in the hope that a reinstall fixes the problem. Any other ideas would be appreciated.
Nothing else is running/installed on the server except Windows.
Last edited:
