0

I have a Windows 10 Pro machine (Creators Edition, build 1703) with Hyper-V installed, and a Win 10 Pro VM (same build). Everything seemed to be working fine at first, when the VM was using an internal virtual switch. I changed that to an external switch hooked up to my Wifi, because I needed Internet connectivity. But now I can't access shared folders on the host.

I have network discovery and file/printer sharing enabled on both the host and VM, for all network types (private, domain, public):

enter image description here

In Explorer on the VM, I can see the host machine show up under the Network tree. But trying to access anything on there results in an error.

enter image description here

I do have a shared folder on the host drive D, which I've managed to access before.

More information: I'm working from home on a domain-joined PC. The IP addresses for the host and VM are 192.168.0.3 and 192.168.0.2 respectively. The subnet mask is 255.255.255.0 for both.

The admin policy won't let me disable the firewall on the host, however I can access a shared folder on the VM from the host (it's the other way around that's causing the problem). Ping works both ways. A screenshot of firewall rules that seem relevant:

enter image description here

8
  • A similar issue in windows 7 and Xp occurred the same see if any of the answers Here will help you. Commented May 1, 2017 at 1:51
  • What is your IP configuration for the machines? Can you access them via IP instead of computer name? Commented May 1, 2017 at 2:22
  • @Twisty The machines are talking to each other via IPV6. I can ping the host from the VM, and the VM from the host, using both the computer name and the IP address.
    – Hong Ooi
    Commented May 1, 2017 at 2:38
  • Then next step is to disable firewalls/security software (for testing only!). Make sure both machines are in the private network profile too. Commented May 1, 2017 at 2:40
  • @Twisty I disabled the firewall on the VM, but it had no effect. I can't disable the firewall on the host, the admin policy doesn't allow it.
    – Hong Ooi
    Commented May 1, 2017 at 8:13

1 Answer 1

0

I managed to solve the problem (or maybe it's more of a workaround) by adding an internal switch to the VM, to go with the external one. After doing that, I could access my folder.

The caveat is that I have to use an IP address (169.254.xxx.yyy) instead of the computer name to refer to the host, but that's good enough for now.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .