virtualbox.org

I had a Windows 7 box running VirtualBox 4.3.15 with a Linux and Windows guest. All IP addresses between host and VMs are static. Network adapter settings are "Bridged Adapter", with Intel PRO/1000MT Desktop. After trying to upgrade to VirtualBox 5.0.0 and 5.0.2, while networking still worked (even the two VMs could ping each other), neither the host nor the VMs could ping each other, as described below:

192.168.1.10 host (can ping .30, but not vm1 or vm2)
192.168.1.20 vm1 (can ping vm2 and .30)
192.168.1.21 vm2 (can ping vm1 and .30)
192.168.1.30 another computer on same subnet (all can ping .30, .30 can see all of them)

I tried changing many settings including Promiscuous Mode, adapter types, etc, however it made no difference. The same problem existed with both VB 5.0.0 and VB 5.0.2. It wasn't an issue of extension packs either. The same thing happened regardless of the extension pack.

I got it working again by DOWNGRADING to VirtualBox 4.3.30, and now it works perfectly again (as it did with VB 4.3.15). It even worked BEFORE I downgraded to the 4.3.30 extension packs, so the problem does not seem related to those.

At this point, I figure it is simply a bug or issue in VirtualBox 5.0.x, hence this posting to perhaps save some others the same headache of trying to figure out why it suddenly doesn't work after upgrading.

That sounds like an issue with the bridged driver version. VBox 5.0.x comes with two of them - the original used in 4.3 and a new one compatible with newer version of Windows.

User Manual wrote: The user is able to choose between NDIS5 and NDIS6 host network filters drivers during the installation. This is realized via a command line parameter NETWORKTYPE. The NDIS6 driver is default for Windows Vista and later. For older Windows versions, the installer will automatically select the NDIS5 driver and this cannot be changed. For Windows Vista and later the user can force to install the (legacy) NDIS5 host network filter driver using NETWORKTYPE=NDIS5. For example, to install the NDIS5 driver on Windows 7, do

VirtualBox-x.x.x-yyyyy-Win.exe -msiparams NETWORKTYPE=NDIS5

or

msiexec /i VirtualBox-<version>-MultiArch_<x86|amd64>.msi NETWORKTYPE=NDIS5

Source

You're correct, that was the problem! I forced VirtualBox to install the older NDIS5 driver version as you showed and all works again.

I filed the following bug report on the issue: https://www.virtualbox.org/ticket/14457

Thanks for the quick and easy solution!

noteirak wrote:That sounds like an issue with the bridged driver version. VBox 5.0.x comes with two of them - the original used in 4.3 and a new one compatible with newer version of Windows.

Thanks, Change NDIS version really help me bypass the comodo firewall conflict.

For me, on windows 10 RTM, this stopped VM's from working altogether. VM's refused to open with some network driver error.

Using the newer NDIS driver I found going to host network properties and tick/untick IPv6 pressing OK inbetween once or twice solved the issue till reboot. Then rinse and repeat.

I'm very happy Thanks, Change NDIS version

A spammer wrote:thanks

... for? What exactly? A three-year old solution that doesn't really apply today? Locking this.

I deleted his post: linked page spam (shopping website URL in profile).

mpack wrote:linked page spam (shopping website URL in profile)

Oops, good call, didn't check that part.