virtualbox.org

Host: Windows 8.1 Pro x64 on a Surface Pro 3 512GB
Guest: Windows 10 Pro x64
VirtualBox 5.0.4

By matching the mac addresses I have determined that:
Adapter slot="0" ==> Ethernet 3 Marvell AVASTAR Wireless-AC Network Controller
Adapter slot="1" ==> Ethernet VirtualBox Host-Only Ethernet Adapter
Adapter slot="2" ==> Ethernet 2 Surface Ethernet Adapter
Adapter slot="3" ==> Ethernet 4 Nat

Unfortunately, Ethernet 2 has been flagged as a Public network: I can map shares from other machines on the network: But they do not show up under Network in File Explorer: I can see the shares on other machines by referencing \\<machine name>\ except for the host (NYW8p1-0015).

I will post the machine definition in a reply to this was the maximum number of attachments is three.

Any suggestions on how to get networking working correctly would be appreciated.

Machine definition is attached (renamed to xml as the extension vbox is not allowed).

I can't see anything there which points to anything in VirtualBox. It looks like a pretty standard Windows 10 networking situation.

Windows networking only shares files on Private network connections. As long as one NIC is in a Private network, it is happy.

Your screenshot of Network in explorer would be more useful if you expanded each device, not just expand Network.

Do you really need four NICs in the vm?

Problems like this are almost impossible to solve through a forum post. There are too many unknowns.

>Windows networking only shares files on Private network connections. As long as one NIC is in a Private network, it is happy.
The question is why the NICs that should be in a Private network are not treated that way.

>Your screenshot of Network in explorer would be more useful if you expanded each device, not just expand Network
The problem is that the other devices are not showing not shares on the shown devices.

>Do you really need four NICs in the vm?
Yes. Actually, if you look at the machine definition you will see that VirtualBox provides for a number of additional NICS they just aren't in the GUI.

>Problems like this are almost impossible to solve through a forum post. There are too many unknowns.
Isn't anyone else running a Windows 10 Pro x64 VM under VirutalBox?

BillG wrote:It looks like a pretty standard Windows 10 networking situation.

As Bill said, you'd have better chances of looking for the solution to your networking situation in a Windows 10 forum. As far as VirtualBox is concerned, there are no problems, or anything you can do from the VirtualBox side to change the situation.

saberman wrote:

BillG wrote:Windows networking only shares files on Private network connections. As long as one NIC is in a Private network, it is happy.

The question is why the NICs that should be in a Private network are not treated that way.

Again, that's a Windows question.

saberman wrote:

BillG wrote:Problems like this are almost impossible to solve through a forum post. There are too many unknowns.

Isn't anyone else running a Windows 10 Pro x64 VM under VirutalBox?

Lots of people. But, the amount of people that have 4 NICs, and some of them got assigned to a Public network as opposed the remaining I guess is too slim.

Having said that, take a look at this discussion ( viewtopic.php?f=6&t=59163 ) from a couple of years ago. The key is that Microsoft's definition of Private, Public and Unidentified is quite fragile and maybe changing from version to version. One thing to focus on should be to fill the default gateway on the guest side.