Good day,
I've looked around and can't find a solution to my issue, which I'm hoping someone can shed light on this for me.
We have a Windows 10 64 Bit machine which has a netowrk drive mapped in. We created a VM with Windows 7 32 Bit to run older software etc... The Host is part of our domain infrastructure, but when we installed Windows 7 on the VM, we didn't add it to the domain as we just wanted it to be off of of the domain.
The problem we are having, is that we can share the Host Drive C, but since we're not on the domain we can't see the network drive. Is there a way to share the network drive?
Thanks
Network Drive from Host to VM
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Network Drive from Host to VM
To see real shared folders in the guest, the guest must be on the physical LAN with the host. Use "Bridged" as the guest's network connection, and the guest will be on the LAN, getting an IP address from the LAN.
See Virtualbox Networks: In Pictures
Note that if the host is connected with Wi-Fi, the guest's Bridged may not work, see the link. Use Host-Only to see just the host's shared folders.
FWIW I was Mr. IT at my former workplace, and I had both real PCs and Virtualbox guests connected to the network but off the domain, and as long as valid domain account info was provided, the shared folders on domain PCs and the server could be accessed. So being off the domain should not prevent non-domain-attached PCs from seeing domain shared folders. No telling what can happen or be blocked if someone got happy with your group policy editor, though...
See Virtualbox Networks: In Pictures
Note that if the host is connected with Wi-Fi, the guest's Bridged may not work, see the link. Use Host-Only to see just the host's shared folders.
FWIW I was Mr. IT at my former workplace, and I had both real PCs and Virtualbox guests connected to the network but off the domain, and as long as valid domain account info was provided, the shared folders on domain PCs and the server could be accessed. So being off the domain should not prevent non-domain-attached PCs from seeing domain shared folders. No telling what can happen or be blocked if someone got happy with your group policy editor, though...