Hi,

Have you tried to "trace route" or "pathping" to diagnostic your current network without installing additional NIC from both (PC to Hyper-V host) and (Hyper-V Host to PC)?

Regards, Terry | My Blog: http://tls1.cc
This posting is provided AS IS with no warranties, and confers no rights.

Yes it's not a routing issue as I can access file shares and other servers within the vlan with hyper-v resides.

I have a bunch of Hyper-V servers sitting on a separate vlan and they have their own special subnet.

I used to be able to install Hyper-V Manager on my desktops and simply specify the Hyper-V servers and manage them remotely however, recently they do not allow me to communicate with them if I am sitting within a different vlan / subnet. 

They Hyper-V servers firewalls are disabled, the VLAN firewall rules allow for full connectivity between my management PCs to the Hyper-V servers so I know it's not anything to do with firewall policies.

Something on the Hyper-V server is not allowing me to administer it. I have added an additional NIC to my management PC which I stuck a leg into the other VLAN by adding an IP without a gateway to it and it allows me to administer it remotely. So I now know for fact that it has something to do with the different subnet.

I really need some help here as adding NICs to administer the servers is simply not an option.

Thank You!

Hi,

What's your operating system of your Hyper-V server and your PC?

Can you use PowerShell to manage the Hyper-V server remotely?

To manage Hyper-V Server 2012 or 2012 R2, you can read Manage Hyper-V Server Remotely for your information.
https://technet.microsoft.com/en-us/library/jj647785.aspx

Regards, Terry | My Blog: http://tls1.cc
This posting is provided AS IS with no warranties, and confers no rights.