2 Subnets - One can't see domain

Microsoft Windows server 2003
April 9, 2010 at 10:05:39
Specs: Windows Server 2003
I work for a software development company, and we use VMs for most of our testing environments. One that we just created has to have a certain IP address to work, but the problem is, the IP address is much different from all the other computers on our domain. Our employees need to be able to remote desktop into it to use it. However, when set to the ip address it needs to have, the VM can't see any of the domain computers, or the domain controller. I'm assuming this is because the are on different subnets-

The VM has the prefix 172.26.104
Domain computers have the prefix 192.168.1

I've tried setting the VM to automatically get an IP address, and then connected it to the domain and told the domain controller to give it the IP it needs as a static ip, but the VM never picks it up, and instead is given an ip with the 192.168.1 address. Is there any way to connect this VM to a domain controller on a different subnet, or at least make it accessible on the network so that people can remote desktop into it?

See More: 2 Subnets - One cant see domain

Report •

April 9, 2010 at 10:10:03
What software are you using for virtualization?

Report •

April 9, 2010 at 10:11:26
We're using an ESX VMware server.

Report •

April 9, 2010 at 10:15:43
Given your criteria you need to put in a router to handle/route between the subnets.

Why is that ip a requirement? That seems strange.

Report •

Related Solutions

April 9, 2010 at 10:16:20
It looks like you've set up the virtual network card to use NAT and so the VM gets it's ip address from the DHCP server of vmware, not of your locally running DHCP server.
Try to configure the VM network card in bridge mode.

Report •

Ask Question