|
When running repadmin /showreps on one of
the good DCs I get the following message only under cn=configuration Last attempt @ 2005-05-21 19:48.33 failed,
result 8614: The Active Directory cannot replicate with
this server because the time since the last replication with this server has
exceeded the tombstone lifetime. Last success @ 1952-08-19 22:59.10. 5823 consecutive failure(s). I agree…I’m already preparing
to rebuild this server…. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe I am confused, the config is the only
partition not replicating? If the DC is not replicating due to being to far out
because of TLS issues then it shouldn't be replicating anything. Anytime you get into a position like that,
I agree with Rick, mow the DC down and start over. joe From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Fontana I have a DC that appears to have had some time synch
problems before I got here… Subsequently, all other DCs have
discontinued replication for the cn=configuration (per repadmin) with this
DC. My question is; the first event I can see showing replication
problems with this DC is on April 8th, which should mean that
I’m not past the 60 day garbage collection period. It seems to me
that I could modify the reg setting to allow the other DCs to resume
replication and no lingering objects would be reintroduced because the deleted
object info is still present. The offending DC is running Windows 2000
SP3. Any thoughts? TIA -Alex |
- RE: [ActiveDir] Replication failures - lingering ob... Alex Fontana
- RE: [ActiveDir] Replication failures - lingeri... joe
- RE: [ActiveDir] Replication failures - lingeri... Jorge de Almeida Pinto
- RE: [ActiveDir] Replication failures - lingeri... Alex Fontana
