Fix Hyper-V Virtual Machines With No Network Connectivity

Before you begin

Applicable to supported Windows Server/client environments where the named role or feature is installed. Run read-only checks first from an elevated PowerShell or Command Prompt as appropriate. Replace example hostnames, domain names, addresses, ports and paths with values from the affected environment. Record the exact error, timestamp, OS build and scope of impact.

Production safety: obtain change approval and a verified backup before modifying AD DS, DNS, DHCP, firewall, IIS, storage or Hyper-V configuration. Ensure console/out-of-band access before network or remote-access changes.

Symptoms and likely root cause

A Hyper-V VM starts but cannot reach LAN/internet while the host may still have connectivity.

VM NIC attached to wrong switch, VLAN mismatch, host uplink/physical switch trunk, guest IP or switch management-OS setting.

Diagnostic commands

Get-VMNetworkAdapter -VMName APP-VM01 | Format-List *
Get-VMSwitch | Format-Table Name,SwitchType,NetAdapterInterfaceDescription,AllowManagementOS
Get-VMNetworkAdapterVlan -VMName APP-VM01
Get-NetAdapter | Format-Table Name,Status,LinkSpeed,MacAddress
Get-NetAdapterStatistics

Run the commands in order and save the complete output. The commands above are intended to establish the failing layer before a configuration change is attempted.

How to interpret the results

VM NIC must attach to intended switch and VLAN. External switch connects VMs to physical network; Internal connects host+VMs; Private connects VMs only. Confirm physical trunk/native VLAN agrees with Hyper-V VLAN mode.

Practical correction

Inside guest, check ipconfig /all, route print, gateway and a known internal TCP service. Verify host uplink and physical switch port. Do not delete/recreate a switch before documenting host management and cluster dependencies.

Make one change at a time. Re-run the failed diagnostic after each change so the cause-and-effect relationship is clear.

Fallback and recovery

Record switch/VLAN configuration and ensure out-of-band host access. Restore previous switch binding/VLAN if connectivity worsens. Avoid remote switch deletion when it carries host/cluster management.

Verification checklist

Success: guest reaches gateway, internal LAN and required services; host management connectivity remains intact.

• Repeat the original failing operation from the affected client/user or service.
• Test from a second approved endpoint or subnet where relevant.
• Review the relevant event log/IIS log after the fix.
• Record the change, actual result and any remaining limitation.

Frequently asked question

Why can host internet work while VM fails? VM switch/VLAN or guest IP may be wrong independently.

Official technical reference

Microsoft Learn — virtual switch

Use the official documentation for exact version support, prerequisites and any procedure that differs between Windows Server releases.

Technician field note

This runbook describes a controlled diagnostic path; it is not a universal guarantee that every environment has the same cause. If evidence does not match the expected result, stop and investigate rather than applying unrelated fixes. Do not mark the incident resolved until the original symptom is verified as cleared.