View original (French)

VirtualBox issues to have a "bridged adapter" access

Solved
kuiknek Posted messages 54 Status Member -  
kuiknek Posted messages 54 Status Member -
Hello,

I have a little issue with VirtualBox; my instructor is asking me to set it to bridged adapter, but I can only switch to NAT and I can't figure out what the problem is!
My virtual machine, as I mentioned in my title, is "VirtualBox."

Thanks in advance, everyone.

4 answers

  1. kuiknek
     
    Hello,

    My version: 4.3.2 r90405
    I downloaded it about 2 months ago, but I hadn't downloaded the extension pack and the guest add-ons (unless it was included in the installation).

    So, following your message, I went to the VirtualBox site, but there is no version 4.3.2....

    To set up a bridged network, I do: right-click on my desired machine, configuration,
    network, then I select "bridged adapter".
    Below "network adapter type" (so: name) there are no cards displayed, so I cannot validate my choice by clicking OK at the bottom

    In "advanced," I chose in "promiscuous mode": "Allow VMs."
    1
  2. kaumune Posted messages 22604 Registration date   Status Contributor Last intervention   5 157
     
    Hi

    Which version of VB?
    Did you install the extension pack and the guest add-ons properly?

    What are you doing to switch to bridge mode and what's happening?
    0
  3. kaumune Posted messages 22604 Registration date   Status Contributor Last intervention   5 157
     
    So, following your message, I went to the VirtualBox site but there's no version 4.3.2....

    There are all the older versions, since 1.6, on the VB site.

    Make sure to install the latest version properly (since we're at it), then we'll see.
    0
  4. kuiknek Posted messages 54 Status Member
     
    Hello,

    I’m sorry for the late response, but after downloading the latest version, my card is recognized again.

    I was worried about losing my virtual machines, so I exported them before installing the latest version, but in the end, that precaution wasn't necessary; nothing has changed except that I have the latest version now :)

    Thank you very much, I hadn't thought of that solution.
    0