Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

RDP, Lab Setting, VMware used

Status
Not open for further replies.

wiimike

IS-IT--Management
Mar 30, 2007
145
US
Hi guys,

I'm in a bind here. I'm currently running a workstation on a production domain, connecting (RDP) to a Lab server, then using VMware's viewing tools to control VMs in that server. The VMs are set to "Host Only" which means they only interact with their host, and other VMs on the same box.

I'd like to be able to RDP into the individual VMs from my workstation directly, rather than this roundabout way. Is this possible? I basically am envisioning using my lab server as a middleman, since it can talk to my workstation and the VMs it contains.
 
Why don't you setup your VMs to use bridged networking whereby they all participate on your network (or is this not an option)
 
I plan on setting up a domain controller, dhcp server, dns, just didn't want to mix production and test
 
Using the VMWare tools from your workstation is the most secure method of working with these systems.

The only way to use RDP in this situation is to do as ITSP suggests or to set up RAS on the Host machine.

The problem with setting up RAS is that you will only be able to configure 1 NAT per IP assigned to the server for inbound connections. You will quickly find this cumbersome and annoying.

Stick with the VMWare tools.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers
 
connection security isn't an issue in my lab environment.

The product you recommend, while wonderful, is $1,600 at the minimum.

I'll check more into RAS
 
Have you considered;
1. Creating a separate network (connect the server to its own switch) and create a private IP address space (10.x.x.x for instance).
2. Configure your VMs to use bridged networking and assign IPs to them on this same 10.x.x.x network as your lab server
3. Install a 2nd NIC in your workstation (disable MS services on it so it doesn't participate on the network)and connect this interface to this private network.

HTH
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top