No host interfaces available in VB2.1

linus1805 · Post by **linus1805** » 2. Jan 2009, 12:51

Hello,

after I have updated to VirtualBox 2.1 there is no host interface available in the settings box for network settings. Also, there is no button to add any adapters !?!

This is the same for existing virtual machines as for new machines.

The manual only explains, how to use the various network scenarios, but no comment on the exact function of connecting to the host network interface(s).

Is there anybody who can help me in this matter ?

Thanks,
linus1805

Jon R · Post by **Jon R** » 2. Jan 2009, 18:57

You need to go into your network settings and when selecting your adapter use the drop down box to select either NAT/Host or internal network.

In the lower box will be all network adaptors found on your system. Select the one you wish to use.

This has been covered in other threads. You no longer need to use a TAP adapter with v2.1.

lcreswick · Post by **lcreswick** » 9. Jan 2009, 12:43

I too am experiencing the issue described by linus1805. I upgraded from Virtualbox 2.0.6 to 2.1 under Windows XP. After the upgrade my exsting Network Bridge (created for host interfacing in 2.0.6) some how got messed up to the point where i could not remove it from Network Connections. I had to remove some "Miniport" driver from Device Manager.

End result is that there are no Host Interfaces listed in the "Host Interfaces" list box when i choose "Host Interface" from "Attached to:" in VM network settings. This is the same for both new and existing VMs. I also tried adding other Network Connections to see if the culprit was my "Local Area Connection", but no good.

linus1805 · Post by **linus1805** » 9. Jan 2009, 12:47

Meanwhile I have found a solution:

If you have VB 2.0.x installed you have just to uninstall the whole package and then reinstall the new 2.1.

If, as in my case, VB 2.1 is already installed and no host interface is visible in the settings dialog box, just uninstall this 2.1 package again and reinstall it.

Good luck,
linus1805

lcreswick · Post by **lcreswick** » 9. Jan 2009, 13:03

Right you are! Upgrade from 2.0.6 to 2.1 caused this issue. Complete uninstall of 2.1 and reinstall resolved issue. Merely running a repair of 2.1 (without uninstalling) did not fix

Cheers!

Post by **Sasquatch** » 10. Jan 2009, 18:08

You might have looked at the properties of your interface(s). VB installs it's driver, but it's possible that it wasn't enabled. A reinstall (remove then install again) does the same, but it's a bit too much

.