My Hyper-V VMs don't see VLAN-tagged networks.
On the host the physical NIC or virtual switch must be on a trunk, and on the VM NIC you set the right VLAN ID. Forgetting one of the two is the most common mistake.
support/servers-on-premise/vlan-trunking-op-hyper-v-hoststeps: 5
Try this first
- Check the physical switch port: trunk mode with the correct VLANs allowed. No native/untagged VLAN if it would cause confusion.
- On the Hyper-V host: New-VMSwitch -SwitchType External, bound to the correct physical NIC. No VLAN config at vSwitch level, that lives per VM.
- On the VM NIC: Set-VMNetworkAdapterVlan -VMName 'vm' -VMNetworkAdapterName 'NIC' -Access -VlanId 20.
- Test: inside the VM run ipconfig, ping the default gateway of VLAN 20. If it fails check Get-NetAdapter and Get-VMNetworkAdapterVlan.
- For the management OS in a VLAN: Set-VMNetworkAdapterVlan on the management OS adapter. Careful: misconfigured and you lose admin access.
When to bring us in
For cluster hosts or SCVMM, configure Logical Networks and VM networks consistently on every host. Otherwise migrations fail when a VM moves from host A to a host B that lacks the SCVMM vNet.
See also
- One DC or two DCs for an SMB office?Two is almost always the right answer; one DC is a single point of failure for logon, DNS and GPOs.
- Should I split FSMO roles across two DCs?For a small domain all on one DC is fine; with two DCs splitting is tidier but not required.
- How do I know my AD replication is healthy?Replication errors creep in silently; they only surface when logins or GPOs misbehave.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.