Jump to content

Hello, 

 

I am setting up a domain controller in the network in our office using 2012 R2. I have set up AD DS and all the other stuff, but when I try to connect other computers on the network to it (Windows 7 Pro or Windows 10 Pro) it says "ADDC for "(domain name) cannot be reached" and something about a DNS delegation. All computers and servers are connected to the same switch and everything. 

 

Please help. I need our servers to work so WE can work! 

 

-Cameron

post-227265-0-43805100-1450595460.jpg

Cameron Lasley

Owner, Lasley Media Group

Link to comment
https://linustechtips.com/topic/509005-windows-server-ad-dc-issues/
Share on other sites

Link to post
Share on other sites

Hello,

I am setting up a domain controller in the network in our office using 2012 R2. I have set up AD DS and all the other stuff, but when I try to connect other computers on the network to it (Windows 7 Pro or Windows 10 Pro) it says "ADDC for "(domain name) cannot be reached" and something about a DNS delegation. All computers and servers are connected to the same switch and everything.

Please help. I need our servers to work so WE can work!

-Cameron

And what are you using as a dhcp server? The server itself or your router?

Link to post
Share on other sites

Hello, 

 

I am setting up a domain controller in the network in our office using 2012 R2. I have set up AD DS and all the other stuff, but when I try to connect other computers on the network to it (Windows 7 Pro or Windows 10 Pro) it says "ADDC for "(domain name) cannot be reached" and something about a DNS delegation. All computers and servers are connected to the same switch and everything. 

 

Please help. I need our servers to work so WE can work! 

 

-Cameron

On the client system, change the primary DNS server to the DC, and re-join the client to the domain. 

 

Or add the A\AAA records to the DNS server currently being used as the primary (you might not have access to do this if they are pointing at Google DNS), and have them point to the DC.

 

Or you might not have authorized the DNS server on the domain (when installing ADDS on 2012 R2 it will do this for you).

Link to post
Share on other sites

And what are you using as a dhcp server? The server itself or your router?

I'm using our Comcast Modem as the DHCP server. And as the DNS, I've tried to watch videos on it, and didn't help me. Is there a good video on how to set up the server to be the primary DHCP server and how to set up DNS?

 

-Cameron

Cameron Lasley

Owner, Lasley Media Group

Link to post
Share on other sites

On the client system, change the primary DNS server to the DC, and re-join the client to the domain. 

 

Or add the A\AAA records to the DNS server currently being used as the primary (you might not have access to do this if they are pointing at Google DNS), and have them point to the DC.

 

Or you might not have authorized the DNS server on the domain (when installing ADDS on 2012 R2 it will do this for you).

How do I change the DNS to the DC? And is there a good video on how to setup a DNS server? I am not too experienced in 2012 R2, clearly. 

 

-Cameron

Cameron Lasley

Owner, Lasley Media Group

Link to post
Share on other sites

You don't need to (and can't) run DCpromo like in 2008. After installing the AD DS role, the user should be prompted in the Server Manager with the "flag" notification to promote the server to a Domain Controller (you need to do this). During this promotion the server will install DNS by default.

 

After the server has been promoted to a domain controller go to your client. Change the client's IP to a static IP on the same network as the server and set the Primary DNS to the Server's IP address. Now you should be good to go.

Link to post
Share on other sites

How do I change the DNS to the DC? And is there a good video on how to setup a DNS server? I am not too experienced in 2012 R2, clearly. 

 

-Cameron

On the DC do an IPconfig and get the host IP address.

On the client Set the primary DNS server as the DC's IP address.

 

When you have DHCP (best practice is on a seperate box -> But if this is a white box you'll be fine with running ADDS and DHCP on the same box), have it auto assign clients the DNS server.

 

Make sure your DNS server (in this case the DC) is configured with a Static IP, as you don't want it changing everytime you reboot it for the monthly security update.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×