If a Windows 11 VM works in ZVM NAT mode but loses internet access in Bridged mode, troubleshoot the guest's LAN path layer by layer instead of assuming the bridge itself is broken. First verify DHCP, gateway reachability, DNS, Windows proxy settings, and the physical interface used by the bridge.
The source thread has an important warning against overgeneralization: one user fixed the problem by disabling Windows “Automatically detect settings” under Proxy, but a later user had the same broad symptom and that change did not help. Treat the proxy toggle as one verified case-specific fix, not the universal solution.
What Bridged Mode Changes
In NAT mode, the VM reaches the outside network through the host's virtual NAT. In Bridged mode, the guest should behave more like a separate machine on the LAN and usually receives its own address from the router.
That makes Bridged mode useful for game servers and services that need a distinct LAN IP, but it also means the VM must successfully reach the physical LAN, gateway, DNS, and any upstream firewall rules.
Step 1: Check the Windows IP Configuration
Inside Windows, run:
ipconfig /allLook for a valid LAN address, subnet mask, default gateway, and DNS server. A self-assigned 169.254.x.x address means DHCP did not complete.
Step 2: Test the Gateway Before Testing the Internet
Ping the router's LAN IP first. If the VM has a normal DHCP address but cannot reach the gateway, DNS and proxy settings are not yet the main issue. Focus on the bridge, physical NIC, VLAN, switch, or guest adapter path.
If the gateway responds, then test an external IP such as your known upstream resolver. Only after raw IP connectivity works should you troubleshoot DNS names.
Step 3: Check Windows Proxy Auto-Detection
In the verified source case, the user opened Settings → Network & Internet → Proxy and disabled automatic proxy detection. Internet access then worked.
That is a valid test when Windows has gateway connectivity but web traffic behaves strangely. However, a later forum user received DHCP but still could not ping the gateway, and the proxy change did nothing. A proxy setting cannot fix a layer-2 or gateway-reachability failure.
Step 4: Verify the Correct Physical Interface Is Bridged
If the ZimaOS host has multiple Ethernet ports, make sure the VM is attached to the LAN-facing interface you expect. Check the host's current interface names, link state, and IP addresses in Settings → Network.
The current ZimaOS networking guide documents how ZimaOS exposes physical interface state.
Be Careful Bridging Through Wi-Fi
Traditional Ethernet bridging maps cleanly to a wired NIC. Wi-Fi client interfaces can have limitations with transparent layer-2 bridging because many access points do not accept arbitrary source MAC addresses behind one station.
If your ZimaOS host itself relies on Wi-Fi, test the VM on wired Ethernet before spending time on Windows settings.
Step 5: Separate Static IP from Port Forwarding
You do not have to hard-code a static IP inside Windows just to keep a stable game-server address. A DHCP reservation on the router can be easier to manage and avoids conflicts.
After the VM has reliable LAN and internet connectivity, forward the required game-server ports from the router to the VM's reserved LAN address. Do not troubleshoot port forwarding until the VM can reach the gateway.
Check Windows Firewall and Network Profile
Windows may classify a new bridged adapter as Public. That does not usually prevent outbound internet access, but it can block inbound game-server traffic. Once basic networking works, set the appropriate profile and create only the inbound firewall rules the game server requires.
The ZVM setup guide provides broader VM context.
When to Report a ZVM Bridge Problem
If the guest receives a valid DHCP address but cannot ping the gateway, NAT mode works, wired Ethernet is in use, and another physical machine on the same switch works normally, collect the ZimaOS version, guest MAC/IP, host interface, bridge selection, router subnet, and ping results.
That evidence is much stronger than “Bridged mode has no internet.”
FAQ
Does disabling Windows proxy auto-detect fix ZVM Bridged mode?
It fixed one verified case, but not another later case. Use it when gateway connectivity exists; do not treat it as a bridge-layer fix.
Can a bridged VM have its own LAN IP?
Yes, that is the usual purpose of bridged networking. A router DHCP reservation can keep that address stable.
Why does NAT work while Bridged mode fails?
NAT hides the guest behind the host's virtual network. Bridged mode depends on the guest reaching the physical LAN directly, so DHCP, switch, NIC, VLAN, and bridge selection matter.
Should I port-forward before fixing internet access?
No. First make sure the guest can reach its gateway and the internet. Then configure inbound forwarding for the service.
