Our WIN2K domain originally had two DCs & 1 DNS server. After adding an additional DC & integrating it into ADS some WIN2k Pro workstations started receiving time synch errors on logging in. After rebooting they could then log in.
After one of the original two DCs failed we added an second addtional DC, & then the workstations & some of the member & domain servers are now unable to log into the domain (some can). If you log on locally to the server you will notice that the time is the same as all the other servers. About 40 percent of the workstations cannot log in the domain, & it is always the same machines that have the problem. Rebooting once used to fix the problem, now some of the machines simply will not allow you to log in to the domain at all.
Although we receive the time sync error at logon I don't know if that really is the problem, since the domain worked normally before the first new DC was added. We have the one of the original two DCs still on line, & it doesn't seem to make any difference is this turned on or not. However, I'm afraid of removing it from ADS in case we find none of our machines can log on.
Does anyone have any idea what's going on, because I surely don't. Any suggestions welcome.