Cannot join Windows VM machines to domain running on Vmware Workstation 5.5

Hi
I have created 3 Win2012 R2 (Evaluations) servers and 3 Win10 Pro (Evaluations) within VMware workstation 5.5. I have made sure that  there are in the same NAT network and the connected to the same adapter in Vmware workstation and there  can all connected to the internet. I have promoted one of the servers to a domain controller and enabled DHCP, DNS. However when l try to join the VM machines to the domain it says the domain controller cannot be contacted. I have tried to given the VM machines static IP addresses not included in the NAT or DHCP but still l cannot get them to join the domain.  I would appreciate any assistance.
LVL 1
Phil MapfumoInfrastructure EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if it cannot find your DOMAIN......

did you

1. turn off VMware DHCP for that NAT network.

2. DNS servers on your Workstations, need to be your DOMAIN DNS servers.

can your workstations ping your DNS servers ?

if they cannot find the domain name via DNS, they will not be able to join the domain.
0
McKnifeCommented:
Verify if the DC is set to be the primary DNS on the virtual NICs.
2
Phil MapfumoInfrastructure EngineerAuthor Commented:
Hi Andrew
 I have have turned of the DHCP for the NAT in Vmware,enabled the DHCP on the DC and authorized it however when I have done internet access is lost for all the machines and the machines are in a private network. I just realized that l have not tried to see if the machines can join the domain in the private Vmware network some how l don't have that much faith it will work but l will try it. @ Mcknife l can ping the DNS but  from the Win 10 Vms machines but still cannot joining the domain
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

McKnifeCommented:
Who was talking about pinging? :-)
You need to set the IP of the DC as your primary DNS entry in the properties of your network card.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I have have turned of the DHCP for the NAT in Vmware,enabled the DHCP on the DC and authorized it however when I have done internet access is lost for all the machines and the machines are in a private network.

to be expected.... will get to that later, can you guess why ?

so what DNS is set on your Workstations, you can screenshot if you like
0
compdigit44Commented:
On your windows server that is running DHCP, did you specify the IP address of the DC that is hosting DNS to the address is handed out to clients? As a test have you tried to manually type in the DNS servers IP on one of your workstations?
0
Phil MapfumoInfrastructure EngineerAuthor Commented:
Hi Guys
  Apologies for the late response, however this is what l have tried so far:
- I have accessed the network settings  for the Vmware workstation have created a network of  192.168.1.0 subnet mask 255.255.255.0
 and disabled the DHCP and NAT
- On DHCP I have created a 192.168. 1.0 network and a scope of 192.168.1.20-30 and activated it
- I have given the DC which is DHCP and DNS an address of  192.168.1.5
- I have made sure that the DC and WinPro10 are connected to the same network adapter.
- I have set the WinPro 10 desktop Vm to get an IP automatically from the DHCP but it failed to join the domain
- I have set the WinPro10 desktop Vm with a static IP of 192.168.1. 7 and set the DNS as the 192.168.1.5 which is the DC but it failed to join the domain.
I  will send screenshot if that helps, as l am am not sure were l am going wrong.
0
McKnifeCommented:
When you try to join, please enter the FQDN (for ex.: yourdom.local)of the domain and not the netbios name (in case you did).
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
lets forget DHCP for the moment, if you set the client TCP/IP information IP Address, Subnet Mask, and DNS.

can you ping the DC ?
0
compdigit44Commented:
Have you tried to set your VM to host bridged mode instead of NAT'd?
0
Phil MapfumoInfrastructure EngineerAuthor Commented:
@ Andrew I cannot ping the DC but l just realized that it must have been because l had the Windows firewall enabled. I will test it and get back to you @McKnife I have entered the FQDN and still no luck.@ Compdigit44 I have enabled bridge mode and gave a static IP for the workstation and now both the DC and workstation have internet. However l will need to disable the DHCP of the router and try and see if the workstation gets an IP from the DC and then try and join it to the domain
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you cannot ping, that's worrying....

changing all to bridge will work, but then you'll have no DHCP from your router!

does it join the domain now, you have changed to bridge, and use static IPs ?
0
Phil MapfumoInfrastructure EngineerAuthor Commented:
It still does not work when changed to bridge mode with static IPs as the workstation cannot join the doman, l am hoping that turning the DHCP on  the router off will allow the DHCP on the DC to issue IP addresses to the client and allowing it to join the domain.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay, DHCP or not, it's not going to make any difference. Park DHCP at present.....we can work on that later....

If you have the correct IP Addresses assigned statically, the workstation should be able to join the domain.

So can we go over the IP Address of the DC, and IP Address of the Workstation, trying to join the domain ?
0
Phil MapfumoInfrastructure EngineerAuthor Commented:
Even with DC issuing IP addresses joining the Domain has not worked. However I will assign the workstations with static IP addresses in bridge mode and see if that make a difference as you have suggested.
0
compdigit44Commented:
I know everyone has  be focused on the client workstation but have us ensured DNS is working correctly on your DC?

From the workstation is your type nslookup and your DC what do you get. If you do the same on the server and try to resolve the client name does it work?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
do you require any further assistance to help close this question?
0
Phil MapfumoInfrastructure EngineerAuthor Commented:
Hi Andrew
 I appreciate all your help, but l have tried all the install options and nothing has worked. I therefore abandoning this and decided to build my network on Hyper- V
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.