iljig
asked on
Time Synchronization (Client Server) Error at log on.
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.
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.
ASKER
Hi Bob
Thanks for your suggestion. I have checked the event logs for both DCs, & there are the mrxsmb 3034 errors. I tired your time fix but find myself in the same situation, which is:
If I turn the workstations off for a while, users can sometimes log in without problems. But, for example, if they log off, & log back on a few minutes later the problem can reoccur. On some people's PCs, like my own, the problem seems to have stopped a few days ago.
I'm stumped. Is it a network connectivity problem?
Iljig
Thanks for your suggestion. I have checked the event logs for both DCs, & there are the mrxsmb 3034 errors. I tired your time fix but find myself in the same situation, which is:
If I turn the workstations off for a while, users can sometimes log in without problems. But, for example, if they log off, & log back on a few minutes later the problem can reoccur. On some people's PCs, like my own, the problem seems to have stopped a few days ago.
I'm stumped. Is it a network connectivity problem?
Iljig
ASKER
After we took the old DC out of the picture, the problem worsened with no-one being able to log on. We pointed every PC to use the PDC emulator as time source (creating an NtpServer value in the W32Time Key), shut down the machines for a few minutes & also disconnected the power, restarted & found we could log in.
That was all fine until about 5 this afternoon when our network started being flooded with packets from somewhere, & now none of the machines can connect to the time server again, & none of us can log in.
Maybe we should just rebuild the whole domain. Any suggestions, anyone?
Iljig
That was all fine until about 5 this afternoon when our network started being flooded with packets from somewhere, & now none of the machines can connect to the time server again, & none of us can log in.
Maybe we should just rebuild the whole domain. Any suggestions, anyone?
Iljig
ASKER
We ended up rebuilding the domain completely, as there were originally connectivity problems between the two company offices, & we thought it better to start from the ground up again.
Thanks for everyone's comments. It was too tough a nut for me to cract!
Thanks for everyone's comments. It was too tough a nut for me to cract!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have a medium sized environment with one PDC that serves all the clients. I added a new DC to spread the traffic, and I initially had clients with "time synch" errors when they tried to login (it prevented login altogether). But when I checked, both the PDC and new DC had identical times down to the second. So why the time synch error?
Although my clients still have problems if I leave the new DC running, I am no longer getting the time synch error per se. On the PDC, I used regedit to set the value for this PC is a "reliable time server". Plus, I manually told the DC to get its time from the PDC - - - - although that is supposed to occur automatically. But I wasn't taking chances. For this info, get the WhitePaper from Microsoft on "The Windows Time Service".
On your DC, do you get any of these errors in the event viewer? "userenv 1000" in the application log or "mrxsmb 3034" in the system log? The mrxsmb 3034 is puzzling, but with some work I traced the code itself to an error that has to do with....you guessed it...the time. Why?!
-Bob