Re: Replication problems

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Jorge,

I was hoping that you would chime in.....

I was going to attack this with a whole lot of troubleshooting....I will add
my comments in a reply...

Thanks,

--
Cary W. Shultz
Roanoke, VA 24012
"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:A38823A7-10C1-41E9-A682-A6C37E6A14FB@xxxxxxxxxxxxxxxx
Hi Joao
Sounds like your DC failed to replicate whithin the Tombstonelifetime
period, generally the best option is to demote (perform metadata cleanup)
the LESS updated DC seize any fsmo roles helded by that DC and then using
the dcpromo /forceremoval switch take the AD off that DC and then add it
again the Domain as normal process. In future pay a litle more attention
to the replication process ny monitring that operation(s).
also ahave a look at:
http://technet2.microsoft.com/windowsserver/en/library/34c15446-b47f-4d51-8e4a-c14527060f901033.mspx?mfr=true


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

Jorge Silva
MCSE, MVP Directory Services
"Joao Luis Rita" <JoaoLuisRita@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:86EE3538-F588-4F5B-A868-9D4CA07DF4DE@xxxxxxxxxxxxxxxx
Hello all

I need some ideas for the following problems.

We have 2 main Windows 2003 servers, PDC1 and PDC2 (service pack 1). A
few
days ago, the 2 servers apparently stopped replicating each other. Some
users
couldn't log in, others received messages stating their PC account didn't
exist. I checked the users/computers listings on the servers and some PCs
are
in PDC2 while not being in PDC1. I checked the event viewer: the
"directory
service" log is full of replication errors. All the errors fall in 3
events
IDs-1864, 2042, 2092. I've checked Technet, and all seem to point to
firewall
problems. However we have no firewall between these servers.

I've been forced to shutdown PDC2 to stop all these errors.
Unfortunately,
the person that usually handles these problems is on vacation, and after
2mn
on the phone he said he may have to format/reinstall PDC2, when he
returns.

Anyone has any ideas about this? I'd like to avoid the whole
format/reinstall.

Any way we can maybe force a replication, using PDC1 as base (it seems to
have the most updated listings)?




.

Relevant Pages

  • Re: Replication problems
    ... I checked the users/computers listings on the servers and some PCs ... I've been forced to shutdown PDC2 to stop all these errors. ... on the phone he said he may have to format/reinstall PDC2, ... Any way we can maybe force a replication, using PDC1 as base (it seems to ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
    ... Ethernet adapter PUBLIC: ... regarding EX-DC3 replication look interesting...anyway, ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
    ... regarding EX-DC3 replication look interesting...anyway, ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
    ... DC's should NOT be multihomed, this creates lot's of problems, especially with replication. ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
    (microsoft.public.windows.server.active_directory)
  • RE: Global Katalog defekt
    ... also im Active Directory ist der Haken bei GC gesetzt. ... Identifying all servers. ... Active Directory LDAP Services Check ... The replication generated an error: ...
    (microsoft.public.de.german.win2000.active_directory)