win2000 AD out of synch for more than 90 days

Hi,  have one win2k AD in win2003 environment that is out of sync with other DC for more than 90 days for some unknown reason.  I tried to manually force it to synch but failed.  Anyway, I remember reading somewhere you can't force a DC to sync if it is out of sync for more than 90 days.  You have to practically rebuild that DC.  Does anyone know if this claim is correct?  if not, then what is the best way for me to fix this problem?  thanks for your helps
Who is Participating?
this is correct - if the server has been offline that long that you need to demote the DC using DCPROMO and then promote the DC backin

the data simple gets to old on the offline machine to update and fix
Did you convert the domain to Windows 2003 mode?  If you did, then you will need to upgrade the Windows 2000 DC to a Windows 2003 server.

If this is not the case, check your bridgehead connections.  This is done from Active Directory Sites and Services MMC.
We had a simlar problem but it wasnt until the netlogon and sysvol shares had disappeared from the server we noticed.
if you run through the following tech article it should solve your problem
once this had been done it resynced our active directory as well.

Hope this helps
If the DC was to long out of sync (I think it was 60 days = tombestone lifetime) you need to remove it from your domain and reinstall/dcpromo it back again.

If a normal DC-de-promo does not work, you need to do a dcpromo /forceremoval and cleanup the AD with metadatacleanup, etc...
vayohaAuthor Commented:
thank you all for the quick response.  I will go with the demo, clean up metadata at all of other domains and then promo it again.  Lets see how it goes.  
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.