Windows 2003 kerberos error codes

  • Thread starter Thread starter rocketz21
  • Start date Start date
R

rocketz21

I've been receiving some kerberos error codes in the event viewer and any
help to fix them would be appreciated.

They are either under Event ID 675 or 673 (I don't know the difference) and
the code is 0x25 which is relation to clock skew or the workstation clock
being too far off from the DC and 0x20 which is a time out ticket request.
Also see 0x1B and a few others.

Is there a way I can fix this?
 
On Jul 13, 11:02 am, rocketz21 <rocket...@discussions.microsoft.com>
wrote:
> I've been receiving some kerberos error codes in the event viewer and any
> help to fix them would be appreciated.
>
> They are either under Event ID 675 or 673 (I don't know the difference) and
> the code is 0x25 which is relation to clock skew or the workstation clock
> being too far off from the DC and 0x20 which is a time out ticket request.
> Also see 0x1B and a few others.
>
> Is there a way I can fix this?

chances are that your clock issue is causing all of the other Kerberos
errors. By default your system clock needs to be within 5 minutes of
your authenticating DC or Kerberos authentication will fail. I'm not
sure which version of windows you are running, but have a look at the
following KB (a Win2k version is referenced in the References
section): http://support.microsoft.com/kb/816042
 
I was able to fix the clock problem, but I see some ticket time out requests
and I'm not sure what is causing that. I don't think those pcs are being
used or they are on an old domain but I would have to check.

"Debo" wrote:

> On Jul 13, 11:02 am, rocketz21 <rocket...@discussions.microsoft.com>
> wrote:
> > I've been receiving some kerberos error codes in the event viewer and any
> > help to fix them would be appreciated.
> >
> > They are either under Event ID 675 or 673 (I don't know the difference) and
> > the code is 0x25 which is relation to clock skew or the workstation clock
> > being too far off from the DC and 0x20 which is a time out ticket request.
> > Also see 0x1B and a few others.
> >
> > Is there a way I can fix this?
>
> chances are that your clock issue is causing all of the other Kerberos
> errors. By default your system clock needs to be within 5 minutes of
> your authenticating DC or Kerberos authentication will fail. I'm not
> sure which version of windows you are running, but have a look at the
> following KB (a Win2k version is referenced in the References
> section): http://support.microsoft.com/kb/816042
>
>
 
Things to check:

1 TImezone on the server and clients
2. Clock on the server and clients
3. Server/clients' BIOS time/date


You might also want to try resetting the clock on the client machine and do
a manual sync with time.windows.com

If all fails, try www.eventid.net


--
Jabez Gan [MVP]
Microsoft MVP: Windows Server
http://www.blizhosting.com
MSBLOG: http://www.msblog.org

"rocketz21" <rocketz21@discussions.microsoft.com> wrote in message
news:5FFAA7CA-05E8-4DEC-B016-C0A810B389B1@microsoft.com...
> I've been receiving some kerberos error codes in the event viewer and any
> help to fix them would be appreciated.
>
> They are either under Event ID 675 or 673 (I don't know the difference)
> and
> the code is 0x25 which is relation to clock skew or the workstation clock
> being too far off from the DC and 0x20 which is a time out ticket request.
> Also see 0x1B and a few others.
>
> Is there a way I can fix this?
 
Back
Top