cannot connect to terminal server on the host machine TM 3.1

[bryanata]

When logged into the web site on the TM 3.1 server I am able to access the virtual terminal server. However when accessing TM 3.1 from a different machine via the web I am unable to access the virtual system terminal. Java starts to do its magic then I get an error "cannot connect to terminal server on the host machine". Everything else concerning TM and Java via the web works as intended. Any help would be appreciated.

Thanks

 

[sienz]

Hi,

Where can i find the Virtual System Terminal in TM3.1 web client?

 

[Stinley]

I would suspect that you have a security dongle attached to the USB port of the server hosting OTM - if so, check that the 'donglechecker.exe' process is running on the server. If it isn't, you should be able to find the .exe of the same name and be able to doubleclick this to start the process. With the process started, you should now be able to make a remote connection to the Terminal Server.

 

[captaingadget]

It may be a terminal server license issue, try this:

If an unlicensed client connects to a Terminal Server for the first time, the Terminal Server issues the client a temporary Terminal Server Client Access License (CAL) token. After the user has logged into the session, the Terminal Server instructs the License Server to mark the issued temporary Terminal Server CAL token as being validated. The next time the client connects, an attempt is made to upgrade the validated temporary Terminal Server CAL token to a full Terminal Server CAL token. If no license tokens are available, the temporary Terminal Server CAL token will continue to function for 90 days. The license is stored in the client's registry.

Thirty-two bit RDP clients store their license under the key HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To clean the client's license cache, just delete this key and its subkeys. The next time the client connects to the server, it will obtain another license.