I'm running a couple of VMs under Hyper-V that I use for testing. I created an "External" Virtual Switch using my NIC so that the VMs would have access to the Internet along with the host PC--the VMs and the host could all access the Internet after creating the switch. However, File and Print Sharing to the host from other PCs in my network quit working; the host in this case is also used as a file server.
I went through the Network troubleshooting from the another box trying to connect to the host and got, "file and print sharing resource is online but isn't responding to connection attempts."
I did find this article, which says:
[When] you create an External virtual network switch with the name "ExtSwitch" and map this virtual switch to a physical network adapter named "Intel(R) 82576 Gigabit Dual Port Network." When you click the Apply button, the following changes are processed in the property of the physical network adapter:
- Unbinds the following services, protocols, and clients: Client for Microsoft Networks, File and Print Sharing for Microsoft Networks, TCP/IP Protocol IPv4, TCP/IP Protocol IPv6, any other service, client or protocol listed in the physical network adapter property.
- Bind the "Microsoft Virtual Network Switch Protocol"
In addition, the changes below are done in the property of the External virtual network switch, in this case ExtSwitch:
- Bind the following Services, protocols, and clients: Client for Microsoft Networks, File and Print Sharing for Microsoft Networks, TCP/IP Protocol IPv4 and TCP/IP Protocol IPv6.
- Unbind the "Microsoft Virtual Network Switch Protocol."
It looks like, "File and Print Sharing for Microsoft Networks" should get re-bound to the new external switch.
I should note that I have recently applied the Creators update to all of my machines.
What is it about using a NIC for a Hyper-V External Virtual Switch that breaks File and Print Sharing over that same connection?