Thin clients cannot login to Remote Desktop on Windows 2008 R2
Over the weekend I upgraded from SBS2003 to SBS2011. Everything seems to work great except for my remote users. We have several users that normally access a Win2008r2 terminal server with Wyse C10LE thin clients. This morning, the TS will not allow users to login from the thin clients. The clients connect to the server but the login fails and the TS logs error 4625. However, I can login from the thin clients as can another Admin. Also, users that launch RD from a Windows desktop have no problem logging in.
Here is the error generated on the TS:
Log Name: Security
Source: Microsoft-Windows-Security
Date: 3/16/2015 11:07:15 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: RDServer.domain.local
Description:
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
Account Domain: domain.local
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:
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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Se
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x80100000000000
<TimeCreated SystemTime="2015-03-16T18:
<EventRecordID>4528681</Ev
<Correlation />
<Execution ProcessID="604" ThreadID="816" />
<Channel>Security</Channel
<Computer>RDServer.domain.
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-
<Data Name="SubjectUserName">-</
<Data Name="SubjectDomainName">-
<Data Name="SubjectLogonId">0x0<
<Data Name="TargetUserSid">S-1-0
<Data Name="TargetUserName">tfau
<Data Name="TargetDomainName">do
<Data Name="Status">0xc000006d</
<Data Name="FailureReason">%%230
<Data Name="SubStatus">0x0</Data
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">Nt
<Data Name="AuthenticationPackag
<Data Name="WorkstationName">
</Data>
<Data Name="TransmittedServices"
<Data Name="LmPackageName">-</Da
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data
<Data Name="ProcessName">-</Data
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
</EventData>
</Event>
Here is the error generated on the TS:
Log Name: Security
Source: Microsoft-Windows-Security
Date: 3/16/2015 11:07:15 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: RDServer.domain.local
Description:
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
Account Domain: domain.local
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:
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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Se
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x80100000000000
<TimeCreated SystemTime="2015-03-16T18:
<EventRecordID>4528681</Ev
<Correlation />
<Execution ProcessID="604" ThreadID="816" />
<Channel>Security</Channel
<Computer>RDServer.domain.
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-
<Data Name="SubjectUserName">-</
<Data Name="SubjectDomainName">-
<Data Name="SubjectLogonId">0x0<
<Data Name="TargetUserSid">S-1-0
<Data Name="TargetUserName">tfau
<Data Name="TargetDomainName">do
<Data Name="Status">0xc000006d</
<Data Name="FailureReason">%%230
<Data Name="SubStatus">0x0</Data
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">Nt
<Data Name="AuthenticationPackag
<Data Name="WorkstationName">
</Data>
<Data Name="TransmittedServices"
<Data Name="LmPackageName">-</Da
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data
<Data Name="ProcessName">-</Data
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
</EventData>
</Event>
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
this just worked for me. I thought I was going Bat Squeeze crazy
http://support.microsoft.com/en-us/kb/2493594
http://support.microsoft.com/en-us/kb/2493594
ASKER