Windows 2008R2 login issues: Security ID: NULL SID

We having strange issues after this weekend patches:
When we try to RDP into servers unable to login.
If i disable loopback check in registry all starts working right.

creates this event below:
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: username@domain
Account Domain:
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: PC1
Source Network Address: -
Source Port: -

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.

I have a fix to disable loopback check, but wondering why all of the sudden it started happening.
Cant seem to find anything in the news relating to new patches.

Any suggestions?

Share this

Related Posts

There was an error in this gadget