| Event Information | According to Microsoft :
Cause :
This event is logged when the terminal server client has been disconnected because its license could not be renewed.
Resolution :
Ensure that the terminal server can discover (contact) a Terminal Services license server
To resolve this issue, do the following:
Determine if the terminal server can discover a license server
To perform this 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.
- Under Terminal Services License Server Information, at least one license server should be listed as discovered.
If Licensing Diagnosis does not list any license servers as discovered, there might be a network connectivity or license server discovery configuration problem.
Identify and fix any network connectivity problems between the terminal server and the license server
To resolve issue,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 network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.
To perform 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.
If can successfully ping the license server by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.
If cannot successfully ping the license 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 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, 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 your 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.
Identify and fix any license server discovery configuration problems
To perform this procedure,must have membership in the local Administrators group, or must have been delegated the appropriate authority.
To use Review Configuration:- Open TS Licensing Manager on the license server. To open TS Licensing Manager, click Start, point to Administrative Tools, point to Terminal Services, and then click TS Licensing Manager.
- 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 All Servers, click the name of the license server, and then on the Action menu, click Review Configuration.
- In the Configuration dialog box, review any messages that indicate that terminal servers will not be able to automatically discover this license server.For example,can see either of the following messages:
- This license server is not published in Active Directory Domain Services. Terminal servers in the forest will not be able to automatically discover this license server.
- This license server is not installed on a domain controller. Terminal servers in the domain will not be able to automatically discover this license server.
Note : The message in the Configuration dialog box that appears will depend on the discovery scope that has been configured for the license server. The current discovery scope for the license server is listed in the Configuration dialog box. The recommended discovery scope for a Windows Server 2008 license server is Forest.
- If the discovery scope for the license server is set to Forest, but the license server is not published in Active Directory Domain Services can click Publish in AD DS in the Configuration dialog box to publish the license server to AD DS. To publish the license server in AD DS,must be logged on as an enterprise administrator to the forest in which the license server is a member.
- If the discovery scope for the license server is set to Domain, but the license server is not a domain controller, should consider changing the discovery scope of the license server to Forest. To change the discovery scope of the license server, click Change Scope in the Configuration dialog box.
|