Hyper-V Server contains only the Windows Hypervisor, Windows Server driver model and virtualization components. It is therefore that it is quite a job to get Hyper-V core to work without errors since the firewall options that you are able to configure in hyper-v core are not enough to allow remote management of your Hyper-V virtual machines. I had this problem when I was running the Hyper-V core not under Active Directory but as a Workgroup. Some of my sites are now running in this vitual testlandscape, and they are running very good.

One of the problems that did take some time to figure out, was the Windows Firewall running on the Hyper-V box. You have to take notice that configuring Hyper-V Firewall through the normal Hyper-V core is not enough. You have to connect to the hyper-v core remotely and then use MMC on the computer you are connecting from. In MMC you add a snap-in for Windows Firewall. Instead of managing the local firewall, you can also manage remote firewall's. Now open a connection to the hyper-V server and add the firewall of that server to your local MMC. Now you are able to configure the firewall of the Hyper-V core.

To solve the problem with the "RPC server unavailable" I had to open network discovery in Windows Firewall. After setting these options, I was able to connect to remote Hyper-V virtual machines without any problem. If you have this error too, try shutting down the firewall in the Hyper-V server core completely (CMD in hyper-v core: netsh firewall set opmode disable“). Then try to connect remotely to this Hyper-V core. Are you able to connect, then you know you have to tweak the firewall settings in Windows Firewall of the Hyper-V core machine that hosts your virtual machines.

The problem I faced when trying to connect to a hyper-v core in my network:


Turning of the firewall in the Hyper-V core solved the problem. So I needed to tweak the firewall settings of this core server remotely.


Start MMC on your local compu:


Loading the remore Windows Firewall of the Hyper-V core in your local running MMC:


The solution is to tweak the Windows Firewall (enable network directory as in the picture) of the Hyper-V core:


After these steps, you will be able to access your Hyper-V core remotely.