NTDS Replication Event_ID 1864
i getting following error on ntds replication on 1 of domain controllers, appreciated.
this replication status following directory partition on local domain controller.
directory partition:
cn=schema,cn=configuration,dc=d214,dc=org
cn=configuration,dc=d214,dc=org
dc=d214,dc=org
the local domain controller has not received replication information number of domain controllers. count of domain controllers shown, divided following intervals.
more 24 hours:
1
more week:
1
more 1 month:
1
more 2 months:
1
more tombstone lifetime:
0
tombstone lifetime (days):
180
domain controllers not replicate in timely manner may encounter errors. may miss password changes , unable authenticate. dc has not replicated in tombstone lifetime may have missed deletion of objects, , may automatically blocked future replication until reconciled.
to identify domain controllers name, install support tools included on installation cd , run dcdiag.exe.
you can use support tool repadmin.exe display replication latencies of domain controllers in forest. command "repadmin /showvector /latency <partition-dn>".
for more information, see , support center @ http://go.microsoft.com/fwlink/events.asp.
ikram hussain
hello,
please upload following files , describe domain setup, amount of dcs , how located, changes done before started:
ipconfig /all >c:\ipconfig.txt [from each dc/dns server]
dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt ["dc* place holder starting name of dcs if begin same (if more 1 dc exists)]
dnslint /ad /s "dcipaddress" (http://support.microsoft.com/kb/321045)
output become large, don't post them thread, please use windows sky drive (skydrive.live.com) [with open access!] , add link here. /e in dcdiag scans complete forest, better run on cob.
best regards meinolf weber disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights.
Windows Server > Directory Services
Comments
Post a Comment