Hello.
Server 2008 R2 SP1, all updates
RDweb, RD Gateway Roles installed
Server has two network adapters: LAN (local IP) and WAN (DMZ IP)
Installing TMG 2010 with all updates (ver 7.0.9193.500) as Back Firewall
TMG has rule in Firewall Policy "Allow from Internal\Localhost\Perimeter to Internal\Localhost\Perimeter any"
I configure RD Web Access to provide users access to RemoteApp and Desktop Connection: go to RDweb site, Configuration tab, enter RD Session Host server name (FQDN).
After pressing "OK" i see error message:
"RD Web Access was not able to access server3.domain.local. Verify that the RD Session Host server name was entered correctly, that the server is running and connected to the network, and then try again."
In System log i see event 10009
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 12/6/2012 9:44:26 AM
Event ID: 10009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WWW.domain.local
Description:
DCOM was unable to communicate with the computer server3.domain.local using any of the configured protocols.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="49152">10009</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-12-06T05:44:26.000000000Z" />
<EventRecordID>8921</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>WWW.domain.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">server3.domain.local</Data>
<Binary>3C5265636F726423313A20436F6D70757465723D286E756C6C293B5069643D3732343B31322F362F3230313220353A34343A32363A3531333B5374617475733D313732323B47656E636F6D703D323B4465746C6F633D313731303B466C6167733D303B506172616D733D313B7B506172616D23303A307D3E3C5265636F726423323A20436F6D70757465723D286E756C6C293B5069643D3732343B31322F362F3230313220353A34343A32363A3531333B5374617475733D313732323B47656E636F6D703D31383B4465746C6F633D313434323B466C6167733D303B506172616D733D313B7B506172616D23303A736572766572332E636C69656E74732E736D6F66662E72757D3E3C5265636F726423333A20436F6D70757465723D286E756C6C293B5069643D3732343B31322F362F3230313220353A34343A32363A3531333B5374617475733D313732323B47656E636F6D703D31383B4465746C6F633D3332333B466C6167733D303B506172616D733D303B3E3C5265636F726423343A20436F6D70757465723D286E756C6C293B5069643D3732343B31322F362F3230313220353A34343A32363A3531333B5374617475733D313233373B47656E636F6D703D31383B4465746C6F633D3331333B466C6167733D303B506172616D733D303B3E3C5265636F726423353A20436F6D70757465723D286E756C6C293B5069643D3732343B31322F362F3230313220353A34343A32363A3531333B5374617475733D31303036303B47656E636F6D703D31383B4465746C6F633D3331313B466C6167733D303B506172616D733D333B7B506172616D23303A3133357D7B506172616D23313A307D7B506172616D23323A3078376131343030306130303030303030307D3E3C5265636F726423363A20436F6D70757465723D286E756C6C293B5069643D3732343B31322F362F3230313220353A34343A32363A3531333B5374617475733D31303036303B47656E636F6D703D31383B4465746C6F633D3331383B466C6167733D303B506172616D733D303B3E</Binary>
</EventData>
</Event>
At the RD Session Host server i see two events in Security log:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 06.12.2012 9:53:26
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: Server3.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: WWW$
Account Domain: DOMAIN
Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xc00002ee
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.
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-12-06T05:53:26.074824300Z" />
<EventRecordID>54591</EventRecordID>
<Correlation />
<Execution ProcessID="540" ThreadID="1104" />
<Channel>Security</Channel>
<Computer>Server3.domain.local</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">WWW$</Data>
<Data Name="TargetDomainName">DOMAIN</Data>
<Data Name="Status">0xc00002ee</Data>
<Data Name="FailureReason">%%2304</Data>
<Data Name="SubStatus">0x0</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">Kerberos</Data>
<Data Name="AuthenticationPackageName">Kerberos</Data>
<Data Name="WorkstationName">-</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>
AND
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 06.12.2012 9:53:26
Event ID: 4634
Task Category: Logoff
Level: Information
Keywords: Audit Success
User: N/A
Computer: Server3.domain.local
Description:
An account was logged off.
Subject:
Security ID: DOMAIN\WWW$
Account Name: WWW$
Account Domain: DOMAIN
Logon ID: 0x325a4cf
Logon Type: 3
This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer.
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>4634</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12545</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2012-12-06T05:53:26.074824300Z" />
<EventRecordID>54592</EventRecordID>
<Correlation />
<Execution ProcessID="540" ThreadID="1104" />
<Channel>Security</Channel>
<Computer>Server3.domain.local</Computer>
<Security />
</System>
<EventData>
<Data Name="TargetUserSid">S-1-5-21-3882217896-3255031834-2471755480-1945</Data>
<Data Name="TargetUserName">WWW$</Data>
<Data Name="TargetDomainName">DOMAIN</Data>
<Data Name="TargetLogonId">0x325a4cf</Data>
<Data Name="LogonType">3</Data>
</EventData>
</Event>
Help, please!