Koldov Posted July 17, 2023 Posted July 17, 2023 I decided that I should bite the bullet and update our servers last night (I'd done a couple of the less important VMs last week with no issues), so I logged on from home but it appeared that the servers had decided to update themselves, however I tried to RDP into one of the VMs and couldn't connect. So I logged into the host and went through VM manager only to find the VM had no network... After trying various troubleshooting (and checking the other VM) I remembered that a long time ago, I had done an in-place upgrade to Server 2019 on the host. This had the unfortunate effect of installing different NIC drivers and also renaming them... very unhelpful as it messed up the VMs networking. I got it sorted, but as usual in a panic seeing as these are production servers, so it wasn't documented as well as I'd like it to have been and it kind of got forgotten about as I moved onto the other issues... it seems that the restart had prompted a change in the Virtual Switch connection (which it hasn't done in previous months). So here is what my host sees as its network adapters in the Network Control Panel and Device Manager: Seems simple enough, but here is what Hyper-V (virtual Switch Manager) sees: This is the old name for the NIC adapters (#38), but as you can see only one of those old names appear (possibly the one that was in use by Hyper-V at the time of the HOST upgrade)... and the 'new' one, but annoyingly the 'new' name of the other adapter doesn't even signify which #no. it is (#39 or #40)! Anyway, it appeared that the the switch manager had somehow lost the connection and the VMs weren't connected anymore because it had changed to 'Public' or something and I need to switch it back to external (trying to make sure I selected the correct adapter), so I also ticked 'Allow Management OS to share adapter' as I was remote and have cut myself off before, but it isn't usually ticked as I have two adapters, one is dedicated to the HOST and the other is dedicated to the VMs. I know it sounds stupid, but I can't really work out from the screenshots which NIC is being used by which... What I'd like to accomplish ideally is to find out why this happens, but also that the Hyper-V Switch Manager sees the correct and full names of the NIC adapters in the HOST, so I can be certain in future which one to choose as even when I try to create a new virtual switch those are the only two options I'm given...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now