asked on

Cannot join PCs to Domain in new second site

Dear Experts,

I have recently setup a second DC in a new site, the sites are connected via VPN and the new server has been promoted in AD - replication works perfect and both servers are happily talking. However when I try to join a PC running win 7 pro to the domain in the new site where the new DC sits it cannot find the domain name :-S I edited the hosts file of the new server when I was joining it to the existing domain - i configured this new server for DNS and it is authorised and serves DHCP on this new site. Please advise :-)

Michael Ortega

What's the IP config of your client and IP address of the ADServer at the new site?

MO

AndreYPB

ASKER

the ADServer at new site is the DHCP using 192.168.100.2 for the server (also DNS server)
The client is on 192.168.100.12 with AD and Router set as DNS servers

Michael Ortega

You have your client machine DNS set to point to the router? You want DNS for your client machines to point to 192.168.100.2, your ADServer.

MO

AndreYPB

ASKER

They point to both the router and the ADServer - the ADserver being the first dns server the router being the second. I just tried editing hosts file of the client pc to point at the new DC in the site - still didn[t find the DC even after a reboot - I examined the error I get when trying to join the domain - this is what I got:

" The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

192.168.100.2
192.168.100.1

- One or more of the following zones do not include delegation to its child zone:

DomainName.local"

ASKER CERTIFIED SOLUTION

Michael Ortega

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

AndreYPB

ASKER

OK just to confirm - to remove the router as dns I amend the static details on the ADServer's adapter?

Michael Ortega

The only thing that should be listed for DNS on your ADServer is itself or it's loopback address (e.g. 192.168.100.2 or 127.0.0.1). There should not be any other DNS server referenced on the server. Now that that's clear you want to modify the DHCP scope on your DHCP server to not include any other DNS servers, but 192.168.100.2 unless you want to include your original ADServer from your main site. Through DHCP you only want your client computer to receive a DNS setting of 192.168.100.2 (or, again, whatever your other ADServer is from your other site).

MO

Michael Ortega

Your ipconfig output from your client computer should be something like this:

IP Address: 192.168.100.12
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.100.1
DNS: 192.168.100.2
WINS (optional): 192.168.100.2

MO

AndreYPB

ASKER

Ok i have that configured - however the clients can no longer access the internet :-(

AndreYPB

ASKER

Ignore that last comment - internet is fine o0 stupid win 7 network centre reporting no internet access

AndreYPB

ASKER

ipconfig now only shows the ADserver as DNS 192.168.100.2 - and router as default gateway - just tried joining domain without success - going to reboot PC now and try again.

Michael Ortega

Worked after the reboot?

MO

AndreYPB

ASKER

It sure did - thanks - going to join the other PCs to the DC now too ;-)

Michael Ortega

Way to go!

MO