Avatar of Eric_Price
Eric_Price
Flag for United States of America asked on

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.
VirtualizationSBSMicrosoft Server OS

Avatar of undefined
Last Comment
Philip Elder

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Philip Elder

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Eric_Price

ASKER
All very good ideas. Fortunately, Ive since resolved the issue

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!
Philip Elder

You are welcome. :)

P.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23