Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 8743

Unabel to setup remote desktop access to isolated HyperV lab

$
0
0

Hey Guys,

I have an isolated HyperV lab made of 5 VMs which are in fact copies of live production VMs.
The lab is made of 4 SharePoint VMs + 1 DC and is working fine on its own. All VMs are connected to the same private HyperV network. Because these VMs are SAN copies of live machines, they can never communicate with the company LAN.

I now need to provide RDP access to the lab. We've first tried to use the HyperV manager to connect to the lab, which works fine, but is not comfortbale to use and only allow on connection at the time per VM.

So the idea is now to setup the host as a Terminal Server, the developpers can then RDP to the host and hop with a 2nd RDP to any VM in the lab.

My idea is to implement the following setup :

The Remote Desktop Services have been installed and configured, but I have the following issue: I cannot RDP to the host as soon as I enable the virtual NIC connected to the internal hyperv network. It's like of the traffic was not routed in the corrected direction. When that NIC connected to the internal hyper network is enabled, I cannot ping any machine from production and I must connect through iLO to manage the host (iLO = HP's console). As soon as I disable the NIC connected to the internal hyper network everything works fine again (except that I cannot of course reach my lab).

I've tried to play a bit with the order of the NIC in the avanced settings, but this didn't help.

What am I missing here ?

Thanks in advance for your help and have a nice day



Viewing all articles
Browse latest Browse all 8743

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>