virtualbox.org

Hello,

Since VB version 5.0.4-102546 the VirtualBox NDIS6 Bridged Networking Driver isn't working like it was till version 5.02-102096.

My host PC is running On Windows 7 and I installed VB on it.
The host PC is having a LAN adapter and a WIFI adapter
Inside VB I created several Windows Machines. (Windows 7(several), Windows10, Windows 2008 (several), windows 20012 (Several))
(all virtual machines are having this issue)

On the LAN adapter of my windows host machine I disabled all the protocols and services except the service "VirtualBox NDIS6 Bridged Networking Driver"
By doing this the host machine is not having any notice of the LAN adapter itself. This is done because the PC is using the WIFI adapter to connect to the company network, which is necessary to run Outlook against the Company Exchange server etc.
The LAN adapter is connected to a DSL line direct on internet.
(but because of no protocols selected on this Adapter the host PC is not using this adapter)

Since version 5.04 the LAN Adapter disappeared from the selectable network adapters in the Virtual Box manager. Till version 5.02 this was working fine
Reinstalling version 5.02 is bringing the network adaptor back in this list.

Another way to get it working (in the latest version) is by activating (for example) the IPV4 protocol.
Than the network adapter is also selectable again in the VB Manager.
But this is not wanted because than the host machine is also recognising the LAN adapter (again) and want to give it a IP address and use it etc.
The DSL router is also DHCP server for this LAN so the host machine is getting an IP address on the LAN Adapter. But then it is necessary to create routes on the host to prevent the host form using the LAN adapter.
Assigning a IP address on the LAN Adapter (like 1.1.1.1) is also creating a situation that the host PC can’t use this Adaptor for traffic on the Company network. But the Network administrator already noticed traffic in this range and also other colleagues are using VB so we must discuss who is using which IP address on the LAN adaptor to prevent duplicated IP addresses there.

Is it possible to get the NDIS Driver working again like it is doing till version 5.02-102096-win?

Or is there another way to get just the NDIS Driver from version 5.02???

Just had the same problem. This was really irritating and I spent far too much time diagnosing the problem.
Requiring us to enable TCP/IP in order to use an Ethernet layer driver is a bit counterintuitive. Please fix it.

i have the same problem. As soon as i installed vb 5.08 and opened a virtual machine i first had to change my driver in vb.

I have the same problem, and versions 5.0.6 and 5.0.8 did not fix the issue.

Also, for me enabling IPv4 on host does not make bridging work on my guest systems.

Same problem. If I enable tcpip on the host's NIC that I want to remain unbound, then boot the VM, then disable tcpip on the host's NIC, I can keep it unbound. VM wont restart though without throwing an error of non-existent NIC. But the best option for me until a fix is released.

Update: I've found that the VM seems to shutdown after a couple days and requires that I repeat the process, so this is not really a viable solution at all, but remains what I am doing until this bug gets fixed!