I have had a similar issue on my home Windows 8.1 Pro machine - I ran into the exact same problem - it has to do with the virtual network tunnel that is created on the hypervisor to the guest machines.
However, verbally - we have not recommended installing the firewall component onto Hyper-V hypervisor machines (guests are OK); this is due in how MS creates their virtual NIC and how SEP is added into the network stack - we do not allow permiscuous traffic though our firewall (packets not intended for the destination machine to pass through) - which in this case, since traffic first passes through the Hyper-Vs OS (and it's firewall) and it is determined that the traffic is for a different IP/MAC/ETC and is dropped (even though we know that the intended destination is a guest OS - SEP firewall doesn't know that)
In this case, I would just go to add/remove programs - modify Symantec Endpoint Protection, deselect Firewall from the Network Threat Protection section (Intrusioin Prevention is just fine).
You can attempt to write your own firewall rules for the hypervisor instead, however in this case, I would start with a default set and set ALL the rules to log that have a block attached and you can make adjustments from there - however, in this case for this one machine only - don't use the SEP firewall, for now.