Fix VirtualBox Network Adapter Not Working in Guest

1. Wrong Adapter Type — The Most Common Culprit

This is the one I see 60% of the time. You set the adapter to something like Paravirtualized Network (virtio-net) or AMD PCNet FAST III and the guest just won't get an IP. The fix is dead simple: switch to Intel PRO/1000 MT Desktop (82540EM).

Here's why: Windows guests (7/10/11) and most Linux distros have native drivers for the Intel 82540EM. The virtio-net adapter requires special drivers you need to install manually. Don't bother with Paravirtualized unless you're running a test lab — it rarely helps in production.

Steps to fix:

1. Open VirtualBox, select your VM, click Settings.
2. Go to Network tab.
3. Under Adapter 1, set Attached to: to NAT (or Bridged — see section 2).
4. Under Advanced, change Adapter Type to Intel PRO/1000 MT Desktop (82540EM).
5. Click OK, start the VM, check if you get an IP.

On a Linux guest, you can also try the Paravirtualized Network (virtio-net) if you're running a modern kernel (4.0+), but I still default to Intel. It just works.

2. Bridged Mode Issues — When NAT Works But Bridged Doesn't

You set the adapter to Bridged so the VM gets an IP from your router. But it doesn't. Or it gets a weird IP like 169.254.x.x. The problem is usually one of two things:

• Your host has multiple network adapters (Wi-Fi, Ethernet, VPN). VirtualBox picks the wrong one.
• The bridged driver on the host is broken or missing.

Fix 1: Pick the correct host interface

In the VM settings, under Bridged Adapter, there's a Name dropdown. You need to select the exact physical adapter that's connected to the internet. On a laptop with Wi-Fi, that's usually Realtek RTL8821CE Wireless LAN 802.11ac PCI-E NIC or similar. On a desktop with Ethernet, it's Intel(R) Ethernet Connection I219-LM. Don't just leave it on the first one — pick the right one manually.

Fix 2: Reinstall the VirtualBox bridged driver

If the dropdown is empty or shows only Not selected, the bridged driver isn't installed. Run this from an admin command prompt:

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list bridgedifs

If that returns nothing, the driver is toast. Reinstall VirtualBox — that usually fixes it. Or run the installer in repair mode.

3. Host Services Not Running — Silent Killer

This one's sneaky. You check the settings, everything looks right, but the guest still has no network. The problem is the VirtualBox host services aren't running. This happens after a Windows update or a manual service stop.

Open Services.msc and look for these two:

• VirtualBox Bridged Networking Driver (starts automatically)
• VirtualBox Host-Only Network (starts automatically)

If they're stopped, start them. If they're set to Manual, change them to Automatic. Then restart the VM.

You can also check with this command:

sc query VBoxNetLwf

If it says STOPPED, run:

net start VBoxNetLwf

This fixes it every time for me. Don't bother reinstalling the whole VM — just restart the service.

Quick-Reference Summary Table

That's it. These three fixes cover 95% of cases. If none of these work, you're dealing with a deeper host networking issue — check your host firewall or DNS settings. But start with the adapter type. Nine times out of ten, that's it.