Fix connectivity in HyperV Client

Hi Kingma,

1. Use an External Virtual Switch (Recommended)

Create an External vSwitch bound to a specific physical NIC.

This way, the VM is bridged directly to the physical network, and DHCP/DNS come from your LAN/WLAN instead of the NAT layer.

But: if you switch between LAN and WLAN, you need to decide which NIC the External switch should be bound to (LAN or WLAN, not both at once).

For roaming devices (laptops), this can still be disruptive.

2. Create Two External Switches (LAN + WLAN)

Make one External vSwitch bound to LAN NIC.

Another External vSwitch bound to WLAN NIC.

Connect your VM to both vNICs (LAN vNIC and WLAN vNIC).

Inside the VM, Windows/Linux will then handle whichever interface is up, just like a physical dual-NIC machine.

This way, switching host networks doesn’t kill connectivity — the VM adapts.

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.