Error 1398

tfranzen

Hi,

does anybody heard of error 1398 occurring when using Windows authentication with native server?? (ERROR_TIME_SKEW: There is a time and/or date difference between the client and server) With database authentication everything works fine.


Thomas

P.S. Solution for customer: adjusting the time on client and server

Malajlo

Is your client in domain? (it should be...)
Then check, what is the time on server and client.
Use in shell:

net time \\domaincontroller
net time /setsntp:domaincontroller

on SQL server and client(s).
Time server should be domain controler by default, but sometimes people think that using third party time progs is better...

Slawek_Guzek

Hi,

Windows authentication rely on Kerberos service and ticket exchanging. Kerberos service requires the server and the client computer clocks has to be in sync with tolerance set on Gropu Policy Editor in section:

Computer Configuration->Windows Settings-> Security Settings Account Policies -> Kerberos Policy

Policy name: Maximum tolerance for computer clock synchronization.


When policy not defined it defaults to 10 min.

Proposed solution to adjust computer clock is 100% correct .

Regards,
Slawek

tooo

Slawek Guzek wrote:

Hi,

Windows authentication rely on Kerberos service and ticket exchanging. Kerberos service requires the server and the client computer clocks has to be in sync with tolerance set on Gropu Policy Editor in section:

Computer Configuration->Windows Settings-> Security Settings Account Policies -> Kerberos Policy

Policy name: Maximum tolerance for computer clock synchronization.


When policy not defined it defaults to 10 min.

Proposed solution to adjust computer clock is 100% correct .

Regards,
Slawek

Can someone point me in the direction of the highlighted directory menu?
EDIT: Found it.