Something else just occurred to me - our issue also occurred a few days after a weekend Windows server update/reboot cycle. I remember our Windows admin remarking after he'd fixed the DC problem that it had been a mistake to simultaneously reboot all the DCs. He said that apparently odd things can happen with the DCs' replication processes when one of them comes up and can't find any of the others. It's best to reboot them one at a time, allowing time between each reboot for the server to re-establish communication with the other DCs.
-John _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
