virtualbox.org

Both NAT and Bridged networking work fine, but Host-only doesn't work.

I've read many threads on the subject, but none of them seem to match my problem exactly. I've tried some of their solutions anyway, including:

• removing and re-installing the "VirtualBox Host-Only Ethernet Adapter #2" on the host (I'm not sure why it's #2, there's no #1)
• checking (enabling) the NDIS6 option in the adapter properties
• uninstalling and re-installing VirtualBox
• re-installing VirtualBox and forcing it to use the NDIS5 driver.
• re-installing the guest OS

If anyone has any ideas about why this isn't working or what I could try next, I'd greatly appreciate it.

The particulars:
VirtualBox Version 5.0.10 r104061
Host: Microsoft Windows 10 Pro, 64-bit [Version 10.0.10586]; 16Gb RAM
Guest Ubuntu 15.10, 64-bit; 2048 MB Base Memory

I couldn't attach Vbox.log.1, Vbox.log.2, or Vbox.log.3 because those extensions aren't allowed.
I couldn't attach VboxHardening.log because the filesize is greater than 128K
I added Vbox.log.1, Vbox.log.2, Vbox.log.3, and VboxHardening.log to a zip file and attached that instead.

Thank you.

vaggrippino wrote: I couldn't attach Vbox.log.1, Vbox.log.2, or Vbox.log.3 because those extensions aren't allowed.
I couldn't attach VboxHardening.log because the filesize is greater than 128K

Then good news! We don't actually need four copies of the VM log, nor do we need the hardening log unless you have a hardening issue. So I deleted that attachment. I would have been nicer if you had zipped the one remaining log, but that's a personal preference (I don't like to be downloading 80k when I could be downloading 16k).

One thing that puzzles me is this according to the log your host only adapter is "VirtualBox Host-Only Ethernet Adapter #2". Normally only one host only adapter is installed (or required). Does your host's device manager actually list two? If so, can you think why? Did you upgrade your host to Win10 from an earlier install perhaps?