Server 2012 R2 Questions (ADDS)

[iamtheoneneo]

So I managed to get server 2012 r2 up and running and wanted to configure DNS and ADDS on it.
I believe I did all correctly but for some reason my client pc just wont connect to the domain.

So my client TCP/IP would look like this:

ip: 10.10.10.2
subnet: 255.255.255.0
gateway: 10.10.10.1 (router ip)
pref dns: 10.10.10.10 (the 2012r2 server)


server side would be:
ip: 10.10.10.10
subnet: 255.255.255.0
gateway: 10.10.10.1 (router)
dns: 10.10.10.10 (server)

Firewalls are disabled on both server and client, i have tried localhost ip, pinging 10.10.10.10 from the client works, What am I doing wrong?

 

[El Pew]

What happens if you ping the DC hostname instead of the IP address? Domain joins are done by domain name (e.g. domain.com) rather than the IP of the DC.

If it doesn't resolve you may need to set the IP address of the DC as a DNS server within your router settings.

 

[Armageus]

What OS is the client? Also what domain functional level?

Can the server ping the client e.g. ping 10.10.10.2?

Shouldn't need to change anything on the router's DNS settings - they should be left as is e.g. ISP settings or set to google's dns servers.

Check the client vs Server clocks/Timezone, as if they are too far out then that can sometimes be a problem (Normally more of a problem at logon though)

Is there an actual error message when you try to join the domain?

Have you checked the event logs on the Server?

 

[Ploppy2k3]

after installing ADDS did you promote it to a DC? its a 2 step process on 2012+

 

[El Pew]

Shouldn't need to change anything on the router's DNS settings - they should be left as is e.g. ISP settings or set to google's dns servers.

Well something needs to change on the DNS side, because effectively he has two DNS servers at the moment - his router DNS will be completely unaware of the domain address because that will be handled by the Windows Server DNS service, even though it may have registered the DC hostname independently - so the client may be able to resolve "dc" or "dc.domain.com" but it won't be able to resolve "domain.com" which it needs to be able to do .

I suspect the best way to fix this will be to change the client's DNS settings to point at the Windows Server DNS instance, then configure that to do DNS request forwarding to the router's DNS service for everything that's not on the domain (i.e. the rest of the internet). Or add the Windows DNS service as a secondary DNS server on the client.

 

[Armageus]

Well something needs to change on the DNS side, because effectively he has two DNS servers at the moment - his router DNS will be completely unaware of the domain address because that will be handled by the Windows Server DNS service, even though it may have registered the DC hostname independently - so the client may be able to resolve "dc" or "dc.domain.com" but it won't be able to resolve "domain.com" which it needs to be able to do .

The router doesn't need to know anything about the domain addresses - it is purely for traffic outside of the domain. Everything can point at Windows DNS Server and the Router's DNS can be safely ignored.

I suspect the best way to fix this will be to change the client's DNS settings to point at the Windows Server DNS instance, then configure that to do DNS request forwarding to the router's DNS service for everything that's not on the domain (i.e. the rest of the internet). Or add the Windows DNS service as a secondary DNS server on the client.

He already is pointing the client at the Windows DNS server, so just a case of adding forwarders to the Windows DNS - in which case you can add google's rather than forwarding to the router.

 

[iamtheoneneo]

Figured it out finally, did some NSLOOKUP investigating and it was pretty clear that it was still trying to connect to the outside world and not my server.
Seems the IPv6 on the router was confusing everything, I took it off and was able to connect to domain.

Then I enabled it again and just disabled IPv6 on the server and client and seems to be ok so far.