Host adapter showing zero bytes traffic

[oivey]

On Windows 10 x64, I cannot get Microsoft Edge to connect to Virtual Box on the host adapter no matter what I try. (and I have researched this thoroughly on the web)

While trying to get the above working, I noticed that the host adapter shows 0 bytes of traffic, even though traffic is definitely passing through it.

My assumption is that there is something anomalistic with the host adapter on Windows 10, and I am hoping that it is this that is preventing Edge from accessing my guest OS.

For more info on this topic please see here:

​https://forums.virtualbox.org/viewtopic.php?f=6&t=76805&sid=03dc09ac43bda2a553c78e31a5b89232&start=15

[oivey]

Update: I have downloaded and installed 5.1.0 r 108711 on Windows 10 x64 and the problem persists ie:

• Edge will not connect to the guest via the host adapter
• All other browsers connect to the guest via the host adapter successfully
• The "VirtualBox Host-Only Network Status" window shows:

1. IPv4 Connectivity: No network access
2. IPv6 Connectivity: No network access
3. Packets Sent: 0
4. Packets Received: 0

And these 0 readings remain despite successfully connecting via the host adapter from any non-Edge browser to the guest via the host adapter

[oivey]

Update: the problem persists in 5.1.2

[oivey]

the problem persists in 5.1.4

[oivey]

the problem persists in 5.1.6

[ToddF]

I also have not been able to get MS Edge to connect to web servers on my VirtualBox host yet Firefox, Chrome, and IE connect just fine. I also can not get any Windows 10 Apps I develop to connect to the VirtualBox host either however Windows Desktop programs I develop connect to the VirtualBox just fine. Any help would be appreciated.

[Socratis]

Replying to ToddF:

I also have not been able to get MS Edge to connect to web servers on my VirtualBox host yet Firefox, Chrome, and IE connect just fine.

Wouldn't you think that this might be a problem with Edge then, rather than VirtualBox and you're looking at the wrong "suspect"? I'm just saying, because if you look for "Edge connection problems", the reports are not limited to VirtualBox. VirtualBox does not discriminate against applications.

[oivey]

@ToddF and @socrates This ticket is about a demonstrable problem with the VirtualBox host adapter on Windows 10.

In order to prevent dilution of the purpose for this bug, please can I ask that you stop commenting regarding the Edge issue which, while important, may be unrelated. (I mentioned it only as background and a possible hypothesis, not as part of the bug)

thanks

[oivey]

the problem persists in 5.1.8

[oivey]

the problem persists in 5.1.10

[oivey]

5.1.14 - host adapter still shows "No network access" and 0 Packets sent or received

... so the problem persists.

[Aleksey Ilyushin]

There are two unrelated issues here: (1) statistics are not updated for host-only adapters, and (2) host-only adapter is not connected to "network". Statistics issue is a minor inconvenience and will be addressed in upcoming version of host-only adapter. The connectivity issue is by design. Host-only adapters are registered as end-point adapters to prevent Windows from complaining about Internet connectivity, "Unknown network", etc. See https://www.virtualbox.org/ticket/9688 for example. If you really need to treat host-only network as "real" network, I suggest the following workaround:

1. Make sure "VirtualBox Host-Only Ethernet Adapter" is configured properly (network IP address and mask);
2. Start regedit and find "*NdisDeviceType" value, make sure "DriverDesc" value in the same key is "VirtualBox Host-Only Ethernet Adapter";
3. Change "*NdisDeviceType" from 1 to 0, reboot the host;
4. Check if Edge can access VM (you will see "Unknown Network" in "Network and Sharing Center");
5. Change the value back to 1, reboot the host ("Unknown Network" will disappear, but Edge will still be able to access it).

A word of warning though, there may be side effects of considering host-only network as a real network, that you may not like either.