Solved

Cannot join PCs to Domain in new second site

Posted on 2011-09-10
14
323 Views
Last Modified: 2012-05-12
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 :-)
0
Comment
Question by:AndreYPB
  • 7
  • 7
14 Comments
 
LVL 16

Expert Comment

by:Michael Ortega (Internetwerx, Inc.)
Comment Utility
What's the IP config of your client and IP address of the ADServer at the new site?

MO
0
 

Author Comment

by:AndreYPB
Comment Utility
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
0
 
LVL 16

Expert Comment

by:Michael Ortega (Internetwerx, Inc.)
Comment Utility
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
0
 

Author Comment

by:AndreYPB
Comment Utility
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"
0
 
LVL 16

Accepted Solution

by:
Michael Ortega (Internetwerx, Inc.) earned 500 total points
Comment Utility
I would remove the router's ip from DNS. You just want your ADServer in there at least during the joining process. If you want to add it back after the fact feel free although it is not recommended. It's known to cause issues like these as well as domain logon issues.

MO
0
 

Author Comment

by:AndreYPB
Comment Utility
OK just to confirm - to remove the router as dns I amend the static details on the ADServer's adapter?
0
 
LVL 16

Expert Comment

by:Michael Ortega (Internetwerx, Inc.)
Comment Utility
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
0
Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

 
LVL 16

Expert Comment

by:Michael Ortega (Internetwerx, Inc.)
Comment Utility
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
0
 

Author Comment

by:AndreYPB
Comment Utility
Ok i have that configured - however the clients can no longer access the internet :-(
0
 

Author Comment

by:AndreYPB
Comment Utility
Ignore that last comment - internet is fine o0 stupid win 7 network centre reporting no internet access
0
 

Author Comment

by:AndreYPB
Comment Utility
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.
0
 
LVL 16

Expert Comment

by:Michael Ortega (Internetwerx, Inc.)
Comment Utility
Worked after the reboot?

MO
0
 

Author Comment

by:AndreYPB
Comment Utility
It sure did - thanks - going to join the other PCs to the DC now too ;-)
0
 
LVL 16

Expert Comment

by:Michael Ortega (Internetwerx, Inc.)
Comment Utility
Way to go!

MO
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Join & Write a Comment

One of the most often confused topics in the area DNS is the idea of GLUE records. Specifically, what they are, when they are needed, when they are provided, and how they are created. First, WHAT IS GLUE? To understand GLUE, you must first under…
Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now