On Feb 12, 2008 3:55 PM, yoth <[EMAIL PROTECTED]> wrote: > The weird thing is that the DC was only disconnected for a day and that was > less than a week ago.
Right, but are you sure it was actually replicating with the other DC? The reason I know so much about this is that I once got called into a customer who had several DCs, none of which had been replicating with each other for at least six months. They had IP connectivity, but other issues had disrupted AD replication. What a mess that was. It's also possible the AD database is somehow damaged on one of the DCs. > These are the only DCs in the domain. Okay, so I think your best bet is to check to see if the AD domain databases on the two DCs agree with each other. If you find discrepancies between the two, that's evidence that replication isn't happening for real. There's a tool called DSASTAT (Support Tools) that's supposed to compare info between DCs. I've never used it. You can try logging in on one of the DCs, looking in "Active Directory Users and Computers", finding some object that should have been updated recently, and noting timestamps and USNs. Do the same on the other DC. Compare. Repeat for some other objects. You might also try running NETDIAG and DCDIAG from the Support Tools. > If I was going to depromo one of them I would want to do the one that went > down, but that isn't an option I think since > it is also an Exchange server...according to MS demoting an exchange server > can cause issues with Exchange. Yah... it might just be time to call MS PSS and pay the $250 to get some expert help. -- Ben ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
