Currently I am working on a data center intergration project where i am getting connected to each data center through a Jumphost, which has TCP 3389 openend to my Citrix desktop. The Jumphots are part of differnt domains respective of each data center. Now let me describe the problem I am facing here . When I use MSTC client from citirx desktop and try to connect to the jumphost with domain\username and correct password it takes some time in Securing connection screen and then it gives "YOUR CREDENTIALS DID NOT WORK" in the same scenario when I use a differnt RDP client known as WEBRDP( java applet ) it works fine with the same credentials. I could find successfull logon event when i use WEBRDP and failure event when use MSTC client.
Failure Event when use MSTSC ( Using correct password and user name )
--------------------------------------------------------------------------------------------------------
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 8/13/2012 3:49:22 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: rdp001.ams2.sf.priv
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: c5177662
Account Domain: SFDC
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: DEWDFM4331
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-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2012-08-13T19:49:22.270771200Z" />
<EventRecordID>19414</EventRecordID>
<Correlation />
<Execution ProcessID="484" ThreadID="1612" />
<Channel>Security</Channel>
<Computer>rdp001.ams2.sf.priv</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">c5177662</Data>
<Data Name="TargetDomainName">SFDC</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2313</Data>
<Data Name="SubStatus">0xc000006a</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">DEWDFM4331</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
</EventData>
</Event>
Success Event when using WEBRDP tool
----------------------------------------------------------
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 8/13/2012 3:48:11 PM
Event ID: 4648
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: rdp001.ams2.sf.priv
Description:
A logon was attempted using explicit credentials.
Subject:
Security ID: SYSTEM
Account Name: RDP001$
Account Domain: AMS2
Logon ID: 0x3e7
Logon GUID: {00000000-0000-0000-0000-000000000000}
Account Whose Credentials Were Used:
Account Name: C5177662
Account Domain: SFDC
Logon GUID: {00000000-0000-0000-0000-000000000000}
Target Server:
Target Server Name: localhost
Additional Information: localhost
Process Information:
Process ID: 0x4a40
Process Name: C:\Windows\System32\winlogon.exe
Network Information:
Network Address: 10.2.242.18
Port: 57059
This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4648</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2012-08-13T19:48:11.738766000Z" />
<EventRecordID>19402</EventRecordID>
<Correlation />
<Execution ProcessID="484" ThreadID="1612" />
<Channel>Security</Channel>
<Computer>rdp001.ams2.sf.priv</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">RDP001$</Data>
<Data Name="SubjectDomainName">AMS2</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TargetUserName">C5177662</Data>
<Data Name="TargetDomainName">SFDC</Data>
<Data Name="TargetLogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TargetServerName">localhost</Data>
<Data Name="TargetInfo">localhost</Data>
<Data Name="ProcessId">0x4a40</Data>
<Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data>
<Data Name="IpAddress">10.2.242.18</Data>
<Data Name="IpPort">57059</Data>
</EventData>
</Event>
----------------------------------------------
The only field which is changed here is Security ID which is NULL SID in failure event and it is system in the successfull event . The IP address of the jumphost is actually NATed in network, When we use WBRDP TCP3389 connection is establishing properly. In one of the data center i configured a stand alone Win 2k8 R2 and it is able to connect with MSTSC client. When I tried a Local user in the Jumphost which is part of a domain is giving same credential error. Could any one please help ?