Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are trying to setup a lab environment in VMWare to test some server configurations.

At the moment we installed VMWare on a extra computer in the domain and created a VM with Windows Server 2012. That Windows Server 2012 is a domain controller and has Hyper-V running with another Windows Server running on it.

Now to make things more manageable we would like to RDP into those 2 server instances from our own pc's, which are also located in the companies domain. But this is the part where we are stuck, we can only RDP from the extra computer into the VM but not from any other place in the network. Anyone an idea how to accomplish this?

share|improve this question
up vote 2 down vote accepted

I am assuming this is VMware Workstation (VMware is a company that makes several different virtualization products), so the specifics will be for that product.

Since you don't want to use Bridge Mode, you can use port forwarding. Enable RDP in your two VMs and then add a port forward for each VM, so for example, if your two VMs are on and, and your LAN ip is, you could add a port forward so that TCP port 3390 goes to and 3391 goes to

Then you could connect to your VMs like this.

There is documentation on how to do this with VMware Workstation 10 here:

However, a word of caution. You indicated you didn't want to use bridge mode since you wanted to "isolate" the computers from the network, so they don't cause problems. About the only thing NATing compared to bridging will protect you from is accidentally setting up a rogue DHCP server, or perhaps a duplicate IP address or netbios name, all things that are fairly simple to avoid.

The virtual machines can still reach your company LAN just fine through the NAT and could protentially cause havoc depending on what you do. If you really want isolation, you'd do well to ask your network administrator to setup a truly isolated VLAN, and put your VM host on that, and then use bridging. You might find that setting up a lab server with ESXi would be easier for that, since you could have multiple people sharing a common lab platform on an isolated network.

share|improve this answer

Set up your virtual network card in bridge mode rather than in NAT mode. This will let the VMs sit directly on the network alongside with the host machine, rather than "behind" the host machine.

share|improve this answer
That's something I can't do, I want the VM isolated so it can't cause any problems on the company network. – dazz Jul 29 '14 at 12:41

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.