Kerberos Error

  • Thread starter Thread starter Colin Pyne
  • Start date Start date
C

Colin Pyne

I get the error message below in the system event log.
I've tryed looking it up on KB but I carnt find any think
on it. I would be very grateful for any help.

Colin


Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 594
Date: 09/10/2003
Time: 08:55:29
User: N/A
Computer: OXYGEN
Description:
A Kerberos Error Message was received:
on logon session InitializeSecurityContext
Client Time:
Server Time:
Error Code: 7:55:29.0000 10/9/2003 (null) 0x7
Extended Error: KDC_ERR_S_PRINCIPAL_UNKNOWN
Client Realm:
Client Name:
Server Realm: LANSYNUK
Server Name: krbtgt/LANSYNUK
Target Name: HOST/10.183.144.17@LANSYNUK
Error Text:
File:
Line:
Error Data is in record data.
 
Here is a cut 'n paste from eventid.net.

"Page 33 of the MIT Kerberos V5 Systems Administrator's Guide identifies
this ERROR CODE as "Client not found in Kerberos database". However, the
EXTENDED ERROR information identifies this error code as "Server not found
in Kerberos database". This might be expected if, for example, you have a
Windows 2000 Server from another Domain, with no trust relationship or
parent/child relationship, which has tried to utilize a transitive trust to
authenticate to the Windows 2000 DC where you received this error. It would
have tried to forward a TGT from cache, and obviously this ticket was not
generated by a Security Principal which the proposed authentication server
would recognize. This may also be as simple as a mistyped user name or
re-named Workstation/Server within your DC Domain".
 
Hey there,
You can set your service principle name using the
setspn.exe on the W2K resource kit tools.
pd
 
Back
Top