06-03-2009, 10:48 AM

In the last couple of days I've had a few of my machines start being weird about their authentication. They are part of an AD domain and have been working fine for a long time.

I haven't had time to sit down and time the issue, but at some point after inactivity (screensaver, machine locked), my password will no longer work. Once my password will no longer let me back in, putting the machine to sleep and then waking back up will allow me to log in again (I originally assumed something wrong with my connection to the domain controller, but I'm not sure anymore).

With another users machine it is basically the same problem. At some point he is no longer able to use his password to authenticate, such as installing and app. Logging out and trying to log back in does not work, including with the local admin account. Again, putting to sleep and waking back up seem to resolve it temporarily, but I am very curious why this started to happen and if anyone has any suggestions as to a resolution. Thanks in advance for any help.

06-04-2009, 04:42 PM

FWIW, I found that my domain controller (win2k3) was not time-syncing properly.

I found this in /var/log/secure.log from every time I was having authentication issues:
authorizationhost[348]: k5_authenticate(): got -1765328347 (Clock skew too great) on plugins/krb5/krb5_operations.c:54


Still very bizarre that putting it to sleep and waking it back up allows me to login.