Year 2142 problem...

[Jeremy Thomas Hunt]

I repeat my question, ... is the server's date set to 2142 as well?

If the server and the client's times are out by more than the "specified 
maximum clock skew of the KDC", which by default is 5 minutes, then you 
will not be able to get a Kerberos ticket.

See 
http://web.mit.edu/kerberos/www/krb5-1.4/krb5-1.4.3/doc/krb5-admin/Clock-Skew.html 
for more details.

Jeremy Thomas Hunt wrote:
> [safeTgram (optim1) receive status: NOT encrypted, NOT signed.]
>
>
> David A. Resler wrote:
>   
>> Over the past couple of weeks we have been seeing a handful of users 
>> not be able to get a Kerberos ticket because the date on their 
>> computer has been set to the year 2142.
>>
>> Once the date is corrected, they can get tickets without any further 
>> problems.
>>
>> So far we have been unable to find anything in common between these 
>> machines.  We have searched for viruses and not found any.
>>
>> Anyone have any ideas???
>>     
> Is the date on the server set to 2142 as well?
>   
>> /David Resler
>> Ohio University
>> ------------------------------------------------------------------------
>>
>> [safeTgram (optim1) receive status: NOT encrypted, NOT signed.]
>>
>>
>> ________________________________________________
>> Kerberos mailing list           Kerberos at mit.edu
>> https://mailman.mit.edu/mailman/listinfo/kerberos
>>   
>>     
>
> ________________________________________________
> Kerberos mailing list           Kerberos at mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos
>
>
>
>