| Event Information | According to Microsoft :
Cause :
This event is logged when the terminal server client has been disconnected because its temporary license has expired.
Resolution :
Ensure that the terminal server can discover a Terminal Services license server with the appropriate type of TS CALs installed
To resolve issue, ensure that terminal server can discover a Terminal Services license server with a sufficient number of the appropriate type of Terminal Services client access licenses (TS CALs). In order for a terminal server to receive TS CALs for its clients from a license server, the following needs to be true:
Determine if the terminal server can discover a license server
To perform procedure, must have membership in the local Administrators group, or must have been delegated the appropriate authority.
To use Licensing Diagnosis in Terminal Services Configuration:- 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 wanted, and then click Continue.
- In the left pane, click Licensing Diagnosis.
- Review the information in Licensing Diagnosis to help determine the root cause of issue:
- Under Terminal Server Configuration Details, ensure that value for Number of TS CALs available for clients is greater than 0.
- Under Terminal Services License Server Information, ensure that at least one license server is listed as discovered.
- Ensure that any license server that is listed as discovered has a sufficient number of the appropriate type of TS CALs installed to support the number of remote connections being made to the terminal server.Information about the type and number of TS CALs installed on a license server is listed under License Server Configuration Details, which is displayed when click a license server listed as discovered under Terminal Services License Server Information.
- Ensure that any license server that is listed as discovered has the appropriate type of TS CALs installed. The Terminal Services licensing mode configured on a terminal server must match the type of TS CALs available on the license server. The licensing mode for the terminal server is listed under Terminal Server Configuration Details.
Use the procedures to resolve any issues that have been identified by Licensing Diagnosis.
The license server does not have a sufficient number of TS CALs installed to support the number of remote connections being made to the terminal server
To resolve this issue, install TS CALs onto a license server by using TS Licensing Manager.
The licensing mode for the terminal server does not match the type of TS CALs installed on the license server
To resolve this issue, ensure that the Terminal Services licensing mode specified on the terminal server matches the type of TS CALs installed on the license server. The Terminal Services licensing mode determines the type of TS CALs that a terminal server will request from a license server on behalf of a client connecting to the terminal server. Therefore, the Terminal Services licensing mode specified on a terminal server must match the type of TS CALs available on the license server.
To perform this procedure,must have membership in the local Administrators group, or must have been delegated the appropriate authority.
To specify the Terminal Services licensing mode:- On the terminal server, open Terminal Services Configuration.To open Terminal Services Confiiguration, 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 wanted, and then click Continue.
- Under Licensing, double-click Terminal Services licensing mode.
- Select either Per Device or Per User, depending on your environment.
- Click OK, and then click OK.
There is a network connectivity problem between the terminal server and the license server
To resolve this issue, identify and fix any network connectivity problems between the terminal server and the license server 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 sections.
To perform these procedures,must have membership in the local Administrators group or 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 license server:- 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 license server and then press ENTER.
If the ping was successful, will receive a reply. - At the command prompt, type ping IP_address, where IP_address is the IP address of the license server, and then press ENTER.
Perform additional troubleshooting steps
These are some additional troubleshooting steps that 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 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, 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 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 using the Windows Firewall with Advanced Security snap-in.
- Check IPsec settings using the IP Security Policy Management snap-in.
|