audit failure 4625

Getting this for almost all my users on my exchange 2010 box along with a terminal services server and a team foundation server. It just started today after rebooting domain controllers last night, one domain controller didn't come up right away due to an F1 prompt but was brought up about 2 hours later.
All my exchange users are getting the prompt for their username/password but email is still working.
I'm under a lot of pressure to get this resolved and can't find the resolution.

An account failed to log on.

      Security ID:            NULL SID
      Account Name:            -
      Account Domain:            -
      Logon ID:            0x0

Logon Type:                  3

Account For Which Logon Failed:
      Security ID:            NULL SID
      Account Name:            my.usersname
      Account Domain:            removed

Failure Information:
      Failure Reason:            An Error occured during Logon.
      Status:                  0xc000006d
      Sub Status:            0x0

Process Information:
      Caller Process ID:      0x0
      Caller Process Name:      -

Network Information:
      Workstation Name:      removed
      Source Network Address:      x.x.x.x
      Source Port:            58327

Detailed Authentication Information:
      Logon Process:            NtLmSsp
      Authentication Package:      NTLM
      Transited Services:      -
      Package Name (NTLM only):      -
      Key Length:            0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
      - Transited services indicate which intermediate services have participated in this logon request.
      - Package name indicates which sub-protocol was used among the NTLM protocols.
      - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
I would be checking to make sure that replication and everything is properly working between the DC's. Use the below commands to check health and replication.

repadmin /replsum
repadmin /showrepl
dcdiag /v
netdom query fsmo
netdom query dc

Also ensure that the NetLogon Service has been started as well, on all DC's.

pcphenom2Author Commented:
Ran all of the above commands. Looks good I think. Also the DCdiag results were perfect, all tests passed.

Replication Summary Start Time: 2015-03-13 13:36:50

Beginning data collection for replication summary, this may t

Source DC           largest delta  fails/total  %%  error
 AOG-DC01                  44m:31s    0 /   5    0
 AOG-DC02                  49m:37s    0 /   5    0

Destination DC    largest delta    fails/total  %%  error
 AOG-DC01                  49m:37s    0 /   5    0
 AOG-DC02                  44m:31s    0 /   5    0

C:\Documents and Settings\>repadmin /showrepl

repadmin running command /showrepl against server localhost

DC Options: IS_GC
Site Options: (none)
DC object GUID: a089abae-0668-494d-a894-050b71fb94ac
DC invocationID: a089abae-0668-494d-a894-050b71fb94ac

==== INBOUND NEIGHBORS ======================================

    Default-First-Site\AOG-DC02 via RPC
        DC object GUID: 7944589e-0a41-45de-a781-883f9a7fc55f
        Last attempt @ 2015-03-13 13:36:32 was successful.

    Default-First-Site\AOG-DC02 via RPC
        DC object GUID: 7944589e-0a41-45de-a781-883f9a7fc55f
        Last attempt @ 2015-03-13 12:47:13 was successful.

    Default-First-Site\AOG-DC02 via RPC
        DC object GUID: 7944589e-0a41-45de-a781-883f9a7fc55f
        Last attempt @ 2015-03-13 12:47:13 was successful.

    Default-First-Site\AOG-DC02 via RPC
        DC object GUID: 7944589e-0a41-45de-a781-883f9a7fc55f
        Last attempt @ 2015-03-13 13:20:28 was successful.

    Default-First-Site\AOG-DC02 via RPC
        DC object GUID: 7944589e-0a41-45de-a781-883f9a7fc55f
        Last attempt @ 2015-03-13 13:23:46 was successful.

C:\Documents and Settings\>netdom query fsmo
Schema owner                aog-dc01.aog.local

Domain role owner           aog-dc01.aog.local

PDC role                    aog-dc01.aog.local

RID pool manager            aog-dc01.aog.local

Infrastructure owner        aog-dc01.aog.local

The command completed successfully.
Will SzymkowskiSenior Solution ArchitectCommented:
Ok that is good that DC's check out. However, have you been able to restart the Exchange services on the server? or even restart the Netlogon service on the terminal server?

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

pcphenom2Author Commented:
I have not restarted the Exchange services as email seems to still be working. I did restart the team foundation server that was exhibiting the same problems and the issue remains on it. As soon as I can I will be restarting Exchange.
I will restart the terminal server now and report back.
pcphenom2Author Commented:
I restarted the terminal server. Still a problem.
I and another user can remote desktop to it, but another user can't.
The user who can't gets the exact error message I originally posted with NTLM as the authentication package.
The user who can log in has Kerberos as the authentication package and logon process.
Not sure if that is remarkable.
Also restarted the TFS server, no change. Users prompted for creds and audit failure logged.
pcphenom2Author Commented:
I'm still dead in the water with this issue.
Will SzymkowskiSenior Solution ArchitectCommented:
So what is happening on the client end exactly? They cannot logon to anything on the network? What are the event ids you are getting on the domain controllers. Have you attempted to reboot the DC's again?

pcphenom2Author Commented:
I did have a chance to reboot the DC's about an hour ago.
For the Exchange/Outlook issue. The end user gets prompted for their credentials, this wasn't happening before. Outlook seems to be able to get and send email if the prompt is cancelled but it pops back up later.
At that same time a failure audit is logged for that user on the exchange server.
Similar thing with the TFS server, users try to open their Visual Studio and are prompted for credentials, not normal. Again a failure audit is logged.
As for the DC's, there are no event ID's for failure audits and I can see the exchange server machine with successful audits in the DC's security log.
pcphenom2Author Commented:
I'm leaning in the direction of IIS authentication methods? Basic/Windows, etc. Kernel mode authentication?
Are there defaults for these settings in Exchange 2010? Peoples phones can authenticate and get mail via IMAP/SMTP and OWA works fine for everyone. What is it about the Outlook client that is triggering this?
Thanks again for the help.
pcphenom2Author Commented:
Been working on this most of the day today.
Working with just one user account and watching the security logs on the Exchange server.
When I launch Outlook I see two security log types for the user, audit failures for NTLM and audit success' for Kerberos. The DC's don't show any audit failures and I see the same user in the audit log at the same timestamp kerberos.
Again mail comes and goes in the Outlook client just fine but the authentication prompt keeps coming up.
pcphenom2Author Commented:
I have resolved the issue.
Removal of update 3002657 from this last patch Tuesday.
Removed from my DC's, Exchange Server, Terminal Server and TFS server.
All is back to normal.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pcphenom2Author Commented:
Worked with Microsoft on the phone who told me there were issue's with this particular update from the last patch Tuesday.
Microsoft case #115031612519646
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.