VM Server reboot has a 169. address.

[computertechguy]

We did a Physical to Virtual copy of a 2012 r2 Server, after the migration we ran an upgrade to 2022 Standard. When the Server reboots we can't connect to it from the network. I can ping the IP address but not the computer name. The server is technically offline when im on it in the VM ware dashboard. If I do an ipconfig I see the server has a 169. address even though the network adapter has a static ip.

The resolution is to log on and change the static ip to something other than what it was and apply, then go back to the original static ip and that works.

The only thing I can think of is the original server had dual nics and they werent bonded only one nic was connected.

So someone suggested maybe the second nic is in the hidden device manager but there isn't a hidden network adapter. Could be a registry item?

Any thoughts.

 

[Sky-Knight]

Use the VMWare console to access the VM's physical console, use the devmgr_show_nonpresent_devices flag to enable Device Manager to show hidden devices. Look in the networking section of device manager, uninstall every single actual NIC you see in there, all the ghosts too.

Then reboot, assuming the VMWare tools are installed, the NIC will reinstall itself. Reconfigure it with the appropriate IP address, and watch the VM work.

Once you get the server online, take yourself into the bathroom, find a large mirror, stare at yourself in the mirror, and slap yourself however many times it takes before you commit to NEVER EVER EVER migrate an out of support server to any platform ever again. Your time is valuable, your sanity matters, and going off the reservation is a money loser, not a money maker. Server 2012 in particular is very persnickety when P2Vd. You got lucky... not a bad thing to be, but you need to know that.

 

[computertechguy]

Use the VMWare console to access the VM's physical console, use the devmgr_show_nonpresent_devices flag to enable Device Manager to show hidden devices. Look in the networking section of device manager, uninstall every single actual NIC you see in there, all the ghosts too.

Then reboot, assuming the VMWare tools are installed, the NIC will reinstall itself. Reconfigure it with the appropriate IP address, and watch the VM work.

Once you get the server online, take yourself into the bathroom, find a large mirror, stare at yourself in the mirror, and slap yourself however many times it takes before you commit to NEVER EVER EVER migrate an out of support server to any platform ever again. Your time is valuable, your sanity matters, and going off the reservation is a money loser, not a money maker. Server 2012 in particular is very persnickety when P2Vd. You got lucky... not a bad thing to be, but you need to know that.

lol

 

[YeOldeStonecat]

I have seen that.....been a while, but yeah there's some "ghost" settings that come forward. I've done lots of "in place upgrades" before and it's gone smooth. And relocating a guest instance.....to either a new Hyper-V host, or a reloaded Hyper-V host, or...and upgraded Hyper-V host (it's all the same)...is a common thing that is normal.

If I recall, on the guest instance, fire up Device Mangler....have it show all hidden devices, and rip out all the NICs.
Bounce it...let it reload a NIC.

I'd also probably "rip out" the v switches in the Hyper-V host...and start from scratch.

This server guest instance, as you probably know, the old 169.254.xxx.xxx address is a self assigned address Windows does to create easy LANs without a DHCP server. Happens when it cannot get an answer from its ARPs (cry outs for a DHCP server). So...."what" is running DHCP for this LAN?

What "roles" does this server do? DC?