2.2.4 and Bridged Networking

[Shad]

Installed 2.2.4 and selected
Bridged Adapter
but none are available under Name.

Tried the Repair/Reboot, nothing. Reinstalled, Repaired, etc etc - nothing.

[Shad]

Saw this thread here
http://forums.virtualbox.org/viewtopic.php?f=6&t=16443

Not sure why it was locked, many people are still having this problem.

No interface is selectable.

The gear icon to configure the attachment has only the MAC and 'connected' setting.

[Perryg]

Shad,
Welcome to the forum. The topic you have referenced is of a version that did in fact have a problem but you specify that you are using 2.2.4 so let's proceed from here.

• First was this a new install or an upgrade? Either way you should try right clicking on the install icon and the left click on run as... Admin. After it installs reboot the computer.
• Now if everything went well you should be able to open the settings and then network, and see Three configurable areas.
• adapter type: which is the virtual network adapter that you are going to use for the guest. Select the Intel PRO/1000 MT Desktop for Windows 7 RC.
• Attached to:where you select Bridged.
• Name: where you should see your actual network adapter that is installed in the host. Select it!
• The gear that you mentioned does allow for you to change the MAC but you should not need to mess with this.

Now if this is not what you see after you follow the instruction you might take a screen shot of the network settings area and post it here so we can see what is going on. Make it a jpg so it will upload.

[Shad]

Shad,
Welcome to the forum. The topic you have referenced is of a version that did in fact have a problem but you specify that you are using 2.2.4 so let's proceed from here.

Thanks!

• First was this a new install or an upgrade? Either way you should try right clicking on the install icon and the left click on run as... Admin. After it installs reboot the computer.

New install, no need for Admin as I am running XPsp3, but this is a good idea.

[*]Now if everything went well you should be able to open the settings and then network, and see Three configurable areas.
[*]adapter type: which is the virtual network adapter that you are going to use for the guest. Select the Intel PRO/1000 MT Desktop for Windows 7 RC.

Selected.

[*]Attached to:where you select Bridged.
[*]Name: where you should see your actual network adapter that is installed in the host. Select it!

Hehe, this is where the problem is. As I stated above, there is nothing to select here.
Obviously I have a network adapter however, I am able to create this post!

[*]The gear that you mentioned does allow for you to change the MAC but you should not need to mess with this.[/list]

I prefer to assign MACs based on a system but I do not need to mess with this, if that helps.

Now if this is not what you see after you follow the instruction you might take a screen shot of the network settings area and post it here so we can see what is going on. Make it a jpg so it will upload.

Virtualbox 224 Network Setup No Names Available

vb224-network1.jpg (36.67 KiB) Viewed 2464 times

Was using VBox1.5 but upgraded to this Sun edition, I believe I was able to select an adapter there, which makes this interesting.

Thanks for the help, though

[Perryg]

New install, no need for Admin as I am running XPsp3, but this is a good idea.

Why not try and see if it fixes your problem anyway. Just to make me happy 98% of the time this stuff does not work in Windows is because of a bad install.
Select repair and watch for any error or problem. Reboot when done.

[Shad]

New install, no need for Admin as I am running XPsp3, but this is a good idea.

Why not try and see if it fixes your problem anyway. Just to make me happy 98% of the time this stuff does not work in Windows is because of a bad install.
Select repair and watch for any error or problem. Reboot when done.

Heh. I usually assign all rights to the account I use the most (which I suppose I shouldn't do, I should use a normal User and RunAs everything important) but here goes.

Rightclick EXE, Repair, Reboot... still the same.

Oh, I had also updated Windows and all the drivers for all the components via MS before all of this, I usually just leave Automatic Updates running all the time, but wanted to make sure they were all ok.
If it helps at all, I am running a USR MaxG PCI Wireless Adapter, but there is also a Realtek onboard NIC that I use as well, and neither were detected/selectable.

Other than a few firewall calls, nothing out of the ordinary came up during the Repair.
It just looks the same as the picture there.

[Shad]

Posting from Windows 7 Beta as guest using NAT

So, NAT appears to work fine, it's just the functionality for Bridged would be nice, if needed (servers, etc).

Bridged is still not working.

[Perryg]

Ok I will sleep on it and go over some things tomorrow.
You did say that you had a previous version. I assume you uninstalled it before installing this one, am I correct? More tomorrow.

[Shad]

Ok I will sleep on it and go over some things tomorrow.
You did say that you had a previous version. I assume you uninstalled it before installing this one, am I correct? More tomorrow.

Yes I did.
I had 1.5 before this and uninstalled/rebooted before the 'upgrade'

Don't drive yourself crazy
Thanks for the ideas/assistance Night

[Perryg]

Ahh ver 1.5 used HIF instead of Bridged and you had to have setup your own Bridge to make that happen. Look in the network properties and see if you still have the bridge setup and remove it and also see if you see any other left over adapters that do not belong. If so try to remove them and then reload VB. If not then there is another way to get rid of the left over drivers that used VB but I have to find them again. I will look and send them later if you still need them.

[Shad]

Ahh ver 1.5 used HIF instead of Bridged and you had to have setup your own Bridge to make that happen. Look in the network properties and see if you still have the bridge setup and remove it and also see if you see any other left over adapters that do not belong. If so try to remove them and then reload VB. If not then there is another way to get rid of the left over drivers that used VB but I have to find them again. I will look and send them later if you still need them.

Thanks but I was wrong.
I did run 1.5 but not on this iteration of Windows. I have formatted/reinstalled since using 1.5...
I'm sorry I didn't recall correctly.

I don't have any bridges or extra adapters set up, but I'm going to try and install 1.5 just to see if it works anyway.

*

Just installed 1.5 I had and tried it out. I have never had to set up a Host Interface before, so apparently I just used NAT (sorry it's been a while since I had tried Vbox haha). The thing is, that takes out the possible adapters leftover, even if I did not redo Windows since then... There seems to be nothing in the way of drivers/etc causing a problem. Going back to 224 and going to continue using NAT for now, which works great.

If it helps, I tried VMware's Virtual Workstation, and the Bridged option worked fine and got an IP from the router, etc etc. It was seen as a seperate system. This is what I would like for Virtualbox

Too bad there is not more information on why so many people have had this problem and a 'Repair' has worked for most of them (not all of them, including myself). What did the Repair do?
Interesting.