Hello,
from the configuration screenshots you shared, the issue is that your Hyper‑V virtual switch is bound to the physical NIC, but the VM is not actually reaching the external network. When you select “External network” and tick “Allow management operating system to share this network adapter,” Hyper‑V creates a new virtual NIC (vEthernet) for the host and rebinds the physical NIC exclusively to the switch. That means the host and the VM both rely on the vSwitch for connectivity. If the vEthernet adapter shows “Unidentified network” or no valid IP, the VM will not be able to reach the internet.
The first thing to confirm is that the vEthernet adapter on the host has a valid IP configuration. If your environment uses DHCP, the vEthernet adapter must be able to obtain a lease. If DHCP is not available, you need to manually assign the correct IP, subnet mask, gateway, and DNS on the vEthernet adapter. The physical NIC itself should not have an IP anymore once it is bound to the switch.
On the VM side, ensure that the VM’s virtual NIC is attached to the same external switch you created. Inside the VM, check that the NIC is configured for DHCP or has a static IP consistent with the external network. If the VM is running Active Directory Domain Services, it is common to assign a static IP and point DNS to itself, but the gateway must still be the upstream router to reach the internet.
If you are still seeing no connectivity, check that the upstream switch port where the Intel I350 NIC is connected allows the VLAN you expect. In your screenshot, VLAN ID is disabled, so the vSwitch is operating untagged. If your physical network requires VLAN tagging, you must enable VLAN ID on the vSwitch and configure the correct VLAN number.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
Domic Vo.