Pre-Authentication Failed - Type 0x0 - Code 0x19 - Event ID 675

[Jemond]

Since turning on full auditing of systems in my domain i am getting Event ID 675,Event ID: 672 and Event ID: 673 on my DC's. I have gone through them and have found most of the event's of type 0x2 with code 0x18 and saying "Pre-authentication failed". Which by theory points to "wrong username or password".
I want to know what might be going wrong in my system and why i am getting that Pre-authentication failed error ???

[dotnetontwikkelaars]

These pre-authentication failed is sometimes caused by the wrong time at the client. We deliver .NET applications to track these stuff

[Candace]

If you want to solve the 675 error that you are getting then you can try to force your operating system to use previous authentication steps. To do that you need to create the below registry value on your operating system:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
Name: DefaultEncryptionType
Type: REG_DWORD
Value: 23 (dec) or 0x17 (hex)

After that restart your computer to take effect.

[Sabastiaan]

I was also having this similar kind of problem with a 2012 domain member and 2003 domain controllers. When I changed the registry entry then it stopped my account from being locked out. If you want then you can also try to add AES support to server 2003 and it will let the 2003 DC to handle the original AES request, check this link for more information - http://support.microsoft.com/kb/948963.