<div>
I've no idea what you're missing since you didn't give an error message ... that always helps :0) 
 
It's almost always related to DNS, so in the absence of any detail, I'd receommend you start there. 
 
PS - this use of terminology doesn't apply, could you explain what you mean - 
 
&gt;&gt;&nbsp;The only DC in the domain tombstoned 
</div>

<div>
Well I'm not getting an error message. I have a parent domain with 2 child domains. One of the child domains started acting up before I started here at this job. My first task is to resolve this issue. I logged into the parent domain DC and say there had been no replication since june. As that is over 60 day's I'm assuming the child domains only DC had hit it's tombstone limit. I built a new DC in that child domain and moved everything (GC, and all fsmo roles) to it. I then domoted the first DC in that child domain. Now the new DC shows it is replicating fine, but the Parent DC does not list the new DC in sites and services or under the replication monitor. (the new DC in the child domain shows the parent DC in it's sites and servicea dn seem to replicate fine with it.) So How do I get the Parent to talk to the child... 
</div>

<div>
If you run DSSITE.MSC and try to force replication between the parent and child, you should receive an interactive error. 
 
In addition, it's likely you'll need this reg tweak - 
 
<a href="http://technet2.microsoft.com/windowsserver/en/library/34c15446-b47f-4d51-8e4a-c14527060f901033.mspx?mfr=true" rel="ugc nofollow">http://technet2.microsoft.com/windowsserver/en/library/34c15446-b47f-4d51-8e4a-c14527060f901033.mspx?mfr=true</a> 
 
... 100% relevant stuff starts at the section titled &quot;Restart Replication Following Event ID 2042&quot; 
 
NOTE - you may want to read up on lingering objects - 
 
<a href="http://technet2.microsoft.com/windowsserver/en/library/4a1f420d-25d6-417c-9d8b-6e22f472ef3c1033.mspx?mfr=true" rel="ugc nofollow">http://technet2.microsoft.com/windowsserver/en/library/4a1f420d-25d6-417c-9d8b-6e22f472ef3c1033.mspx?mfr=true</a> 
 
... before you proceed since it's an almost certainty that you'll introduce some. 
 
PS - what OS are your DCs running and how old is this AD?
</div>

<div>
They are all server 2003...but it's 2000 AD. I just noticed the child domain is running 2000 mixed and the parent is 2000 native. Would that cause an issue? 
 
I'm not sure how old the AD is... 
 
When I run dssite.msc it works fine on the chils but on the parent I don't even show the child domains DC to try to force the replication.... 
 

</div>

<div>
Wow ... that's not good. &nbsp;This appears to be quite a serious issue. &nbsp;I'm not going to have time today to walk through the process of determining the cause and a subsequent fix so I'll have to bail out for now. &nbsp;I hope someone else picks it up for you. &nbsp;I'll try and take a look again tomorrow ...
</div>

<div>
So it really looks like my parent domain just does nto see the child in Sites and services. It sees it in DNS, and AD users and computes. I can ping it, connect to it, even verify the trust, I just can't get it to replicate down to it.
</div>

<div>
Hmmm ... what is it you're expecting to replicate? &nbsp;Parent and child domains share only the config, schema and some application partitions used by DNS (by default). &nbsp;They don't share domain content (GCs acknowledged). &nbsp;Logon at a root-domain DC as an admin and run these 2 commands at a command prompt - 
 
repadmin /syncall /e /P 
repadmin /syncall /e 
 
... paste the outback here. &nbsp;If you receive an error, install the Support Tools from the original CD or download them from Microsoft. 
 

</div>

<div>
Microsoft Windows [Version 5.2.3790] 
(C) Copyright 1985-2003 Microsoft Corp. 
 
C:\Documents and Settings\Administrator.MyDomain&gt;repadmin /syncall /e /P 
CALLBACK MESSAGE: The following replication is in progress: 
&nbsp; &nbsp; From: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 7a47d9b6-3283-41a1-90b3-3e5209970b19._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication completed successfully: 
&nbsp; &nbsp; From: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 7a47d9b6-3283-41a1-90b3-3e5209970b19._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication is in progress: 
&nbsp; &nbsp; From: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 3c1e2513-bb92-40d3-b624-9d9aeb52553b._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication completed successfully: 
&nbsp; &nbsp; From: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 3c1e2513-bb92-40d3-b624-9d9aeb52553b._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication is in progress: 
&nbsp; &nbsp; From: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 8fdfaa55-ec11-4ce9-914a-0e9d41609432._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication is in progress: 
&nbsp; &nbsp; From: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 02ebc903-dd3e-4608-897f-3baa99b01f6d._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication completed successfully: 
&nbsp; &nbsp; From: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 8fdfaa55-ec11-4ce9-914a-0e9d41609432._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication completed successfully: 
&nbsp; &nbsp; From: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 02ebc903-dd3e-4608-897f-3baa99b01f6d._msdcs.MyDomain.com 
CALLBACK MESSAGE: SyncAll Finished. 
SyncAll terminated with no errors. 
 
 
C:\Documents and Settings\Administrator.MyDomain&gt;repadmin /syncall /e 
CALLBACK MESSAGE: The following replication is in progress: 
&nbsp; &nbsp; From: 7a47d9b6-3283-41a1-90b3-3e5209970b19._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication completed successfully: 
&nbsp; &nbsp; From: 7a47d9b6-3283-41a1-90b3-3e5209970b19._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication is in progress: 
&nbsp; &nbsp; From: 3c1e2513-bb92-40d3-b624-9d9aeb52553b._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication completed successfully: 
&nbsp; &nbsp; From: 3c1e2513-bb92-40d3-b624-9d9aeb52553b._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication is in progress: 
&nbsp; &nbsp; From: 8fdfaa55-ec11-4ce9-914a-0e9d41609432._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication completed successfully: 
&nbsp; &nbsp; From: 8fdfaa55-ec11-4ce9-914a-0e9d41609432._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication is in progress: 
&nbsp; &nbsp; From: 02ebc903-dd3e-4608-897f-3baa99b01f6d._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
CALLBACK MESSAGE: The following replication completed successfully: 
&nbsp; &nbsp; From: 02ebc903-dd3e-4608-897f-3baa99b01f6d._msdcs.MyDomain.com 
&nbsp; &nbsp; To &nbsp;: 0d7584b0-074c-455a-8f2d-5e609e1238bb._msdcs.MyDomain.com 
CALLBACK MESSAGE: SyncAll Finished. 
SyncAll terminated with no errors.
</div>

<div>
That all looks fine to me. &nbsp;I've placed a copy of a DC dumping script on the following FTP server. &nbsp;Download it and run it from a command prompt followed by the FQDN of the forest root domain - 
 
<a href="ftp://falcon.msetechnology.com/scripts/DCdump.cmd.txt" rel="ugc">ftp://falcon.msetechnology.com/scripts/DCdump.cmd.txt</a> 
 
... e.g - 
 
C:\&gt; dcdump /? 
 
DCdump 1.0 / Dean Wells (dwells@somwehere.com) - May 2006 
 
SYNTAX - dcdump &lt;Forest Root FQDN&gt; [optional search string] 
 
&nbsp;Displays the FQDN, site and IP address of each Domain Controller 
&nbsp;within the Forest supplied in argument one 
&nbsp; - requires sufficient security context 
&nbsp; - argument two serves as a name-filter for site names and DC FQDNs 
 
C:\&gt; dcdump mset.lab 
 
DCdump 1.0 / Dean Wells (dwells@somewhereelse.com) - May 2006 
 
STATUS - Querying &quot;DC=mset,DC=lab&quot; 
 
&nbsp; - Running on CUBELET 
&nbsp; - Obtaining list of Domain Controllers 
 
&nbsp; &nbsp; [Default-First-Site-Name] 
&nbsp; &nbsp; &nbsp;+ CUBELET.mset.lab 
&nbsp; &nbsp; &nbsp; = 10.254.254.1 
&nbsp; &nbsp; &nbsp;+ enterprise.mset.lab 
&nbsp; &nbsp; &nbsp; = 10.254.254.2 
&nbsp; &nbsp; &nbsp;+ SPHERE.child.mset.lab 
&nbsp; &nbsp; &nbsp; = 10.254.254.3 
 
&nbsp; - 3 Domain Controller[s] found in 1 site[s]. 
 
STATUS - process complete. 

</div>

<div>
It lists out my servers for my parent and one child but not the other. When I run it for my chiild domain japan.mydomain.com I get 
 
error - ldap failed enumerating list of domain controllers 
 
now maybe it's my ignorance but when I run it for china.mydomain.com it runs but shows no DC's. Should that be? This is the first time I've dealt with child domains so I'm not quite up to speed here. 
 

</div>

<div>
Are you positive this is a child domain and not 2 discreet forests?
</div>

<div>
Sweet!!! That almost did it! I've got hem listed now, but It only set up one way replication child to parent not the other way. Well let me jump back when I try to force replicate from the child dc to the parent I get the child rpc server is unavailable.... 
 
When I try from the Parent down (under the child DC NTDS settings as it still does not show the child under the parent NTDS settings) I get access is denied.
</div>

<div>
Please, please be careful here ... blindly adding replica links may resolve what you perceive as your primary problem at the expense of a potentially more severe resulting condition -- lingering objects can cause many ill-effects. &nbsp;I'll keep my fingers crossed .......
</div>

<div>
Did you follow the steps in the link, and also do a repadmin /sync? &nbsp;Try that, if you haven't. &nbsp;It resolved my problems (and this was also PSS's recommendation, when I contacted them in my case, not just a jury-rig). &nbsp;Allow time for replication to occur, and then see what happens.
</div>

<div>
Ok I left tis over night and I'm now bacl to where I was. The child DC keeps getting event_id 1925,1926 errors saying it can't reach any other server due to rpc server being down, and the parent DC can't reach the child for the same reason. I've doing the net logon stop and starts and DNS &quot;looks&quot; ok, and I can ping from machine to machine, but I'm still having issues. 
 
The only thing I see jumping out is in my parent domins DNS in the _msdcs folder there are a bunch of cnames listed in the root folder, then there are the sub folders (dc,domains,gc,pdc) 
 
in the child domain I only have the sub folders dc,pdc in the _msdcs folder. Could this be my issue?
</div>

<div>
Turns out it was mainly a networking issue. The MTU settings were causeing an issue. Microsoft told me to switch it to use tcp to sync ad not udp. It seems to be working now.
</div>

<div>
<div class="content wysiwyg-content">
I've got a child domain that deosn't want to talk to my parent domain. The only DC in the domain tombstoned so I added a new DC and transfered all the roles to taht server. Now I can't get it to register on my parent dmina that this DC is there. It will replicate with the old server and another child dmina but not the parent. What am I missing?
</div>
</div>

I've got a child domain that deosn't want to talk to my parent domain. The only DC in the domain tombstoned so I added a new DC and transfered all the roles to taht server. Now I can't get it to register on my parent dmina that this DC is there. It will replicate with the old server and another child dmina but not the parent. What am I missing?

Force child domain to replicate with Parent

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.