How To Force Mapping Through Virtual Host Ehernet Adapter

[saberman]

Host: Windows 10 Pro x64 (Surface Pro i7) in a Surface Pro docking station
Guest: Windows 10 Pro X64
VB: 5.12.14 r123301

I have the following adapters defined:
NET
Host Only Adapter
Bridged (Surface Ethernet Adapter)

I also have a VBOXSHR drive defined and mapped.

The host does not show up under Network in File Explorer. I can map shared drives using: NET USE I: \\<Host Name>\<Share Name>
However, that creates a problem when I remove the host from the docking station and the Bridged adapter is not available.

Is there a name I can use in: NET USE I: \\<Host Only Ethernet Adapter Name>\<Share Name>
to force the mapping to go through the Host Only Ethernet Adapater?

The default gateway IP address for the Host Only Ethernet Adapter is: 192.168.56.1
Is that always the IP address and, if so, is it safe to map using: NET USE I: \<192.168.56.1>\<Share Name>

I am having problems where even if I unmap all drives before shuting down and removing the host from the docking station and removing the Bridged Adapter when I start the VM and log into it I get a popup that not all network drives are available and explorer goes into an abort restart loop.

[ChipMcK]

1. Start up VBox
2. Start the Windows VM, log in, etc.
3. From the Start menu, select (My) Computer
4. On the Menu Bar, select Tools
5. From drop down, select Map Network Drive ...
6. follow the prompts

[saberman]

I am a little confused. There isn't any (My) Computer on the Start Menu. I can map a share using File Manager but the Browse button does not show the Host Only Ethernet Adapter.

Please advise how to reference the Host Only Ethernet Adapter -- preferably using Net Use.

[ChipMcK]

windows does not show that information.

[BillG]

That is probably a Windows problem, not a VirtualBox one. The host only network does not use default gateways because it is for host-guest communication only and is not routable. Because of this, Windows will make it a public network by default which prevents file sharing. You will need to persuade Windows to make the network private.

The net use command knows nothing about interfaces. It is only concerned with machine/file/folder names and usernames and passwords.