Page 1 of 1

Virtualbox Bridge Adapter wont connect

Posted: 11. Jan 2018, 15:41
by tadek1981
I would like my guest machine to have its own IP on my network, and from what I understand, a Bridged Adapter is the way to go.

Looking at some tutorials, it seems straight forward to change from NAT to Bridged Adapter. However, when I configure my guest machine adapter in the following way and restart my VM, I lose the connection I had with the default NAT.

My host is 64bit Windows 10 Home version 1709

Guest OS is Ubuntu 16.04.3 I'm running Virtualbox v 5.2.0

Any ide what's going wrong?

Re: Virtualbox Bridge Adapter wont connect

Posted: 11. Jan 2018, 15:46
by socratis
tadek1981 wrote:I lose the connection I had with the default NAT.
If you change from A to B, you're supposed to lose A, no? Do you mean that you lose your "internet" connection? If yes, do you get an IP in your guest? Which one?

We're going to need to see a VM log from a complete VM run:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM.
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

Re: Virtualbox Bridge Adapter wont connect

Posted: 12. Jan 2018, 01:26
by BillG
How does your host connect to the Internet? NAT will work with just about any host connection. Bridged is a bit more selective. It works best if your host is on a LAN which has its own DHCP server.