Static IP address in virtualized SBS 2011 not recognized as static by key services
I have a Windows 2011 SBS running as a guest VM on Windows 2008 R2 Hypervisor. There are two NICS in the server. One is dedicated to management, the other to the guest.
When the VM boots up it fails to assign the static IP address (192.168.0.7) to the virtual NIC. If you look in the GUI, its there. Sometimes, the DGW entry is missing. re-adding it causes it to stick, at least for a time. If you go to the command prompt and do a ipconfig the address is an APIPA.
If I do a
netsh interface ip set address name "local area connection" static 192.168.0.7 255.255.255.0 192.168.0.1
then the address will stick, can be pinged both locally and from computers on the same subnet, etc. The DHCP and DNS services though, even if restarted, fail to recognize it as an active card with a bound static IP.
Rebooting the server after doing this reverts back to the original problem.
I spent much of today ripping out the virtual NIC, recreating it in HyperV, and generally trying to clear what I assume is most likely some sick / corrupted registry entry, all to no avail. Anyone out there run into this, or have some ideas about what to do or how to narrow down the issue?
I was half tempted to restore from last nights backup (which allegedly was successful) but I didnt want to lose the email, and now of course there was work done on the server today (done while the workaround was in place). I probably should have just wiped it and gone on.
When the VM boots up it fails to assign the static IP address (192.168.0.7) to the virtual NIC. If you look in the GUI, its there. Sometimes, the DGW entry is missing. re-adding it causes it to stick, at least for a time. If you go to the command prompt and do a ipconfig the address is an APIPA.
If I do a
netsh interface ip set address name "local area connection" static 192.168.0.7 255.255.255.0 192.168.0.1
then the address will stick, can be pinged both locally and from computers on the same subnet, etc. The DHCP and DNS services though, even if restarted, fail to recognize it as an active card with a bound static IP.
Rebooting the server after doing this reverts back to the original problem.
I spent much of today ripping out the virtual NIC, recreating it in HyperV, and generally trying to clear what I assume is most likely some sick / corrupted registry entry, all to no avail. Anyone out there run into this, or have some ideas about what to do or how to narrow down the issue?
I was half tempted to restore from last nights backup (which allegedly was successful) but I didnt want to lose the email, and now of course there was work done on the server today (done while the workaround was in place). I probably should have just wiped it and gone on.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You are welcome. :)
P.
P.
ASKER
In the end, I ended up using a tool to programmatically clean out the registry and settings of all my old network information.
nvspscrub
It allowed me to do what I apparently could do manually. Or maybe I just got lucky. I linked to the tool though in case someone else comes along with the same problem.
Almost makes me pine for the old days of real network cards.
Almost.
Thanks again!