KnowledgeBase Event Repository

This site is the central interface to the Adiscon Event Repository

  • Details for this entry
  • Eventlog Type:
    Security
    Eventlog Source:
    Security
    Event ID:
    676
    Full Description:
    Authentication Ticked Request Failed
    This is an error by the Kerberos authentication system. The "Failure Code" parameter (see below) is the original Kerberos failure code - click here to look it up.
    Parameter Description:
    Authentication Ticket Request Failed:%n
    %tUser Name:%t%1%n
    %tSupplied Realm Name:%t%2%n
    %tService Name:%t%3%n
    %tTicket Options:%t%4%n
    %tFailure Code:%t%5%n
    %tClient Address:%t%6%n
    Sample Data:
    Authentication Ticket Request Failed:
    User Name: WSNAME$
    Supplied Realm Name: INTER.ADISCON.COM
    Service Name: krbtgt/INTER.ADISCON.COM
    Ticket Options: 0x40810010
    Failure Code: 0x6
    Client Address: 10.19.1.21
    More Informations:

    Sometimes a logon fails not because of a bad password but because the user mistyped the username or tried to guess someone elses username. If a logon fails because of an invalid username, Windows 2000 logs event ID 676 (authentication ticket request fail

    Search for this Event::
    Search in Knowledge Base  •  Search in this Forum  •  Search on Windows-Expert.com
  • Software Vendor: Microsoft
    Accessed: 9135

Discuss the Event

Discussion for KB Entry 21 - Event ID 676

by knowledgebase on Thu May 29, 2008 2:57 pm

This is the discussion thread for the Knowledge Base Entry 21

Eventlog Type: Security
Eventlog Source: Security
Event ID: 676
Link to KB Entry

Short Description:
Authentication Ticked Request Failed
User avatar
knowledgebase
Frequent Poster
 
Posts: 128
Joined: Wed May 28, 2008 10:09 am


About the KnowledgeBase Event Repository

This is a repository of known Windows Events, hopefully together with a description of what it means, when it appears and how to troubleshoot it. The event repository was initially provided as a tool for parser creation but has since evolved. It is now part of the overall knowledgebase in the hope that it provides a useful service to the community. Please add your comments and questions (which we try to answer), as this increases the event repository usefulness for all of us.

Return to

cron