| Event Information | According to Microsoft :
Diagnose :
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.
To resolve this issue :
Cause
There is a network connectivity problem between the terminal server and 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 TS Session Broker server.
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 can ping other servers but not the license server, try to ping the license server from another computer. If cannot ping the license server from any computer, first ensure that the license server is running.If the license server is running, check the network settings on the license 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,it may indicate a corrupt TCP/IP stack or a problem with network adapter.
- Type ping IP_address, where IP_address is the IP address assigned to the computer. If 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 network,should ping each one. If 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 license server is on a different subnet, try to ping the default gateway. If 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.
Cause
There is an issue with DNS
Resolution :
Identify and fix DNS issues
To 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.
Cause
The Terminal Services Session Broker service is not running on the TS Session Broker server
Resolution :
Start the Terminal Services Session Broker service
To resolve this issue, start the Terminal Services Session Broker service 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 start the Terminal Services Session Broker service:- 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, right-click Terminal Services Session Broker, and then click Properties.
- On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
- Under Service status, click Start.
- Click OK to close the Terminal Services Session Broker Properties dialog box.
- Confirm that the Status column for the Terminal Services Session Broker service displays Started.
Cause
An incorrect name or IP address is listed for the TS Session Broker server
Resolution :
Specify the correct name or IP address of the TS Session Broker server
To resolve this issue, specify the correct name or IP address of the TS Session Broker server. TS Session Broker setttings can be configured either by using the Terminal Services Configuration tool or by using Group Policy.- Specify the TS Session Broker server by using Terminal Services Configuration
To perform this procedure,must have membership in the local Administrators group, or must have been delegated the appropriate authority.
To specify this :- 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, enter the correct computer name or IP address of the TS Session Broker server. The TS Session Broker server is the computer where the TS Session Broker role service is installed.
- Click OK to close the Properties dialog box.
- Specify the TS Session Broker server by using Group Policy
If the name or IP address of the TS Session Broker server has been specified by using Group Policy, change the Group Policy setting that is being applied to the terminal server so that the correct name or IP address is entered for the TS Session Broker server.
The name or IP address of the TS Session Broker server can be specified in the Configure TS Session Broker server name Group Policy setting. This Group Policy setting is located in Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\TS Session Broker. Note that the Group Policy setting will take precedence over the setting configured in Terminal Services Configuration. |