Hello,I've just updated to the new 3.0 version. Now I have big trouble with using my bridged network connection.

I'm using virtualbox on my notebook by using my wlan connection as bridged network interface. With the old 2.2.4 Version I had have nearly no problems. But with the new version I have noticed two problems.

1. After starting my ubuntu-server it don't get an ip from my router. Sometimes it works to stop and restart the networkinterface (ifdown | ifup) or to renew the IP by using the dhcpclient. Sometimes it only helps to stop and start the whole vm.

2. One time I have startet my W2k3 Server and after about 15 minutes no other pc in my network can't reach my vm. From my host it was possible to reach this machine, an my other vms were able to reach this server, too. On my host I didn't notice any network problems. I was able to reach the router and all other systems in network.

i have the same problem using vbox 3.0 on win7rc-64bit host and ubuntu 9.04 as guest. with vbox 2.2.2 i have no issue with bridge networking. upgrade to 3.0 and all of my guests that use bridge networking are no longer have network access to the router. i re-install 2.2.2 and i got the network working again.bummer. i really like the new features in 3.0 but i need bridge networking on the guest so that my little mmorpg server can be running and serve my home networking. for the moment 3.0 is no go for me.

NAT networking in 3.0 seems to be working the same way as the older ver 2.2.2. from my experience NAT in both version are slower compare to bridge networking though

I've lost two days of work because of this bull. Will have to get a laptop or something and install a real version of Linux.

ANY RESOLUTIONS????

I've uninstalled 3.0 and installed 2.2.4 but still the same problem.

What is going on?

Is VB intended for serious work or for hobbyists??

NOW, DHCP doesn't work with the VB bridged network (IT WORKED FINED BEFORE) so I set up the addresses manually and Windows doesn't report any errors but when I try to log into SUSE in VB I get the following error:

after installing 3.0 and failed to get bridge networking to work last time i have been playing with a few options. Here is what i found out:

test1:0. install 3.0 on the host in my case win7rc64bit1. REBOOT THE HOST2. start an old 2.2.2 ubuntu guest 9.04 networking is working fine. odd thing here is no vb3.0 tool is install in guest yet. it still has 2.2.2 vbtool. this success is a shortlive however i keep losing the connection and regaining after a reboot of the guest. after serveral reboot attempts.. enough is enough.3. exit vb3.0 entirely, re-install 2.2.2, reboot the host and i am back to a working environment again.

When I installed Virtual Box 3.0.0 it worked fine for a while (with dual processors even), but then the networks couldn't be configured by DHCP no more. After that, I decided to reboot-reinstall and the virtual machines crashed on startup with the error known by everyone: "Failed to open/create internal network ... (VERR_SUPDRV_COMPONENT_NOT_FOUND)"

I've installed and uninstalled versions 3.0.0 and 2.2.4 and rebooted in all possible combinations and nothing worked.

The NAT networking works fine, but I need a bridged network to export a NFS filesystem from the guest :-s

all previous attempt to use 3.0 was on old 2.2.2 guest linux os. today i attempted to create new guest from scratch. installation of ubuntu9.04 64bit went fine until it tries to reboot the guest.. it hang on loading network component. bugs bugs bugs vb=virtual bugs.

today i checkout vb website and that there is an update to 3.0 as 3.0.2 it list some networking as fixes in the changelog. i download it immediately.-installing over 2.2.2- reboot host- start an old 2.2.2 guest- bridge networking works for several seconds, i was almost jump for joy.- then it stop just like 3.0.0 minute later.

Switch the virtual network adapter to the IntelPro/1000 T server. This should fix your problems. You may need to get the drivers first and have them on the guest in case Windows does not have the drivers.

Perryg wrote:Switch the virtual network adapter to the IntelPro/1000 T server. This should fix your problems. You may need to get the drivers first and have them on the guest in case Windows does not have the drivers.

The virtual network adapter is selected in the network settings in the guest settings. For some reason there have been a lot of people that have had to change from the PCNet III to PCNet II or one of the other adapters (Intel) to clear up network problems since 3.0.X came out.

perryg. thanks for your suggestion. i managed to change the guest? network card to the one you mention and bridge networking seems to work a little longer before it give up again. yes it did not stay up for long.