| Event Information | According to Microsoft :
Cause :
This event is logged when the server failed to retrieve the security identifier (SID) of the TS Session Broker server.
Resolution :
Identify and fix network connectivity issues
To resolve this issue, identify and fix any network connectivity problems between the terminal server and the Active Directory domain controller by doing 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 terminal server and the domain controller:- 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 (FQDN) of the domain controller (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 - At the command prompt, type ping IP_address, where IP_address is the IP address of the domain controller, and then press ENTER.
If you can successfully ping the domain controller by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.
If you cannot successfully ping the domain controller 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 domain controller, try to ping the domain controller from another computer. If you cannot ping the domain controller from any computer, first ensure that the domain controller is running. If the domain controller is running, check the network settings on the domain controller.
- 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 domain controller 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 terminal server has successfully joined a farm in TS Session Broker, use either of the following methods:
Method one
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority. - On the terminal server, open Event Viewer. To open Event Viewer, click Start, point to Administrative Tools, and then click Event Viewer.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the left pane, expand Windows Logs, and then click System.
- Look for an event with a Source of TerminalServices-SessionBroker-Client and an Event ID of 1005. This event indicates that the terminal server has successfully joined a farm in TS Session Broker.
Method two- On the terminal server that has been joined to a farm in TS Session Broker, start a new Terminal Services session by using the IP address of the terminal server.
- After the session is established, disconnect the session.
- To connect to a different terminal server that is also a member of the same farm, use the IP address of that terminal server and the same user credentials that you used to connect to the first terminal server. If you are able to reconnect to the existing session on the first terminal server, the terminal server is successfully joined to a farm in TS Session Broker.
|