• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1508
  • Last Modified:

Can't join Windows Server 2008 to Server 2003 domain

I've got a new Windows Server 2008 R2 machine that I'm using to replace a Windows Server 2003 machine.  I'm at the very beginning and am trying to join the 2008 server to the 2003 domain.  When I do  so, I'm getting the following error message:

An Active Directory Domain Controller (AD DC) for the domain "domain.local" could not be contacted.  

In the details of the error message, I get this information

The error was "This operation returned because the timeout period expired"

When I look on the 2003 server, I get a DNS error 7062 below, where is the IP address of the 2003 server.

The DNS server encountered a packet addressed to itself on IP address The packet is for the DNS name "_ldap._tcp.dc._msdcs.domain.local.". The packet will be discarded. This condition usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
  1) Forwarders list. (DNS servers should not forward to themselves).
  2) Master lists of secondary zones.
  3) Notify lists of primary zones.
  4) Delegations of subzones.  Must not contain NS record for this DNS server unless subzone is also on this server.
  5) Root hints.
Example of self-delegation:
  -> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com.
  -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,
  (bar.example.microsoft.com NS dns1.example.microsoft.com)
  -> BUT the bar.example.microsoft.com zone is NOT on this server.
Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result.  If found, the subzone DNS server admin should remove the offending NS record.
You can use the DNS server debug logging facility to track down the cause of this problem.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The DNS on the 2008 server is pointing toward the 2003 server.  I've tried clearing the DNS cache on the 2003 server as well as deleting and adding back the forwarders & root hints.

Any help would be appreciated.  Much thanks!
  • 4
  • 2
  • 2
  • +2
1 Solution
You don't need to prep just to join the domain.

It sounds like the IP of the new 2008 machine is the same as the 2003 machine

Check the IP and mask of the machines
VirastaRUC Tech Consultant Commented:

This might be a very basic question,
=> Where u able to ping the Windows 2003 Server by IP Address?
=> Where u able to ping the FQDN of the Windows 2003 server?

Are you getting replies? if YES and still not working please post the system info from both Windows 2003 and the Windows 2008 Machine for further investigation.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Does the 2003 DNS server have forward lookup zones named domain.local and _msdcs.domain.local, or does the domain.local zone contain an _msdcs folder? It sounds like this part of the DNS configuration may be screwed up in some way.
SupermanTBAuthor Commented:
Thanks for everyone's help.  Here are the answers to all your questions:

NRhode:  I don't believe the prep is necessary in order to just join the domain.  I have definitely not done it yet though.

KCTS:  The IP address of the 2003 server is and the IP address of the 2008 server is being assigned dynamically.  The SM for both machines is

virastar:  I can ping the 2003 server by both IP address and FQDN name.  System Info is attached

DrDave242:  The DNS on the 2003 server only has one forward lookup zone named domain.local containing an _msdcs folder.  The _msdcs folder does appear to be grey color while the other folders are more yellow.  There are also no sub folders under _msdcs.  The only entry for _msdcs is

(same as parent folder)
Name Server (NS)
VirastaRUC Tech Consultant Commented:
by: SupermanTBPosted on 2013-11-25 at 19:44:20ID: 39674655

KCTS:  The IP address of the 2003 server is and the IP address of the 2008 server is being assigned dynamically.  The SM for both machines is

May I know why the IP Address of the Windows 2008 is dynamic ?

Can you please try settings the same IP as static and try joining the domain?
Also try a different host name for Windows 2008 Server and try joining again.

SupermanTBAuthor Commented:
I have tried setting the 2008 IP address as static and got the same problem.  I've also tried changing the computer name of the 2008 server as well.

No luck
DrDave242:  The DNS on the 2003 server only has one forward lookup zone named domain.local containing an _msdcs folder.  The _msdcs folder does appear to be grey color while the other folders are more yellow.  There are also no sub folders under _msdcs.
OK, this is at least part of the problem. That gray _msdcs folder is a delegation record, and it will only contain name server (NS) records for each of your DNS servers. Since the delegation is present, there should also be a separate _msdcs.domain.local zone present, but it sounds like this zone is missing in your case. Fortunately, recreating it isn't hard.

In the DNS console, right-click Forward Lookup Zones and select New Zone. Provide the following information when prompted by the New Zone wizard:

Zone type: Primary
Store the zone in Active Directory.
Replicate the zone to all DNS servers running on DCs in the forest.
Name the zone _msdcs.domain.local (substituting your domain name, of course).
Allow only secure dynamic updates.

After the zone has been created, close the DNS console, open a command prompt on the DC, and run these four commands:

ipconfig /flushdns
ipconfig /registerdns
net stop netlogon
net start netlogon
Wait a few minutes, then open the DNS console and look at the contents of the new zone. It should contain a single SOA record, NS and CNAME records for each DC, and folders named dc, domains, gc, and pdc. Each folder will contain records and/or subfolders, but if the folders themselves are all there, it's probably safe to assume everything is intact. Run ipconfig /flushdns on the 2008 R2 server and try to join it to the domain again.
SupermanTBAuthor Commented:
Awesome.  I'm away from a computer, but will give this a try tomorrow.
SupermanTBAuthor Commented:
This solved my problem.  The new zone populated exactly as you said it would.  Thanks very much for the help!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 4
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now