bridged Network not working anymore, how to resolve this?

[pfautz]

Is there anybody who could give me a tiop how to rebuild or resolve my network disfuntionality on a Windows Vista Host and a Windows2003 guest system?

[Perryg]

Not enough information to be able to help.
Forum Posting Guideline

We need to know what you have done, what you want to do and how you have it setup now.

• Please provide host and guest memory.
• What are the VBox settings (all of them) for the guest?
• What (if any) error messages are you getting?

[mhanor]

I have the same problem
the host is running Windows XP SP3 32 bit
VB 3.0.8 (without VB USB driver and Python support, I've also removed the host-only interface created by default)
192-512MB guest memory (the default set by the Create new VM wizard, depeding on the selected guest OS)
other VM settings are defaults set by the wizard (I've tried XP 32 bit guest, Win7 64 bit guest), except the network adapter attached type (bridged), the USB&audio controllers (all disabled)... VT-X is enabled (Intel E6400)

From the logs:

00:00:01.446 IntNet#0: szNetwork={HostInterfaceNetworking-Generic Marvell Yukon 88E8056 based Ethernet Controller} enmTrunkType=3 szTrunk={\DEVICE\{22918FFA-6B43-4BEC-9244-FAD5433D78E5}} fFlags=0x0 cbRecv=223232 cbSend=36864
00:00:01.446 PDM: Failed to construct 'e1000'/0! VERR_SUPDRV_COMPONENT_NOT_FOUND (-3700) - The component factory was not found.
00:00:01.487 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={0a51994b-cbc6-4686-94eb-d4e4023280e2} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Generic Marvell Yukon 88E8056 based Ethernet Controller' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
00:00:01.487 Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).
00:00:01.487 Unknown error creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND)} aWarning=false, preserve=false
00:00:01.493 Power up failed (vrc=VERR_SUPDRV_COMPONENT_NOT_FOUND, rc=E_FAIL (0X80004005))

I have to mention that I've been waiting for VB 3.0.8 because 2 weeks ago I've uninstalled 3.0.6 and I was unable to reinstall it with the network drivers (this problem has occurred in the past several times, using different versions). The VB installation succeeded every time, no visible errors were shown, but Sysinternals' Autoruns listed only VBoxDrv, no trace of VBoxNetAdp or VBoxNetFlt. VB networking wasn't functional.

Those drivers are now listed as installed. When selecting Host-only, internal or NAT, the VM is able to start (I haven't checked for network functionality). Nirsoft Driverview doesn't list VBoxNetFlt as loaded.

[Perryg]

Try reinstalling by right clicking on the install program and left clicking run as admin. Select repair and see if it will install the drivers.
If that fails then rerun the install and select uninstall. Reboot the host and then try the above again as an install. This time let it install everything. Do not tell it to exclude any of the drivers and see if it will allow it to install all of the drivers and test bridged.

[mhanor]

it worked after uninstall/reboot/clean remains (including registry)/reboot/install... the thing is I use these steps every time when (re)installing VB, except I don't install the USB support driver and the Python support... It's weird
thanks

[rhkean]

ARGH!!!

I've been having this problem since I upgraded to 3.0.6. I had one install of Ubuntu that continued to work after the upgrade, but every new machine that I created reported "not connected" when I bridged to my wireless nic. When at work, I can bridge to my wired nic without problem.

I'm running Windows 7 as my host, and I've attempted 32-bit and 64-bit installs of Ubuntu, openSUSE, and fedora. I've also got a Win XP vm that I created with a 1.x version of VBox about 2 years ago. All work great in NAT mode and bridged to my wired nic, but not to my wireless.

I tried the procedure above, but that didn't work either. Any ideas would be greatly appreciated.

thanks,
rob

[Perryg]

@rhkean,
I don't know if this will help but you can try to create a second adapter in the guest and set it to the wireless card and leave the first connected to the NIC.
Leave them both active and see if you can switch between them by shutting down the wireless, or unplugging the NIC.
Then no matter which you hit it should be picked up.
I had this working a ways back so I could switch between office and home and not need to select the connection I needed at each location.

[rhkean]

ok... this really doesn't make any sense....

today, at work, I connected to our wireless router instead of our wired network. When I booted my Kubuntu VM, it connected just fine. So, I figured that everything was good now (not really knowing why, but not really caring either ).

But, when I got home and booted up the same VM... no connection. ARGH!

the status bar at the bottom of my VM window reports "Adapter 1 (Bridged Adapter): cable connected", but the network indicator inside the VM is reporting "Not Connected"...

I don't get it!?!?!!

-rhkean

[capnjack]

For me, with Ubuntu 9.04 on an HP EliteBook 8730w (iwlagn card) as the host, my XP guest wouldn't get a bridged connection to my wireless card using the Intel Pro/1000 MT Desktop or the PCnet-PCI III adapters, but when I switched to the PCnet-PCI II adapter, it worked smoothly. That's only a 10Mb adapter, but it works.

I mention it only because I haven't heard anyone else mention it yet, but XP would very quickly cycle through the "get a link, try to get an address" routine when it was broken.

Thanks,
Chaz

[rhkean]

Soooooooo... I'm an idiot!!!! LOL

On a suggestion from my co-worker, I set the IP of my bridged VM nic to static and, bingo, it worked... I tried this with a couple other VM's and bridged networking worked on them, too.

so, after a moment of head scratching, it clicked... I did a stupid thing. I had set the DHCP scope on my wireless router to only contain 10 IP addresses. That, by itself, not a big deal. But, for some stupid reason, I set the lease time to "forever". Again, not a problem when you're only using 2 home laptops and an occasional buddy stops by... A big problem when you're experimenting with multiple VM's with bridged nics.

anyhow, sorry for the wasted post. I'm going to go put on my dunce cap now... LOL

-rob