Home > Ask the Windows Server Experts > Questions & Answers > Migrating the Active Directory database to a new domain
Ask The Windows Server Expert: Questions & Answers
EMAIL THIS

Migrating the Active Directory database to a new domain

Paul Hinsberg EXPERT RESPONSE FROM: Paul Hinsberg

Pose a Question
Other Windows Server Categories
Meet all Windows Server Experts
Become an Expert for this site


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


>
QUESTION POSED ON: 30 November 2004
I need to migrate the Active Directory database from one domain to a newly created one. The domains are in different forests, and I do not want to go with a domain rename. I need advice on the best migration tool to use from Windows 2000 to Windows Server 2003, because I keep receiving "network path cannot be found error 53" when using the ADMT tool from Microsoft.


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   



RELATED CONTENT
Microsoft Active Directory Migration
What factors need to be considered during an NT4 to Windows Server 2003 migration?
Changes to Active Directory: Windows Server 2003 SP1
Active Directory for Windows 2000 and 2003: What's the difference?
Will Exchange migrate easily from NT4 to Windows 2003 with Active Directory?
Active Directory issues to look for when upgrading from Windows 2000 to Windows 2003 Server
Steps to migrate from Windows NT to Windows 2003 Active Directory
Learning guide: Migrating to Windows Server 2003
Moving DHCP without interruption during an Active Directory migration
Chapter of the Week: Windows Server Undocumented Solutions -- Chapter 6, 'Server management'
Changing NTDS links with Active Directory

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


The ADMT is one of the better ones (especially since it is free). Let's look at the issue of the error 53. This is usually an indication of an error in the name resolution. The best way to resolve that is to make the Domain Controllers in the new domain secondary DNS servers for the first domain's DNS zone and vice versa. So you end up with copies of both zones in the DNS of both domains. The next issue can be one of security. If there is a firewall or any packet filtering going on between the two domains, it could result in this type of problem. Check with the networking engineers and see if they can review the firewall or the network logs for issues or rejected packets. The error 53, is very generic and occurs are the networking level -- not the application level. Thus, if you don't resolve the root problem, no tool will work.

Additional Expert Help:
Be sure to check our Answer FAQ for more expert advice.
For faster answers, visit ITKnowledge Exchange.




Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice



Windows Server Solutions - Intel Hardware Solutions
HomeTopicsBlogsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2004 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts