Event ID 1019 — Terminal Server Communication

Updated: January 5, 2012

Applies To: Windows Server 2008

yellow

For the Terminal Services Session Broker (TS Session Broker) server to support session load balancing between terminal servers in a farm, and to reconnect users to existing sessions in a load-balanced terminal server farm, the TS Session Broker server must be able to communicate with the terminal server across the network.

Note:  TS Session Broker was formerly called Terminal Services Session Directory.

Event Details

Product: Windows Operating System
ID: 1019
Source: Microsoft-Windows-TerminalServices-SessionBroker
Version: 6.0
Symbolic Name: EVENT_FAIL_CALL_TS_REJOIN
Message: TS Session Broker failed to call terminal server %1 to rejoin.

Resolve

Check firewall settings, and if necessary, identify and fix network connectivity issues

To resolve this issue, check firewall settings to ensure that RPC communication is not blocked between the TS Session Broker server and the terminal server.  If the firewall settings are correctly configured or the problem persists, identify and fix network connectivity issues.

To perform these tasks, refer to the following sections.

Check firewall settings

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To check firewall settings:

  1. On the terminal server, click Start, and then click Control Panel.
  2. Click Security, click Windows Firewall, and then click Change Settings.
  3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  4. In the Windows Firewall Settings dialog box, click the Exceptions tab.
  5. Under Program or port, ensure that the Terminal Services check box is selected. If the Terminal Services check box is not selected, select it, and then click OK.
  6. On the TS Session Broker server, click Start, and then click Control Panel.
  7. Click Security, and then click Windows Firewall.
  8. Click Change Settings, and then, in the Windows Firewall Settings dialog box, click the Exceptions tab.
  9. Under Program or port, ensure that the Session Broker Service check box is selected. If the Session Broker Service check box is not selected, select it, and then click OK.

Note:  To view more detailed information about Windows Firewall settings, use the Windows Firewall with Advanced Security snap-in.

Identify and fix network connectivity issues

To identify and fix any network connectivity problems between the TS Session Broker server and the terminal server, do the following:

  • Determine if there is a network connectivity problem by using the ping command.
  • Perform additional troubleshooting steps, if necessary, to help identify the cause of the problem.

To perform these tasks, refer to the following sections.

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.

Determine if there is a network connectivity problem

To determine if there is a network connectivity problem between the TS Session Broker server and the terminal server:

  1. On the TS Session Broker server, click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name (FQDN) of the terminal 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

  3. At the command prompt, type ping IP_address, where IP_address is the IP address of the terminal server, and then press ENTER.

If you can successfully ping the terminal server by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.

If you cannot successfully ping the terminal server by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.

Perform additional troubleshooting steps

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 terminal server, try to ping the terminal server from another computer. If you cannot ping the terminal server from any computer, first ensure that the terminal server is running. If the terminal server is running, check the network settings on the terminal server.
  • Check the TCP/IP settings on the local computer by doing the following:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, type ipconfig /all, and then press ENTER. Make sure that the information listed is correct.
    3. 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.
    4. 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.
    5. 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.
    6. If the terminal 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.

Verify

To verify that the TS Session Broker server can successfully communicate with the terminal server:

  1. On the terminal server, start a new Terminal Services session.
  2. After the session is established, disconnect the session.
  3. On a different terminal server, but one that is also a member of the same farm in TS Session Broker, try to reconnect to your existing session. If you are able to reconnect to the existing session, the TS Session Broker server is successfully communicating with the terminal server.

Related Management Information

Terminal Server Communication

Terminal Services

Community Additions

ADD
Show: