Results 1 to 5 of 5

Thread: Pre-Authentication Failure

  1. #1
    Join Date
    Feb 2006

    Pre-Authentication Failure

    I am using a new Exchange 2007 server on 2008 and I am seeing the below errors every now andthen on my Server 2003 DC. There isnt a problem that it says, but every minutes it looks like an issue:

    Event Type: Failure Audit
    Event Source: Security
    Event Category: Account Logon
    Event ID: 675
    Date: 7/6/2008
    Time: 10:16:06 PM
    Computer: FILESERVER
    Pre-authentication failed:
    User Name: EXC$
    User ID: DOMAIN\EXC$
    Service Name: krbtgt/DOMAIN.LOCAL
    Pre-Authentication Type: 0x0
    Failure Code: 0x19
    Client Address:

    For more information, see Help and Support Center at

  2. #2
    Join Date
    Oct 2005

    RE: Pre-Authentication Failure

    The problem that you are facing can occur because the Key Distribution Center Service returns the wrong user name format to the router. A supported hotfix is available from Microsoft. Download it from here -;EN-US;829074

  3. #3
    Join Date
    Oct 2005

    RE: Pre-Authentication Failure

    Have you took the chance to try the troubleshooting steps? And did it solve the issue for you, incase you have any other quetions, the you can surely post it here and we will let you know about a proper solution for it.

  4. #4
    Join Date
    Jan 2006

    Re: Pre-Authentication Failure

    Can you try to insert the below command from any device that you are trying to connect and check if any error is occuring on your machine. You will need to also run eventcombmt.exe and check from what device you are getting the problem:


    /SC_VERIFY:<DomainName> - Verify secure channel for <Domain> on <ServerName>

  5. #5
    Join Date
    Nov 2009

    Re: Pre-Authentication Failure

    This error was something that I was also getting. The source client was on a Windows 7 pc running Symantec Backup Exec System Recovery (BESR). I had been using a Usb hard drive long back that was connected to a Windows XP computer in the network and this BESR was trying to ping this non-existent drive at regular intervals time which was resulting in the errors. After removing the location from BESR the problem got fixed.

Similar Threads

  1. IAS use authentication failure (Reason code=16)
    By abeh555 in forum Windows Server Help
    Replies: 3
    Last Post: 09-01-2014, 10:04 AM
  2. Replies: 2
    Last Post: 16-03-2012, 02:16 PM
  3. Authentication failure in MTNL broadband
    By Victorious in forum India BroadBand
    Replies: 4
    Last Post: 25-01-2011, 07:48 AM
  4. Replies: 4
    Last Post: 09-02-2010, 09:00 PM
  5. AD 2003 Replication Failure/Authentication Failure
    By Nickason in forum Active Directory
    Replies: 1
    Last Post: 20-05-2005, 03:54 AM


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Page generated in 1,675,337,954.05529 seconds with 18 queries