Page 1 of 1

Win7 wireless network stack hang (under 2.2, 2.4, and 3.0)

Posted: 4. Jul 2009, 19:41
by ahopper
I'm on a laptop (MacBook Pro). I am seeing an odd issue where networking works perfectly immediately following installation, but once I reboot, it appears that the Windows network stack locks up. When I log in, I see the wireless indicator with the spinning circle, except it's *not* spinning; it's stuck in one position, and all network access at this point is b0rked.

I understand that bridging wireless adapters to VBox is problematic; is there a way to make my life easier here, or am I just stuck removing the VBox bridging services from the wireless adapter?

Thanks!

Re: Win7 wireless network stack hang (under 2.2, 2.4, and 3.0)

Posted: 4. Jul 2009, 22:23
by Perryg
Usually the problem can be resolved by changing the virtual adapter to one of the IntelPro/1000 adapters. You might need to download and have the drivers ready. I don't think they are all included in Windows.

Re: Win7 wireless network stack hang (under 2.2, 2.4, and 3.0)

Posted: 5. Jul 2009, 04:49
by ahopper
Thanks for replying!

This is on the host (that's where I'm seeing the hang)? Are you referring to the "VirtualBox Host-Only Ethernet Adapter"?

Re: Win7 wireless network stack hang (under 2.2, 2.4, and 3.0)

Posted: 5. Jul 2009, 15:39
by Perryg
Removing the host-only adapter is something that a few have done to solve network problems, but I interpreted your problem to mean that you did have host networking which I guess is not correct. I use wireless on my laptop and have never had a problem. It dual boots into Windows host and to Ubuntu. So it must be a MAC thing but I do not have a MAC at the moment to test this theory. I will read up and see if I can come up with more suggestions and let you know if I do, while we wait for others to reply.

Re: Win7 wireless network stack hang (under 2.2, 2.4, and 3.0)

Posted: 6. Jul 2009, 03:57
by ahopper
You were correct in that this is a host networking issue; however, the issue appears after installing VBox but before any VMs are created or started. I have discovered a workaround of sorts: uninstalling VBox prior to rebooting followed by a reinstallation appears to resolve the issue. Clearly that's an unacceptable long-term solution, so I'll test to see if just removing/replacing the VBox bridged networking driver has the same effect (still not a great solution, but better...).