12.04 - Bridged Network in VirtualBox

  • user1042031

    I have just installed Oracle VMBox version 4.2.6 & Ubuntu 12.04.

    Am trying to use Bridge network connection but for some reasons it is giving me error as:

    Invalid settings detected


    enter image description here

    Unfortunately even after a host reboot I cant see any adapter name in the dropdown for "Name". Are there any settings need to be done for that as well?


    when I tried executing this command :

     sudo /etc/init.d/vboxdrv setup

    Result :

     sudo: /etc/init.d/vboxdrv: command not found
  • Answers
  • guntbert

    I have seen that on several occasions, every time it was some failed module.

    On a command line type sudo /etc/init.d/vboxdrv setup and watch the output for error messages. If there are no errors that should get you going, if there are any please post them into your question.

  • Related Question

    How to set up VirtualBox Bridged Network on Windows 7 Host?
  • Tong Wang

    I have virtualbox running on a Windows 2008 server, with a guest running ubuntu 10.04. The ubuntu guest is given a static IP of, which also has openssh installed. The guest has bridged network setup, I can ping from any machine in the LAN, the ubuntu guest can also access the LAN. However, when I try to PuTTY into the ubuntu machine, I always get "connection refused". Below are some setup details:

    ubuntu IP:


    sshd :


    ALL : ALL

    when I the following command, I can see that sshd is listening on port 22:

    lsof -i tcp:22

    Any idea?


    It turned out to be a wrong VirtualBox Bridged Network setup. I give the Ubuntu guest a static IP of (assigned to eth0). Then in the Windows 7 host, in the Network and Sharing Center, there is a new connection named "VirtualBox Host-Only Network" after the bridge is setup, that connection is again given the same static IP of Once I change the "VirtualBox Host-Only Network" to automatically obtain an IP address, it's getting a different IP address of And now I can SSH into with no problem, even without touching hosts.allow and hosts.deny.

    I've also noticed that in the properties windows (see screenshot below) of the "VirtualBox Host-Only Network", the second checkbox, "VirtualBox Bridged Networking Driver" is unchecked. While the same checkbox of the physical NIC (that is bridged to) is checked. So my further question is: is this how VBox bridged networking supposed to be setup? Any rationale behind this? I'd appreciate if someone could provide some explaination on VBox bridged networking setup on Windows host and I'll accept it as an answer.

    VirtualBox Host-Only Network Properties

  • Related Answers
  • Freddy Huayamave V

    I have a Windows 7 host, Ubuntu 12.04 guest, Virtual Box.

    My host get the IP from a router via wireless, choose network adapter options (running Ubuntu ) and select ''Attached to bridge adapter -> Name: < the name of your connection adapter (it can be your wireless or network adapter) >.

    Disconnect the ''wired connection'' from Ubuntu and set as DCHP client (automatic DHCP) in edit connections ipv4.

    Now you get an Ip assigned by your router and you can test making ping between host -> guest and guest -> host.

  • Eliah Kagan

    Here's a similar situation and what I did to resolve. I had my network settings set to NAT, which resulted in my guest not using the hosts network adapter. The ip was set and then I found out later:

    Search for:

    I've installed BigBlueButton using the VM, but I can't access it from a browser

    On this page:

    Even though I switched I needed to refresh my guest network adapter to pick up a new ip address, use the commmand ifconfig in the guest to find out what IP its using and set bbb-conf setip to that ip address result from ifconfig. The guest will use the host's adapter to get out to the web/network.

    For a Putty connection, run this command on your guest: sudo apt-get install openssh-server

    Run Putty with the ip from above (ifconfig result) with port 22.

    Here is a good read on host-only networking: