Re: AD replication

yes, it has _msdcs.domain.com at the root domain. As this is the only DC in
the child domain, I remove DNS from the child domain DC during weekend, and
after few minutes, I install the DNS on the same child domain DC, it still
had the same forward lookup zone, I could not find _msdcs.domain.com in the
child domain DC, what should I do next?

Thank you much for you help.
Irene


"Jorge Silva" wrote:

Is the _msdcs.domain.com at the root domain?

--
===================================
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
===================================

"Irene" <Irene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F3B2934-2EBF-4CC9-B38D-F8F1AD005DC4@xxxxxxxxxxxxxxxx
Hi Jorge,

Thanks for you quick answer.

Actually, I could not find _msdcs.domain.com, and all the others subfolder
under child domain DNS forward lookup zone, how can I get all the
_msdcs,_sites,_tcp,_udp back in child domain DNS forward lookup zone.

Thanks again for you help
Irene

"Jorge Silva" wrote:

Ok, after I re-read your post I noitice that the failures are regarding
to a
old DC GUID correct?
Do you have the _msdcs zone in the child domain?
Can you confirm if the old GUID for DC1 is there (is CNAME record and
it's
under _msdcs.domain.com, and you can confirm the GUID for that DC under
NTDS
Settings for that DC in Active Directory Sites and Services)?
Assuming that the GUID that the DC2 is trying to use to replicate no
longer
exists, you may try to delete that old/invalid GUI and recreate a new
CNAME
for the correct GUID, then try replication on the DC2.
--
===================================
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
===================================

"Irene" <Irene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8F9008D8-AE4F-4035-B76E-032A61F61EC2@xxxxxxxxxxxxxxxx
Hi Jorge,

Before I upgrade the schema version to windows 2003 R2, even " Last
success @ 2006-05-09 08:48:13" , I still can move accounts between
child
domain and parent domain, but after upgrade forest to 2003 R2 schema
version
31, the child domain can not replicate with parent domain as the schema
version still at 30, we have about 10 users in that subdomain, is there
a
way
to delete the users from subdomain, and create with the same name as
they
used before in parent domain, we need demote the child domain from
forest.

Thanks
Irene

"Jorge Silva" wrote:

Hi
Unless you have a uge default tombstonelifetime in your forest this "
Last
success @ 2006-05-09 08:48:13" means that your child domian is dead to
the
forest.
Now the only option is to manually remove it from your forest and
rebuild
it
again from the beginning.

--
===================================
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
===================================

"Irene" <Irene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:80A39414-A004-4815-8975-5B56FC5F049A@xxxxxxxxxxxxxxxx
Hi Guys,

we have an AD contain 5 subdomain, 20 days again, I tried to upgrad
a
Windows 2003 R2 server to DC, which it need upgrade the forest, then
I
run
adprep /forest on the DC1 which is schema master DC, the system
upgrade
the
schema to version 31 on 4 subsdomans except one domain COS is still
version
30, then the AD replication betwenn COS DC2 to main domain stoped.
and
DC2
is
the only DC in the subdomain of COS. our plan is merge subdomain COS
to
main
domain, but now the AD stop replicated between those 2 domains, any
action
I
did on the COS domain could not replicate to main domain. the
following
is
the repadmin /showrepl on both DCs, please help me the fix this
issue
ASAP.

please note, the GUID for schema master DC1 is different from the
result
of
two DC, we rebuilt our DC1 last year, looks like the DC2 still has
the
old
DC1 GUID. so, How can I simply change the schema version to 31 on
COS
DC2,
and how can I easliy let COS DC2 know the DC1 has differrent GUID.


repadmin running on DC1
repadmin running command /showrepl against server localhost
WGCCHQ\DC1
DC Options: IS_GC
Site Options: (none)
DC object GUID: d2269f42-ec2f-4469-8864-5de4bc6adbac
DC invocationID: 2eaf16ca-d685-4ff1-bf76-f67c2e6a6150

==== INBOUND NEIGHBORS ==========

DC=main,DC=com
CN=Configuration,DC=main,DC=com
COS\DC2 via RPC
DC object GUID: 5bbe5009-7cc9-4bff-9bed-874557f5435c
Last attempt @ 2007-10-15 18:20:29 failed, result 8418
(0x20e2):
The replication operation failed because of a schema
mismatch
between the servers involved.
34 consecutive failure(s).
Last success @ 2007-09-25 16:24:15.
CN=Schema,CN=Configuration,DC=main,DC=com
COS\DC2 via RPC
DC object GUID: 5bbe5009-7cc9-4bff-9bed-874557f5435c
Last attempt @ 2007-10-15 18:20:29 was successful.
DC=DomainDnsZones,DC=main,DC=com
DC=ForestDnsZones,DC=main,DC=com
COS\DC2 via RPC
DC object GUID: 5bbe5009-7cc9-4bff-9bed-874557f5435c
Last attempt @ 2007-10-15 18:20:30 failed, result 8418
(0x20e2):
The replication operation failed because of a schema
mismatch
between the servers involved.
34 consecutive failure(s).
Last success @ 2007-09-25 16:07:28.
DC=Subdomain,DC=main,DC=com
COS\DC2via RPC
DC object GUID: 5bbe5009-7cc9-4bff-9bed-874557f5435c
Last attempt @ 2007-10-15 18:20:30 failed, result 8418
(0x20e2):
The replication operation failed because of a schema
mismatch
between the servers involved.
34 consecutive failure(s).
Last success @ 2007-09-25 16:07:29.
DC=Cos,DC=main,DC=com
COS\DC2 via RPC
DC object GUID: 5bbe5009-7cc9-4bff-9bed-874557f5435c
Last attempt @ 2007-10-15 18:20:33 failed, result 8418
(0x20e2):
The replication operation failed because of a schema
mismatch
between the servers involved.
34 consecutive failure(s).
Last success @ 2007-09-25 16:07:33.
Source: COS\DC2
******* 34 CONSECUTIVE FAILURES since 2007-09-25 16:33:49
Last error: 8418 (0x20e2):
The replication operation failed because of a schema
mismatch
between the servers involved.


repadmin /showrepl running on subdomain DC2
repadmin running command /showrepl against server localhost
COS\DC2
DC Options: IS_GC
Site Options: (none)
DC object GUID: 5bbe5009-7cc9-4bff-9bed-874557f5435c
DC invocationID: 8d5432ba-928c-4a57-8c8d-427fe9a63c26


==== INBOUND NEIGHBORS ===================
CN=Configuration,DC=main,DC=com
WGCCHQ\DC1 via RPC
DC object GUID: d110d01f-67c8-4962-a461-08254136208e
Last attempt @ 2007-10-15 17:47:07 failed, result 8452
(0x2104):
The naming context is in the process of being removed or
is
not
replicated from the specified server.
12499 consecutive failure(s).
Last success @ 2006-05-09 08:48:13.
CN=Schema,CN=Configuration,DC=main,DC=com
WGCCHQ\DC1 via RPC
DC object GUID: d110d01f-67c8-4962-a461-08254136208e
Last attempt @ 2007-10-15 17:47:08 failed, result 8452
(0x2104):
The naming context is in the process of being removed or
is
not
replicated from the specified server.
12495 consecutive failure(s).
Last success @ 2006-05-09 08:48:13.
DC=ForestDnsZones,DC=main,DC=com
WGCCHQ\DC1 via RPC
DC object GUID: d110d01f-67c8-4962-a461-08254136208e
Last attempt @ 2007-10-15 17:47:08 failed, result 8452
(0x2104):
The naming context is in the process of being removed or
is
not
replicated from the specified server.
12495 consecutive failure(s).
Last success @ 2006-05-09 08:48:13.
DC=main,DC=com
WGCCHQ\DC1 via RPC
DC object GUID: d110d01f-67c8-4962-a461-08254136208e
Last attempt @ 2007-10-15 17:47:11 failed, result 8452
(0x2104):
The naming context is in the process of being removed or
is
not
replicated from the specified server.
12497 consecutive failure(s).
Last success @ 2006-05-09 08:48:13.
Source: WGCCHQ\DC1
******* 12499 CONSECUTIVE FAILURES since 2006-05-09 08:48:14
Last error: 8452 (0x2104):
The naming context is in the process of being removed or
is
not
replicated from the specified server.

Thans in advance.









.

Relevant Pages

  • Re: Unable to Raise Domain Functional Level
    ... that directory replication is healthy on multiple test passes. ... Should I check the remaining child domain and root domain to ... The server that DCDiag complains about is CNR-PR-DOMA00 ... are indicating the servers are receiving their DNS settings via DHCP. ...
    (microsoft.public.windows.server.migration)
  • Re: adprep /forestprep failure
    ... If I understand correctly, I don't expect to see anything for replication, ... because there is currently only one DC in the domain and forest, spserver01. ... The win 2003 server is not yet a DC, ... Schema FSMO holder shows spserver01.season.com. ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD replication
    ... Before I upgrade the schema version to windows 2003 R2, ... Windows 2003 R2 server to DC, which it need upgrade the forest, then ... then the AD replication betwenn COS DC2 to main domain stoped. ... COS\DC2 via RPC ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD replication
    ... Before I upgrade the schema version to windows 2003 R2, ... Windows 2003 R2 server to DC, which it need upgrade the forest, then I ... then the AD replication betwenn COS DC2 to main domain stoped. ... COS\DC2 via RPC ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD replication
    ... Assuming DC1 for the Root Domain, and DC2 for the child domain: ... NtdsSettings -> all tasks and choose check replication topology, ... Before I upgrade the schema version to windows 2003 R2, ...
    (microsoft.public.windows.server.active_directory)
Loading