Network adapter not working after setting up hyper-v lab

Hi, I saw an article on your website regarding issue with hyper-v and was hoping for help with my issue.
Basically I have created a lab environment on my laptop with:
1) one 2019 server VM, AD DS installed and domain created and static ip for the DC
2) two win10pro VMS
3) One Virtual switch used for external connectivity to server and other VM's using my computer's NIC
4) One private switch for VM's to join to internal domain.

The issue is it completely messed up my computer's NIC, it has no connectivity no matter what I have tried. I then tried an external usb adapter and restarted and it did exactly the same. I ended up removing all the switches and there is no change.
I have done a fair amount of googling but nothing really helps.

I hope you can help

Regards
--
David Green

In my experience with VM's you need to have Virtual Adapters for each VM for connectivity. Virtual switches will then function with a virtual adapter.

Thanks Railtech, Yes the VM's do need adapters however when switch manager doesn't really say "create switch" it only say add adapter and only suggests it as a choice of three types of network "external, internal and private". But I understand that this does suggest it is a switch, and it will create the adapters at the same time. The annoying thing is I have resorted to using a usb adapter and the speed is terrible. My computer's NIC is messed up even if I remove all the VM's all the virtual switches and disable hyper-v. Then the other day it decided to work (I don't know what I changed to make it work) and now it doesn't work again. Additionally I have no idea how to share between my local machine and any of the vm's despite searching on google. I don't understand how Microsoft make this so messy.
Anyway I have looked at the posts here and nothing really helps either so I may have to rebuild my machine and do all this on a old beefed up one.

- - - Updated - - -

Belcant2 said:

Thanks Railtech, Yes the VM's do need adapters however when switch manager doesn't really say "create switch" it only say add adapter and only suggests it as a choice of three types of network "external, internal and private". But I understand that this does suggest it is a switch, and it will create the adapters at the same time. The annoying thing is I have resorted to using a usb adapter and the speed is terrible. My computer's NIC is messed up even if I remove all the VM's all the virtual switches and disable hyper-v. Then the other day it decided to work (I don't know what I changed to make it work) and now it doesn't work again. Additionally I have no idea how to share between my local machine and any of the vm's despite searching on google. I don't understand how Microsoft make this so messy.
Anyway I have looked at the posts here and nothing really helps either so I may have to rebuild my machine and do all this on a old beefed up one.

Sorry, just took another look, switch manager does say create new switch. Aside from that I have created an adapter for each VM as well. I have removed the switches and adapters and started again and this time it knocked out the usb adapter as well.

When making these changes have you shutdown your VM's and your host then, restarted them all? When making changes to network at a minimum a restart is necessary and in your case because of all the changes a shutdown and cold start is probably necessary. What this accomplishes is a full initialization of the hardware (virtual as well) and generally gets things working.

You need also to understand that an virtual adapter performs just as a physical one does and same for a virtual switch. Each VM must have it's own adapter which then can work with a switch.

Thanks RailTech. For the most part I have restarted the vm's each time I made a change but from what you saying the physical host needs to be restarted too. Which makes sense now however the physical adapter is still not functional, it's like it is stuck on an earlier config and can't get back.
I understand about the adapters too after all I need them to set a static ip for the dc etc.

I am saying that you need to shutdown your PC not restart it. A restart will not result in an uninitialized adapter. The only way to do that and then initialize the adapter again is by a complete shutdown of the PC.

Thanks RailTech, I get it. Not that it makes any difference I shut it down every day and nothing changes. I might try removing every switch and adapter tonight and do as you say. Failing that I fear I will need to rebuild.