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:
    1396
    Full Description:
    Logon Failure: The target account name is incorrect.
    There is Microsoft Knowledge Base article available. Please see http://support.microsoft.com/default.aspx?scid=kb;en-us;296993 for further details.
    Parameter Description:
    Logon Failure: The target account name is incorrect.
    More Informations:
    Symptoms
    • When using net use, you may receive above message.
    • When using net view \\hostname, you may receive "System error 5 has occurred. Access is denied.". However, net view \\ip works fine.
    • You may receive above error while running logon script.
    Causes
    • SPN for the domain that is hosting the replica has not been propagated.
    • Incorrect target account name or the server is not online.
    • If you have DFS, make sure the DFSRoot is available
    Search for this Event::
    Search in Knowledge Base  •  Search in this Forum  •  Search on Windows-Expert.com
  • Software Vendor: Microsoft
    Accessed: 21353

Discuss the Event

Discussion for KB Entry 1788 - Event ID 1396

by knowledgebase on Thu May 29, 2008 9:13 pm

This is the discussion thread for the Knowledge Base Entry 1788

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

Short Description:
Logon Failure: The target account name is incorrect.
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