Opened 14 years ago
Closed 12 years ago
#5455 closed defect (fixed)
Bridged Networking Driver breaks host networking
| Reported by: | David Colborne | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 3.0.10 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Windows |
Description
After installing VirtualBox 3.0.10 on my workstation, my computer would have network connectivity after installation. However, after a reboot, my computer was unable to retrieve a DHCP address. Whenever I'd try to repair the connection, it gave me the error, "Failed to query TCP/IP settings of the connection. Cannot proceed." After uninstalling VirtualBox, my computer immediately retrieved a DHCP address and started to behave normally, which led me to dig a bit further.
After a while, I discovered that, if the VirtualBox Bridged Networking Driver was checked on the host NIC when it booted, I wouldn't have network access. However, if I unchecked it, waited for a DHCP address on the host interface, and rechecked it, everything worked normally.
I'm using an HP Compaq dc5750 with a Broadcom NetXtreme Gigabit Ethernet adapter running Windows XP Professional SP3.
Let me know if you need anything else. I (hopefully) attached a screen shot of the error I received.
Attachments (1)
Change History (7)
by , 14 years ago
follow-up: 4 comment:1 by , 14 years ago
Replying to DavidPCS: Do you have any custom networking-related software installed? I.e. VPN, firewals, antiviruses, other hypervisors (Virtual PC, VMWare), etc. ?
comment:2 by , 14 years ago
Also what is the latest VBox version that did not have this issue in your environment?
comment:4 by , 14 years ago
Sorry about not replying sooner. To answer your questions...
Replying to misha:
Replying to DavidPCS: Do you have any custom networking-related software installed? I.e. VPN, firewals, antiviruses, other hypervisors (Virtual PC, VMWare), etc. ?
Nothing fancy. I'm using TrendMicro OfficeScan 8.0, no VPN or firewall software (Windows Firewall is even disabled on the GPO level), and no other hypervisors.
Replying to misha:
Also what is the latest VBox version that did not have this issue in your environment?
3.0.6 was trouble-free. I never tried 3.0.8, so I can't vouch for that.
comment:5 by , 14 years ago
Good news, everyone - I installed 3.0.12 and the problem was fixed. I'm not sure what caused it in .10, but I'm not complaining.
Thanks!
comment:6 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Screenshot