We're getting these random errors on our ADFS security logs, how can I track down what is generating them?
An account failed to log on.
Subject:
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:
Account Domain:
Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xC000035B
Sub Status: 0x0
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: -
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Kerberos
Authentication Package: Kerberos
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.
Note the last part is showing a command for ADFS in Windows Server 2012 R2.
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Marked as answer byStryker801Tuesday, January 3, 2017 9:41 PM
The default on Windows 7 & 8 is to not have any value set for this setting, though this particular user's PC it was set to "Send LM and NTLM - use NTLMv2 session security if negotiated "; it needs to be set to “Send NTLMV2 response only”. Once
this was done the Windows 8.1 PC was able to open RemoteApp applications without problems.
You can check in the group policy and change the setting accordingly.
Proposed as answer byLiinusMonday, January 2, 2017 10:12 AM
Note the last part is showing a command for ADFS in Windows Server 2012 R2.
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Marked as answer byStryker801Tuesday, January 3, 2017 9:41 PM
Hi Jorrk, sorry for the late reply, I been off for the holidays.
Yes we do see successful logins, but sometimes the failure will occur 2-4 times in a row but then we see successes, but I'm unsure if it's coming from the same user/process.
Thanks for the reply, I saw an article relating to this, but we're not getting any user complaints about being unable to access any apps, our ADFS is only used for O365 and an internal at the moment.
Appreciate the reply, I did a Get-AdfsProperties and it looks like ours is set to "Allow", what does this do by turning this off? Are there any drawbacks?
Disabling the CBT? Well, more vulnerable to Man in the Middle attacks.
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
