How to access domain controller running on VMware from client pcs

Question

I have installed Windows Server 2008 in VMware workstation. But I can't add client pc in domain controller.

VMware workstation computer's IP:

IP: 192.168.126.132
Subnet Mask: 255.255.255.0
Default: 192.168.126.2

DNS: 127.0.0.1

Client's PC IP:

IP: 192.168.32.3
Subnet Mask: 255.255.255.0
Default: 192.168.32.1

DNS: 127.0.0.1

Domain Name is: SPN.com

When I add client's PC in Domain it prompts a msg saying a domain controller for the domain [name] could not be contacted, ensure that the domain name is typed correctly.

Client's PC IP ping 192.168.32.3 in VMware Workstation its give me Reply perfectly.

Answer 1

VMware workstation typically deploys virtual network adapters on the client. Make sure that when you ping the PC VMware Workstation (192.168.126.132) to your PC Client (192.168.32.3), it uses the correct network adapter. Network cards used by VMware can be configured in three profiles: Bridged, NAT and Host-only.

Bridged should be the correct configuration.

Be sure that you can ping in both direction. However, attention to the configuration of your subnet mask beacause they are not in the same address range and preferably put the address of the domain controller for the DNS.

I hope this will be helpful.

Answer 2

I had a similar problem. My VMware machine could ping the D and vice versa. All I had to do was go to the server manager > Local server > click on "workgroup/Domain" > hit the "change" button and under "Member Of" type in the name of your domain without the .com > when prompted enter your credentials as yourdomainwithout.com\user and password > then it should say welcome to your domain. You must restart the VMware machine for the changes to apply.

Answer 3

You've listed 127.0.0.1 as your DNS server for both. For the DC, I'm not sure that it matters (if you've installed and configured the DNS role). For your client, it needs to use a valid DNS server configured with your domain suffix. You'll want to either configure internal domain DHCP or if this is a test environment statically assign it. But if your client doesn't have a valid DNS server configured it won't reach a dc.