virtualbox.org

Hi all

I use Virtualbox on Windows7 system with 3 VM at the same time.
Stand-alone these machines work well, everything perfect and they go online using the NAT option [and AMD PCNet FAST III (Am79C973) card].

Now I need these 3 VMs to talk to each other.

With NAT they receive a different IP address (10.0.x.y) from the host (192.168.x.y)
This means that Host does not see virtual machines and virtual machines do not see the host's network.
In addition, the 3 virtual machines are not seen between them.

At this point I tried to set up "Bridged networking" but I receive this error

Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Codice 'uscita: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaccia: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

How should I proceed?
There is something I can check or install manually?

About "Bridged networking" I understood that is VBoxNetFlt that allow it.

Searching in my windows registry, under

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network

I don't have any reference about VBoxNetFlt.

I have references about VBoxNetAdp6 (driver of Host-Only Network Adapter) that is working.
I have references about VBoxNetAdp (driver of Host-Only Ethernet Adapte)

How can I manually install VBoxNetFlt?

Use a more modern Virtualbox. The whole 5.0.x vs Windows 7 vs NDIS thing got fixed long ago. Larger 'x' in 5.2.x version should be good. I run 5.2.28 on a Windows 7 host with the default NDIS6 just fine.

Be sure to uninstall Virtualbox and reboot first. Then when you upgrade, right-click the installer icon and choose Run As Administrator, even if you already are an Admin. And check all the options in the installer, so you get Bridged and Host Only.

The results you see when using NAT are expected.

valentino.b wrote:With NAT they receive a different IP address (10.0.x.y) from the host (192.168.x.y) <- true
This means that Host does not see virtual machines <- unless you open ports through NAT
and virtual machines do not see the host's network. <-false, the host and LAN are completely accessible by the guest

See Virtualbox Networks: In Pictures

scottgus1 wrote:Use a more modern Virtualbox. The whole 5.0.x vs Windows 7 vs NDIS thing got fixed long ago. Larger 'x' in 5.2.x version should be good. I run 5.2.28 on a Windows 7 host with the default NDIS6 just fine.

Be sure to uninstall Virtualbox and reboot first. Then when you upgrade, right-click the installer icon and choose Run As Administrator, even if you already are an Admin. And check all the options in the installer, so you get Bridged and Host Only.

Thank you Scott.
I'm using "portable" version of VirtualBox.
Lastest version is 5.1.22
Would I have the same issues with this version?

There is no official "portable" version of VirtualBox. If you are using a third party build then you need to go to them for support.

It seems that the problem is linked to network driver installed into HOST computer.
This network card is missing.
What is the Oracle package that installs this network card?

valentino.b wrote:What is the Oracle package that installs this network card?

The "package" is VirtualBox, obviously. See the Downloads area.

Please don't post offsite links. Attach images locally using the "Upload attachment" tab.

And let's reiterate:

valentino.b wrote:I'm using "portable" version of VirtualBox.

mpack wrote:you need to go to them for support.

We do not support Portable Virtualbox here. Whatever issues you have with Portable Virtualbox must be fixed by the Portable Virtualbox folks.

At the risk of diluting the above reiteration, if you want to get support here, you must remove Portable Virtualbox and any leftovers thereof, and install an up-to-date official Virtualbox from the Downloads link Mpack provided.