Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

My background is primarily .NET Development with some System Administration skills. I'm trying to set up a VM Lab for me to test System Applications I'm developing but I've only ever done System Administration in already set up environments; I've never set up my own.

My current setup: Server 2008 R2 Hyper-V Host on physical machine (only role enabled) with two NICs. First NIC dedicated for Management w/ DHCP address from company's network. Second NIC dedicated to RRAS VM w/ DHCP address from company's network. RRAS VM has two NICS, one is virtual private internal only NIC w/ static entry. The other is the physical NIC mentioned above. I've joined it to my internal domain. My Active Directory Domain Controller server (ADCT) also runs DNS, DHCP, and Certificate Services which I'm familiar with but don't understand completely.

RRAS is already set up with NAT to provide the private internal network with Internet access. What I would like to do is be able to RDP into the servers/computers on the domain from my computer. Do I need to add the Remote Desktop Services role and enable the Remote Desktop Gateway service on RRAS in order to do this or is there a way to set up port forwarding on RRAS to just allow a direct connection to the internal servers...or both? What would the best practices be here?

Network Diagram

share|improve this question
You don't need RDP Gateway services. I believe you just need to route your company network segment to the vm's network segmnet. Can you post description of both networks and respective gateways ? – voodooo Jan 21 '11 at 18:40
Added a link to network diagram, let me know if that helps with the description or if you need more info. Thank you for your help and interest. – Dennis Evans Jan 21 '11 at 18:58
How many lab nentworks do you need? Do you have a l3 switch that supports VLANs? We have similair setup with 5 labs running on different VLANs either isolated or routable depending on firewall – g18c May 21 '13 at 0:53

1 Answer 1

Assuming you're pc is behind network and the default gateway of that network is you just need to add a static route to this gateway like -> and make sure that the default gateway of every machine on the network points to (RAS Server). With this configuration everybody on the network will reach network. If you just need for your PC or for start testing you can make this local route, in windows: "route add mask" (cmd). Regards.

share|improve this answer
I've been researching static routes and port forwarding on an RRAS but haven't found anything that helps. What I'm still not understanding is how my computer that's on the network can "see" the servers in the private LAN behind the RRAS gateway. I made the local route and even added the RRAS as a default gateway in the IPv4 settings of my laptop's nic, but I'm still not able to ping or connect to the servers behind the RRAS. – Dennis Evans Jan 24 '11 at 18:19
Your RRAS server act like a router. Has one interface on each network ( and so he can route between them. Let's try again, if your PC is on network you can point the default gateway to the network IP of your RRAS server and traceroute an ip of the network: "tracert" for example and post the results. – voodooo Jan 25 '11 at 17:33
Our network administrator is going to give me a range of IP addresses so I can just put the VM's on the second NIC and do away with the RRAS altogether for convenience and immediate ease of use since I can't spend too much time on the setup of this. I do think having this VM network set up this way would be a best practices scenario and it will be something I'm going to pursue configuring on my home server. I will update this entry once I get things setup there. Thank you for your help thus far, it has been helpful. – Dennis Evans Jan 27 '11 at 14:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.