virtualbox.org

I am using VirtualBox-4.1.18-78361-Win version on my windows workstation and try to connect to the network using Bridged adapter setting.
But after changing the settings the VirtualBox guest-CentOS6.2 RedHat Linux does not start and gives the error as per the attached screen.
Please let me know how to fix this problem.

Is this due to lack of admin rights - by any chance ? Because on another workstation with same environment as mine - it connects without any problem - the only difference is that the other workstation has admin rights while I have a more restricted environment.

Thanks in advance - G

Run the following in a command window and post the results. Note: You need to be in the directory that has VBoxManage.exe for the command to work.

Hi Perryg,
The relevant output for this command is pasted below - thanks in advance

Name: Intel(R) 82579LM Gigabit Network Connection
Dhcp: Enabled
IPAddress: ***.***.166.96
IPV6NetworkMaskPrefixLength: 64
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-Intel(R) 82579LM Gigabit Network Connection

Name: Intel(R) Centrino(R) Ultimate-N 6300 AGN
Dhcp: Enabled
IPAddress: ***.***.211.86
IPV6NetworkMaskPrefixLength: 64
MediumType: Ethernet
Status: Down
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Centrino(R) Ultimate-N 6300 AGN

I obscured your first address. No need for the world to know it.

From looking at this I see the first one is obtaining from the Local LAN dhcp pool and the second one is not. The second post is an apipa address usually meaning that the guest can not reach the dhcp server.

Is this a corporate LAN? If so you will more than likely need the LAN administrator to allow the machine on the network, and to receive dhcp leases.

It could also be that the Bridged adapter is missing see troubleshooting Bridged adapter missing although this seems strange since bridgedifs report back.

Hi Perryg,
I am more interested in the first one - the Intel(R) 82579LM Gigabit Network Connection.
This is the one I am using for the connection.
And the virtualbox error is related to this adapter.

I checked the Device Manager and the device driver for - Intel(R) 82579LM Gigabit Network Connection
does not show any exclamation mark or error.

From the response below - Do I need to talk to the local LAN admin for the first one ??? - will the first one also have to be enabled ?

The actual pc adapter will not show up in the virtual guest since it is virtual. When you select Bridged in the guest settings there is a section that says advanced. If you click that to open it you can see the adapter that is presented to the virtual guest. Windows 7 should be the Intel/pro 1000, by default. See screen shot below and where it says Paravirtualized in mine for the Adapter Type your should say Intel/pro 1000. If you don't have Bridged as an option you will need to re-install VirtualBox, select repair, and make sure that you install the Bridged drivers. (This takes admin permission)

Hi Perryg,
I tried with the Bridged adapter setting with Intel/pro 1000 as Adapter type.
But I still get the same error.
I have Bridged Adapter as an option in the Attached To select box.

Let me know what else I can do 0- Is there some place I can check for the drivers or download and register spoecific drivers for Windows 7.

I'm afraid I am at a loss to tell you what is missing. You say that you have Bridged available in the settings and that you have the Intel driver selected, but the guest does not see the service and of course aborts. It sound to me like a failed Bridged adapter driver. I would re-install, select repair and make sure that the Bridged adapter is selected.