Windows Terminal services servers not found

  • Thread starter Thread starter topec
  • Start date Start date
T

topec

Could some help me?
I am installing a 2x ApplicationServer on application server with windows terminal services activated legally, after 3 months I got the message:
The remote session was disconnected because there are no Terminal Server License Servers available to provide a license.

Do I really need to buy MS terminal server license to use the 2x ApplicationServer ?
I check the license server and saw 12 temporary license.

thaks

to+
 
I get this message to occasionally. No rhyme or reason behind it. I have 500 licenses with only 200 - 250 being used and I still get this message. I only started getting these messages after upgrading to v6 of the ApplicationServer and client. V5.9 never did this! Howerver, I can reproduce this problem every time on a Windows 2000 machine if the Microsoft Windows Remote Desktop client isn't installed on the machine. If you install the RDP client then the message goes away, if you remove the rdp client from the machine then the message comes back. And yes you must have Terminal Services CALs to legally use terminal services.
 
Thanks a lot!
Very Interesting!!
Maybe I have to downgrade the 2x ApplicationServer.
I checked the agent and it is working properly. The only application I can use is the admin desktop.
I have the remote desktop client installed on my client desktop, it should not be the reason.
Terminal Server CALs, nowhere is writing that use should have a Terminal Services server with client licenses activate. If it is right like that then the customer's budget is quite different.
 
Downgrade does not work

mj23449 as I told you I downgraded the server to 5.1 and it is having the same problem.
 
License Servers

Hi there topec, but can I ask if you have checked to see if you have specified the license servers in your terminal server configuration?? Don't know if you are aware but if you do not specify the license servers in here then LDAP will query Active Directory for the Licenses Server connected to the specific site then will try and use the server specified there for TS licensing. This may be the reason you are not connecting to the license server.
I haven't had this problem and have been using 2x for 4 or 5 months now, but have been using terminal services for over 5 years.
 
Something Else

One other thing on licensing. If you specify licensing on a per user base then you won't see the licenses that are distributed. This is because the user licensing in Windows 2003 terminal services doesn't work. They didnt have time to do it. Only per client device will show you licenses that are issued.
 
Hello,
You need to have MS Licensing server installed and MS TS CAL for every user using published apps.
Use of 2X does not eliminate the need for MS licenses. Regardless of the version of 2X.
 
I've recently had the same message when trying to connect to a 2x server and doing this on the client PC seems to fix the problem

1. <Start>

2. <Run>

3. type regedit then Click <OK>

4. Navigate to
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\HardwareID

5. Select ClientHWID then delete and Click <OK>

6. Navigate to
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing

7. Select Store folder then delete and click <OK>

Now you should be able to connect again, only once has this not worked for me

I'm uising 2X 5.1, so not sure if it will solve the problem in the later versions
 
I know this is an old post but I had similar issues with Win8 client and 2x on 2012r2.

The solution for me was on client computer, connect to company VPN and then go to Remote Desktop Computer. Right click on Remote Desktop Computer and choose “Run as Administrator”. Log into 2x server then log off.

2x client will work now.
 
I know this is an old post but I had similar issues with Win8 client and 2x on 2012r2.

The solution for me was on client computer, connect to company VPN and then go to Remote Desktop Computer. Right click on Remote Desktop Computer and choose “Run as Administrator”. Log into 2x server then log off.

2x client will work now.
 
You must log in or register to reply here.
Back
Top