Fooling around with ntdsutil and metadata cleanup or ADSIedit should
give you some hints about the name of the DC(s) that's (are) missing. If
its missing on purpose, you need to do the metadata cleanup for the
server to get rid of it completely
(http://support.microsoft.com/default.aspx?scid=kb;en-us;216498) or if
that server should be online, you need to demote it, do the same
cleanup, fix the network connection, then promote it again. I don't know
if there's any way of fixing a DC that has been isolated for too long,
but if there is, its not probably worth the trouble since
demoting-promoting is a pretty straightforward and simple procedure.


-Sami

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kamlesh Parmar
Sent: 30. elokuuta 2005 22:21
To: [email protected]
Subject: Re: [ActiveDir] Replication problems!

It seems you have not been watching your logs frequently...

One of the DC has not replicated with this DC beyond tombstone
lifetime...
it could be a DC which was taken offline abruptly, without properly
demoting it.

run dcdiag.exe on that server it will tell you, which other DCs it is
not able to replicate.



On 8/30/05, Wilhelmsen Jan <[EMAIL PROTECTED]> wrote:
>  
> 
> Hi! 
> 
> I have noticed that on my DC i got several entries in the Directory 
> service event log
> 
> Event Type:     Error 
> 
> Event Source:   NTDS Replication 
> 
> Event Category: Replication
> 
> Event ID:       1864 
> 
> Date:           29.08.2005 
> 
> Time:           10:40:14 
> 
> User:           NT AUTHORITY\ANONYMOUS LOGON 
> 
> Computer:       domcontroller1 
> 
> Description: 
> 
> This is the replication status for the following directory partition 
> on the local domain controller.
> 
>   
> 
> Directory partition: 
> 
> DC=DomainDnsZones,DC=mydomain,DC=net
> 
>   
> 
> The local domain controller has not recently received replication
> information from a number of domain controllers.   The count of domain
> controllers is shown, divided into the following intervals. 
> 
>   
> 
> More than 24 hours: 
> 
> 1
> 
> More than a week: 
> 
> 1
> 
> More than one month: 
> 
> 1
> 
> More than two months: 
> 
> 1
> 
> More than a tombstone lifetime: 
> 
> 1
> 
> Tombstone lifetime (days): 
> 
> 60
> 
> I run the command : repadmin /showvector /latency dc=mydomain,dc=net
> 
> And the result shows the following output: 
> 
> 0de822b5-b8da-4f0e-82a1-66ec9407b8f3    @ USN     26321 @
> Time (unknown)
> 
> 1f2ff24b-496b-47e9-a735-089bd8f57285    @ USN   2175489 @
> Time 2004-11-28 16:06:20
> 
> How can I fix this problem, there is obvious that this server has not 
> been replicated for a while but I can't seem to figure out which
servers it is.
> 
> If I run repadmin /showreps /v domcontroller1, I can all successful 
> and no errors.
> 
> Can anyone provide me with some tips on how to attack this problem? 
> 
> I also noticed that in one particular OU I cannot copy a user but if I

> create a new user in the OU there is no problem.
> 
> When I try to copy a user I get this error message after I press oko 
> for the creation of the new user.
> 
> Stop box: 
> 
> Windows cannot create the oobject test user because: 
> 
> The Name reference is invalid: 
>  
> 
> Thanks in advance: 
> 
> Jan


-- 
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Fortune and Love befriend the bold"
~~~~~~~~~~~~~~~~~~~~~~~~~~~
List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

Reply via email to