Domain joining issues with Windows 2012 Domain & Windows 7 Professional

Hello Experts,

I am having a BIG problem joining some machines, about 10 of them into a Windows 2012 Server domain. These machines are all fitted with Windows 7 Professional.

The network is flat, both clients and server are on the single switch and they can ping each other. hey, I am even able to ping the domain...but when trying to join the machine to the domain I get the error the "AD domain could not be contacted" (SEE PICTURE ATTACHED).

What could be the problem, and how do I resove this?

Thank you.

Soames
Domain-Problems.jpg
TMAAAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Manjunath SulladConnect With a Mentor Technical ConsultantCommented:
Run ipconfig /flushdns and ipconfig /registerdns and reboot clients,

And restart the netlogon service on DCs.

Also check SRV records are registered on DC or not,

How to Verify the Creation of SRV Records for a Domain Controller

Refer : http://support.microsoft.com/kb/241515

More Info : http://social.technet.microsoft.com/Forums/windowsserver/en-US/2da7e03b-5818-4cec-a504-cc094f4b5d15/active-directory-domain-controller-could-not-be-contacted-windows-7-ultimate?forum=winserverDS
0
 
Spyder2010Connect With a Mentor Commented:
Are the domain controller and clients on the same vlan?  Just because they are on the same switch does not mean they do not have an ACL between them blocking specific ports.  AD needs quite a few ports open between the domain controllers and the clients to function... the article below lists all the ports AD uses for different functions, but specifically for your clients, you need at least:

ip/53
ip/88
tcp/135
udp/137
tcp/139
ip/389
up/445
tcp/636
tcp/3268
tcp/3269


You may need more of the ports in this list depending on what AD DS services you are using:
http://technet.microsoft.com/en-us/library/dd772723(v=ws.10).aspx

From your client machines, you can verify whether these ports are open or not by attempting to telnet from the client to the DC on each of the ports.

Also, by default, a normal AD user can only add 10 computers to the domain.  I don't believe this is the case for Domain Admins, but that is the default limit for non-admin users.  This doesn't appear to be your issue, but thought I would mention it since you mentioned 10 clients in your post.
0
 
TMAAAuthor Commented:
On the client machine did: ipconfig /flushdns and ipconfig /registerdns, restart the I stopped Bitdefender Firewall on the client machine and added a domain controller address on the client DNS machines. It worked on all 10 machines/clients
0
All Courses

From novice to tech pro — start learning today.