RDC License Issue

  • Thread starter Thread starter Carlos M Suarez
  • Start date Start date
C

Carlos M Suarez

Hi Everyone,



I was wondering if any of you have experience the
following problem with RDC (Remote Desktop Connection) I
have two clients with this problem the first client is
using Windows XP Pro, second client is using Windows 2000.
Each client works for a different company and are getting
the following error.



"Remote Desktop Disconnected"

The remote session was disconnected because there are no
terminal server clients access licenses available for this
computer



Please not the problem is not with the server each user
has more then one workstation, if they go to there second
computer they are able to login to the server. This
problem is with the local client workstation this issue
has me puzzled and I was wondering if there's a fix or
article on this issue. I have not yet been able to find
the article. If you know the answer to this problem please
email me or post it on here, thanks for all of your help.

Sincerely,

Carlos M Suarez
Network Admin
Email:[email protected]
C&O Network Solutions
 
Carlos -

It sounds like you need licenses for the clients with the problem.
Check out the info on licenses on the TS FAQ:
http://www.microsoft.com/windows2000/community/centers/terminal/terminal_faq.mspx

Hi Everyone,



I was wondering if any of you have experience the
following problem with RDC (Remote Desktop Connection) I
have two clients with this problem the first client is
using Windows XP Pro, second client is using Windows 2000.
Each client works for a different company and are getting
the following error.



"Remote Desktop Disconnected"

The remote session was disconnected because there are no
terminal server clients access licenses available for this
computer



Please not the problem is not with the server each user
has more then one workstation, if they go to there second
computer they are able to login to the server. This
problem is with the local client workstation this issue
has me puzzled and I was wondering if there's a fix or
article on this issue. I have not yet been able to find
the article. If you know the answer to this problem please
email me or post it on here, thanks for all of your help.

Sincerely,

Carlos M Suarez
Network Admin
Email:[email protected]
C&O Network Solutions
Click to expand...

This posting is provided "AS IS" with no warranties, and confers no rights
 
Ivanei,



Thanks for taking the time to reply to my post
and try to help me. I checked the link that you posted but
I still haven't found the correct answer. Perhaps I am
confused I thought Remote Desktop Connection client
requires no license for Windows 2000 & XP?



-Carlos M. Suarez
 
Provided that the TS is running W2K, then W2K Pro and XP Pro
clients receive a free TS CAL from the TS Licensing Server.
So you *must* have a LS installed and activated.
If the clients run the Home Edition of W2K or XP, you will need to
buy and install TS CALs fore them on the LS.

If the TS runs Windows 2003, you'll need to install a TS CAL for
every client.
 
I have the same problem. I have activated the Terminal Server and
installed the CAL pack. The Licencse Manager program shows that I have
20 available client licenses.

I have also deleted teh registry key on the client machine that had
the Temporary License information. (This was issued before I activated
the Terminal Server on my Win2k3 Server).

Any help will be appreciated.

Ram
 
It's usually not a good idea to take over someone else thread with
"I have the same problem..." Much easier for everyone involved to
start a new thread. You seem to have a completely different
problem, so I've deleted the history of the original thread.

You write that you activated the TS, but only the TS Licensing
Server can be activated. I assume that you mean the LS?
With CAL pack, do you mean server CALs or TS CALs?
Assuming again TS CALs, did you buy them "Per User" or "Per
Device"?

If you have installed "Per User" TS CALs: is the Terminal Server
(not the Licensing Server!) set to use "Per User" licensing? The
default is "Per Device"!
You can check this from Administrative Tools - Terminal Services
Configuration - Server Settings
If it's set to Per Device mode, it will look for a Device TS CAL
and will not issue your Per User TS CALs.
Note that you must reboot the server after making the switch!

Check this article as well, it explains that even after you have
switched licensing mode on the TS, your User TS CALs count will
not be decremented:

822134 - The Function of Terminal Server CALs in Windows Server
2003
http://support.microsoft.com/?kbid=822134

If this doesn't help, can you post any events from the EventLog on
the TS that show up when you try to connect?
Can you also post the exact error message that you get?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

(e-mail address removed) (Ram Ramakrishnan) wrote in
 
Back
Top