This error might be caused by one of the following conditions:
• | There is a network connectivity problem between the terminal server and the TS Session Broker server. |
• | There is an issue with DNS. |
• | The Terminal Services Session Broker service is not running on the TS Session Broker server. |
• | An incorrect name or IP address is listed for the TS Session Broker server. |
Note: This condition might only indicate a temporary communication issue. Therefore, first try to reconnect to an existing session. If you are able to reconnect to the existing session, the terminal server is successfully communicating with the TS Session Broker server, and the temporary communication issues have been resolved. If you are unable to reconnect, refer to the following sections to determine the root cause of the problem.
There is a network connectivity problem between the terminal server and the TS Session Broker server
Note: The following procedure includes steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To determine if there is a network connectivity problem between the terminal server and the TS Session Broker server:
• | On the terminal server, click Start, click Run, type cmd, and then click OK. |
• | At the command prompt, type ping IP_address, where IP_address is the IP address of the TS Session Broker server, and then press ENTER. |
If the ping was successful, you will receive a reply similar to the following:
Reply from IP_address: bytes=32 time=3ms TTL=59
Reply from IP_address: bytes=32 time=20ms TTL=59
Reply from IP_address: bytes=32 time=3ms TTL=59
Reply from IP_address: bytes=32 time=6ms TTL=59
If you cannot successfully ping the TS Session Broker server by IP address, see the section below titled "Identify and fix network connectivity issues."
There is an issue with DNS
Note: The following procedure includes steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To determine if there is a DNS issue:
• | On the terminal server, click Start, click Run, type cmd, and then click OK. |
• | At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name of the TS Session Broker server (for example, server1.contoso.com), and then press ENTER. |
If the ping was successful, you will receive a reply similar to the following:
Reply from IP_address: bytes=32 time=3ms TTL=59
Reply from IP_address: bytes=32 time=20ms TTL=59
Reply from IP_address: bytes=32 time=3ms TTL=59
Reply from IP_address: bytes=32 time=6ms TTL=59
If you cannot successfully ping the TS Session Broker server by FQDN, see the section below titled "Identify and fix DNS issues."
The Terminal Services Session Broker service is not running on the TS Session Broker server
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To check if the Terminal Services Session Broker service is running:
• | On the TS Session Broker server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services. |
• | If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. |
• | In the Services pane, if the Status column for the Terminal Services Session Broker service does not display Started, see the section titled "Start the Terminal Services Session Broker service." |
An incorrect name or IP address is listed for the TS Session Broker server
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To determine if an incorrect name or IP address is listed for the TS Session Broker server:
• | On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration. |
• | If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. |
• | Under TS Session Broker, double-click Member of farm in TS Session Broker. |
• | On the TS Session Broker tab, under TS Session Broker server name or IP address, if the computer name or IP address listed is incorrect, see the section titled "Specify the correct name or IP address of the TS Session Broker server." |
Identify and fix network connectivity issuesTo resolve this issue, identify and fix any network connectivity problems between the terminal server and the TS Session Broker server.
Note: The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
If you cannot successfully ping the TS Session Broker server by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.
The following are some additional troubleshooting steps that you can perform to help identify the root cause of the problem:
• | Ping other computers on the network to help determine the extent of the network connectivity issue. |
• | If you can ping other servers but not the TS Session Broker server, try to ping the TS Session Broker server from another computer. If you cannot ping the TS Session Broker server from any computer, first ensure that the TS Session Broker server is running. If the TS Session Broker server is running, check the network settings on the TS Session Broker server. |
• | Check the TCP/IP settings on the local computer by doing the following: |
• | Click Start, click Run, type cmd, and then click OK. |
• | At the command prompt, type ipconfig /all, and then press ENTER. Make sure that the information listed is correct. |
• | Type ping localhost to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with your network adapter. |
• | Type ping IP_address, where IP_address is the IP address assigned to the computer. If you can ping the localhost address but not the local address, there may be an issue with the routing table or with the network adapter driver. |
• | Type ping DNS_server, where DNS_server is the IP address assigned to the DNS server. If there is more than one DNS server on your network, you should ping each one. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or with the network between the computer and the DNS servers. |
• | If the TS Session Broker server is on a different subnet, try to ping the default gateway. If you cannot ping the default gateway, this might indicate a problem with the network adapter, the router or gateway device, cabling, or other connectivity hardware. |
• | In Device Manager, check the status of the network adapter. To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK. |
• | Check network connectivity indicator lights on the computer and at the hub or router. Check network cabling. |
• | Check firewall settings by using the Windows Firewall with Advanced Security snap-in. |
• | Check IPsec settings by using the IP Security Policy Management snap-in. |
Identify and fix DNS issuesTo resolve this issue, identify and fix any issues related to DNS.
Note: If you cannot ping the TS Session Broker server by FQDN, this indicates a DNS issue.
To determine whether DNS servers are configured and accessible:
• | On the terminal server, click Start, click Run, type cmd, and then click OK. |
• | At the command prompt, type ipconfig /all, and then press ENTER. |
• | In the results, make sure that DNS servers are listed, and that the IP addresses of the DNS servers are correct. |
• | Ping the listed DNS servers to determine whether they are accessible. |
• | If you cannot ping the DNS server, ensure that the DNS server is running. You can also test connectivity from other computers in your network to help isolate the issue. If the DNS server responds to IP address ping requests but does not resolve host names, make sure that the DNS Server service is running on the DNS server. |
For general information about identifying and resolving DNS issues for Windows Server 2008, see DNS Troubleshooting. For general information about troubleshooting DNS in Window Server 2003, see Troubleshooting DNS on the Microsoft Web site.
| Target | Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer | ||
| Category | Custom | ||
| Enabled | True | ||
| Event_ID | 1003 | ||
| Event Source | Microsoft-Windows-TerminalServices-SessionBroker-Client | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Remotable | True | ||
| Alert Message |
| ||
| Event Log | System |
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| DS | DataSource | Microsoft.Windows.EventProvider | Default |
| Alert | WriteAction | System.Health.GenerateAlert | Default |
Home
ENU <Rule ID="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer.EventCollection.TSSessionBrokerClient1003" Enabled="onStandardMonitoring" Target="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Custom</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">1003</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Microsoft-Windows-TerminalServices-SessionBroker-Client</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertName/>
<AlertDescription/>
<AlertOwner/>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer.EventCollection.TSSessionBrokerClient1003.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/LoggingComputer$</SuppressionValue>
</Suppression>
<Custom1/>
<Custom2/>
<Custom3/>
<Custom4/>
<Custom5/>
<Custom6/>
<Custom7/>
<Custom8/>
<Custom9/>
<Custom10/>
</WriteAction>
</WriteActions>
</Rule>