Private host network problem => Fixed in SVN

[alex57]

Since I have pass to the last version 4.1.4 I have a problem :

The Private host network function for the partage in network don't work.

This functionnaly don't work since i have restart the computer.

I use Windows 7 and a VM with ubuntu 10.10.

I have solve my problem with re-install the version 4.0.12.

Sorry for my english.

Regards.

[alex57]

I think that is a Driver problem.

I must re-install the driver "oracle VM virtual network adapter driver Host-only Networking" after each reboot.

Thanks.

[Leif Ringstad]

Same problem here. I can ping from Host to VM, but not from VM to Host. 4.1.0 and 4.1.2 works.

Actually it seems to be unable to ping from VM to HOST on bridged as well. Seems like the network config has been broken.

[Leif Ringstad]

Host: Windows 7 - 64-bit VMs: Ubuntu 10.04 (Server) Windows 7 - 64 bit

Unable to ping from VM to Host Able to ping from Host to VM Able to ping from VM to VM

Narrowed it down to beeing a Windows Firewall issue.

Check that your Virtual Host Interface isn't in "public zone".

[Leif Ringstad]

It seems like the installer doesn't set the *NdisDeviceType properly See the following:

​http://msdn.microsoft.com/en-us/library/ff557037(VS.85).aspx ​http://brianreiter.org/2010/09/18/fix-virtualbox-host-only-network-adapter-creates-a-virtual-public-network-connection-that-causes-windows-to-disable-services/

Follow Brians guide, or just do it yourself through regedit.

To fix this, *NdisDeviceType should be set as DWORD with value 1 in the VirtualBox installer.

[Aleksey Ilyushin]

The proposed fix will be included into the next maintenance release. Thanks a lot for your feedback!

[Frank Mehnert]

Fix is part of VBox 4.3.22.

[alexander.stohr]

as of mid 2015 the network adapter still prominently pops up as an "unidentified network". this does not look to me like it's fixed.

see also here:

• ​https://forums.virtualbox.org/viewtopic.php?f=1&t=27924
• ​https://mariobrandt.de/archives/technik/virtualbox-not-identified-network-849/
• https://www.virtualbox.org/ticket/9688
• ​https://gist.github.com/dansmith65/7950823
• ​http://www.brokenwire.net/bw/Various/120/fix-virtualbox-causes-unidentified-network-on-vista-and-windows-7
• ​http://blog.dmitryleskov.com/virtualization/powershell-script-to-fix-virtualbox-unidentified-network-issue-in-windows-7-and-vista/
• ​http://brianreiter.org/2010/09/18/fix-virtualbox-host-only-network-adapter-creates-a-virtual-public-network-connection-that-causes-windows-to-disable-services/
• ​http://superuser.com/questions/436617/virtualbox-hostonly-network-configuration-on-laptop-runing-windows-7-64-bit

[Valery Ushakov]

All the links you give seems to pre-date the fix. Can you provide any up-to-date evidence?

[z3r0]

By changing the value of NdisDeviceType in your driver to NDIS_DEVICE_TYPE_ENDPOINT (which indicates not a real network interface). You lock some windows components out of this device. One of the the biggest issues is that Edge (former IE) wont pass any requests if its ment for this device. Basically you can't use MS Edge with host-only adapters. Windows firewall will not monitor that network as well. More information on this in MSDN ​https://msdn.microsoft.com/en-us/library/windows/hardware/ff557037(v=vs.85).aspx

Virtual machine can contain multiple network endpoint and manage routing to other (for example internal virtual) networks so you cant decide in the driver itself what kind of network virtual machine is intended for.

The best option IMHO would be to expose this selection to user itself. As locking this to any option has its own drawbacks