Hi everyone I have a Windows Server 2008 R2 serving 10-12 users mostly on thin clients. There is one particular client that has problems logging in pretty regularly. They enter their password over and over again, but it does not allow them to log in. Then, after some time passes, it just starts working, even though I have taken no action to correct the problem. They have tried changing the keyboard to remove any sticky keys problem. Also, there are 3 total thin clients that use the same AD account to log in, and I have no reports of problems on the other clients.
Is it OK to use the same AD account for multiple clients? I know there are some issues surrounding sharing an environment, but it should not prevent login correct?
The event below is logged every time there is a login failure. 16 times today.
Thank much in advance for any suggestions!
Event Type: Failure Audit
Event Source: Microsoft-Windows-Security-Auditing
Event Category: (12544)
Event ID: 4625
Date: 1/28/2014
Time: 8:29:33 AM
User: N/A
Computer: ts1.clientdomain.com
Description:
An account failed to log on.
Subject:
Security ID: S-1-0-0
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: S-1-0-0
Account Name: OfficeStaff408R1
Account Domain: CLIENTDOMAIN
Failure Information:
Failure Reason: %%2313
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name:
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.
For more information, see Help and Support Center at http://www.eventid.net/eventviewer.asp.