Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
A Kerberos Error Message was received: on logon session InitializeSecurityContext
Error Code: 20:1:38.0000 4/16/2004 (null) <error code>
Extended Error: <error>
Server Name: LDAP/DC-server.<domain>.COM
Target Name: LDAP/DC-Server.<domain>.COM@<domain>.COM
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is Kerberos?
- Error: 0x29 KRB_AP_ERR_MODIFIED - See ME938702.
See ME230476 for a description of common Kerberos related errors in Windows 2000.
- Error: 0x43, error name: KRB_ERR_RESPONSE_TOO_BIG - From a newsgroup post: "Try forcing Kerberos to use TCP as per ME244474".
From a newsgroup post: "Page 33 of the MIT Kerberos V5 Systems Administrator's Guide identifies the "KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN" 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".
Check the MIT Kerberos V5 Systems Administrator's Guide for information regarding your particular error code.
If in conjunction with this event, you have the message "network path not found" in the MMC for the WINS server, check if you have disabled the remote access registry service. If yes, set it to automatic. See ME287727 for more information.
|Private comment: Subscribers only. See example of private comment|
|Links: ME230476, ME244474, ME287727, ME938702, MIT Kerberos V5 System Administrator Guide|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated