Windows 10: Unable to Access Shared Folder on Hyper-V Virtual Switch

I have a Hyper-V virtual machine that uses a default switch, which is connected to a virtual adapter called vEthernet on the Windows 10 host. Using the IP address of the vEthernet adapter, I have no problem pinging the host machine from both the guest and the host machines. However, I am unable to access the shared folders on the Windows host. The sharing worked a few months ago when I first configured it so I suspect the issue might either relate to system updates or some other configuration changes that I am not aware of. Following is some more information of the configuration and my tests.
(1) I have tried to turn on the sharing on all networks under "Sharing options", but that does not help.
(2) I have tried to turn off the firewall but that does not help either.
(3) The shared folder can be accessed on other networks. The issue occurs only on the virtual switch.
(4) Troubleshooting indicates the file sharing port is not enabled on the virtual switch. An attempt to connect to port 445 on the virtual adapter fails.

:)

 

Hyper-V - Unable to Create External Virtual Switch


Nothing is listed:





Kevin

 

Hyper-V - Unable to Create External Virtual Switch

I see Windows PowerShell Listed at top left corner --- It Does Not Say "Administrator" Maybe problem

 

Win10 Accesses the Internet With Hyper-V's Virtual Switch


Just to add to Mystere's excellent post, using a Hyper-V external switch virtual machines get a bridged connection. If you prefer NAT (Network Address Translation) instead, you don't have to create an external virtual switch. About bridged vs. NAT: NAT vs. bridged network: A simple diagram - TechGenix

To use NAT in Hyper-V, first create an Internal switch in Virtual Switch Manager then share your host Ethernet or WLAN connection with your internal switch:




In VM settings set virtual machines to use the internal switch. They will now get private IP addresses 192.168.137.XXX, internal switch on host acting as DHCP server with IP 192.168.137.1.

Using NAT only with virtual machines makes external virtual switch unnecessary but as it makes networking between host and virtual machines quite a challenge if not impossible, the bridged mode with an external switch is the recommended way.

Quote from an old tutorial at our sister site EightForums.com:

(From EightForums.com tutorial Hyper-V Virtual Switch Manager)