#14326 closed defect (fixed)
5.0 NDIS6 Bridged Driver kills host network
| Reported by: | Kiran Otter | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 5.0.0 |
| Keywords: | lan bridged driver network | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
After installing Vbox 5.0 on Windows 7 x64, the host LAN stops functioning. Tried both 5.0.0-101573 and 5.0.1-101778. If I unbind the bridged adapter in the LAN network adapter properties, the LAN immediately begins to work again. Without it bound, Vbox guests can't use bridged networking.
See https://forums.virtualbox.org/viewtopic.php?f=6&t=68980
Change History (11)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
I was a contributor to that forum thread and still have the same problem with 5.0.4. Now have a Windows 10 host but same problem of host network connectivity being lost when the "Bridged" (and / or "Host Only) adapter is selected in the installer.
comment:3 by , 9 years ago
| Component: | network/hostif → network |
|---|
comment:4 by , 9 years ago
I'm having this issue on Windows 10. Not knowing what it was at first I:
Rebooted the machine.
Verified network settings were right ( 192.168.1.1 with DNS. Other devices worked on network)
Changed DNS
Uninstalled the network adapter.
Reinstalled network adapter
Unchecked IPv6
Disabled the NDIS6 Bridged Driver IT WORKED
Removed NDIS driver
Reinstalled NDIS driver STOPPED WORKING
Now I sit here without a driver, and I'm expecting VirtualBox to not allow Bridged network.
comment:6 by , 9 years ago
demortes, please try the latest Windows test build. There was a fix for NDIS6.
comment:7 by , 9 years ago
comment:9 by , 9 years ago
@Kiran - is this still fixed for you?
I am able to reproduce exactly this in 5.0.6 after going to sleep/resume.
I think we might be seeing false-positive fixes due to this issue not being present when a Host adapter is newly created or Bridging Driver is newly installed.
comment:10 by , 9 years ago
Gabe, I tested this and I too have the issue where the NIC doesn't connect after the host has been asleep. If I click the icon at the bottom to disconnect, and then connect the network adapter, it does work.
Kiran
comment:11 by , 9 years ago
Issues Duplicated here: https://www.virtualbox.org/ticket/14676
- In which I discovered this appeared to begin starting with version 4.3.30.
I can reliably reproduce on my laptop with sleep/resume.
My best workaround is to disable power management on the network interface.
Any improvement with VBox 5.0.4?