Computer Time and Network Time are Different
I've started to run into this message more and more over the course of the last two weeks or so. It started on a handful of Windows XP machines...they were unable to connect to the mail server because "the server time and workstation time are not the same". I was able to correct the problem by going to every machine and server and syncing the time via:
net time //DomainController \set \yes
Even though the time on all machines was correct (I checked, double-checked, and triple-checked). Same time, same date, same year, etc.
Anyway, the problems SEEMED to have gone away..until now. I just rebooted out mail server and now cannot log onto it with a network account because "the current time on this computer and the current time on the network are different".
But they aren't. I logged onto the server with the Admin account and ran the net time command to sync it with our DC. The command is successful, but I still get the same message. One thing that concerns me is that we just applied that "Daylight Savings patch" to the mail server earlier this week...could that have anything to do with it?
net time //DomainController \set \yes
Even though the time on all machines was correct (I checked, double-checked, and triple-checked). Same time, same date, same year, etc.
Anyway, the problems SEEMED to have gone away..until now. I just rebooted out mail server and now cannot log onto it with a network account because "the current time on this computer and the current time on the network are different".
But they aren't. I logged onto the server with the Admin account and ran the net time command to sync it with our DC. The command is successful, but I still get the same message. One thing that concerns me is that we just applied that "Daylight Savings patch" to the mail server earlier this week...could that have anything to do with it?
it could be the language and regional settings on the work station are not correct
ASKER
The mail server is now "magically" letting me sign on with a network account.
Removing/adding the workstations from teh domain seems to temporarily fix the problem, but I don't think the problem is going to go away...
Removing/adding the workstations from teh domain seems to temporarily fix the problem, but I don't think the problem is going to go away...
Are you in a AD environment? I remember somebody telling me flaky things will start happening if your DC's have more that a 5 minute difference in their times and that member servers will start having issues if their time is more that 5 minutes off from the DC's.
Did you apply both the Windows and the Exchange patches?
Regional settings should not matter as Windows does not use local time, but GMT time, that is how you can have DC's and member server in different timezones.
Did you apply both the Windows and the Exchange patches?
Regional settings should not matter as Windows does not use local time, but GMT time, that is how you can have DC's and member server in different timezones.
ASKER
Okay, this has to be related to the Daylight Savings issue. Our domain controller is now an hour off. If I go in and manually change it's time an hour forward...it takes for about 10 minutes. Then it automatically reverts back an hour.
Again, this Win 2000 Server Domain Controller has all relevant updates.
Again, this Win 2000 Server Domain Controller has all relevant updates.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well then apparently our DC didn't get the patch. Here are the results:
Current Timezone is :
Daylight Saving Time begins at 02:0:5:1
Daylight Saving Time ends at 02:0:5:10
I'm trying to manually download the patch for Win2K server, but can't find it online. Does anyone have a link? Thanks in advance.
Current Timezone is :
Daylight Saving Time begins at 02:0:5:1
Daylight Saving Time ends at 02:0:5:10
I'm trying to manually download the patch for Win2K server, but can't find it online. Does anyone have a link? Thanks in advance.
ASKER
Okay, I *think* I've figured it out. I had to manually update it via this procedure:
http://support.microsoft.com/kb/914387/
As of right now, it looks like it worked..but we'll wait and see I guess.
http://support.microsoft.com/kb/914387/
As of right now, it looks like it worked..but we'll wait and see I guess.
I had to download the fix for one of the PC's that was missed by our PC support staff. What I had to do is change the time to march 3 01:59:55, allow it to get change over to 02:00:00 and then it went forward to 03:00:00, then change the time to the real time. Now this was on a XP desktop. Tomorrow I have to do it on an W2K server that was missed, but is not critical.
ASKER