Windows Forum

Ask something
Discussion Locked

Time Difference between Client & Server

0 helpful
5 replies

by paul.parkin

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Issue:

On a Windows 2000 Pro Workstation (SP2), when the user tries to Logon the login fails with the following error message:

"There is a Time Difference between the Client and Server contact your Administrator "

This is a complete lock out situation.

The time, when checked against the Win 2000 Domain DC/Time Server/Global catalogue holder is accurate to within 2 seconds.

Even allowing for permitted time skew, the Bios is only 2 miliseconds out!

I have had this problem before, and eventually had to delete/re-create the user account. I dont see this proccess as being an acceptable solution, but even Microsoft cannot provide me with a more satisfactory option.

The user can login to any Win2000 Workstation and still getsthe same denial of service message.

He logged in to a windows NT Server on the network, no problems. I am sure that the problem here is a mixture of user login rights, Kerberos Security problems and/or active directory/DC security/logon information.

If anyone has had this problem, or have a known solution to my quandry, please reply to this question.

I am formulating a Technical Investigation request for Microsoft Support based on the outcome of ths posting.

At the moment, I am aware of over 233 individual Administrators/users/technicians who have ALL come accross a similar problem, and lack of resolution from Microsoft Support/Technet.

To all those who may reply,

Thank You.

5 replies

by parbo

Paul there is an tchnet article on this:
Cannot Log On If Time and Date Are Not Synchronized [Q232386]

Hope this solution helps....

by shanghai sam

Thanks for the swift reply,

Sorry....but...

Tried this one, as have so many others before me. Looks like it might work, but fails miserably.

It would seem that it affects the user account, and NOT the local computer as when logging on to any other workstation the user still recieves the same message.

by sergey kovzik

problem isn't with user account but with computer itself. you can try to login with same account from different computers. have you had situation when one account was logged in but other - not, and all this on same PC? during kerberos authenticationcomputer sends answer with local time. if it different - you'll have this message. have you tried "NET TIME /DOMAIN:name /SET"? Even if clock looks exactly it's better to use windows tool to let it know what you need domain name, not local one.
well, if nothing helps you can disable kerberos type of authentication...

This discussion is closed to new replies.