Remote session disconnected

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am getting error while connecting to Terminal server through WinXP Pro
workstation. Few days back I was able to connect from same computer and right
now also, I can able to connect to terminal server through other computers, I
don't know this is server problem or this workstation problem. The error I
received is:
The remote session was disconnected because there are no terminal server
clinet access licenses available for this computer. Please contact the server
administrator.

I checked the network and everything seems to be fine to me. If it is
license then how can connect from any other computer which has internet.
Please help me to solve the problem. Thank you.
 
It seems that you have been connecting with a temporary license,
which now has expired. Most likely, the other clients will also
stop connecting, once their licenses expire.
Do you have a Terminal Server Licensing Server installed and
activated?
If so, have you verified that the TS can locate the Licensing
Server? (Check the EventLog on the TS).
Are you running W2K or 2003 on the Terminal Server?
If W2K, a TS Licensing Server is all you need, since XP Pro
clients will receive a free TS Client Access License from the
Licensing Server.
If 2003, then you need to buy and install a TS CAL for every
client that connects to the TS.
 
I checked the terminal server licensing in my W2K3 server, it seems to me
that I have sufficient licenses but I am not sure, I may be wrong. It is as:

1. Existing Windows 2000 server - terminal services CAL Token (per device)
Type-built-in, Total-unlimited, Available - unlimited, issued - 0
2. Temporary Licenses for Windows server 2003- terminal server per device
CAL token
Type-temporary, Total - -, Available - -, Issued - 2
3. Windows server 2003 - terminal server per device CAL token
Type-open, Total-10, Available-0, issued-10
Does this means that we are using temporary license. If yes, then can you
tell me how to install TS license. Do I have to install on server or on
client machine. We have four users who are always on Terminal server and they
are fine. Thank you.
 
Thanks for providing such detailed information!
No, you have run out of TS CALs.

The lines that are important are:
3. Windows server 2003 - terminal server per device CAL token
Type-open, Total-10, Available-0, issued-10

This means that you have purchased and installed 10 TS CALs
(purchased with an Open License agreement). Those 10 TS CALs have
all been issued, which means that they are in use. None of them is
avialable any more.
2. Temporary Licenses for Windows server 2003- terminal server
per device CAL token
Type-temporary, Total - -, Available - -, Issued - 2

This shows that 2 temporary licenses have been issued, no doubt
because the installed TS CALs have all been issued. Such temporary
licenses last for 90 days, and after that period you cannot
connect anymore from the same client.

So what the Licensing manager shows you is that connections have
been made from 12 different client workstations. You should even
be able to see which workstations, in the detail pane.

The only solution is to buy more TS CALs and install them on the
TS Licensing Server.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Thank you very much, it is really helpful for me to understand this. But, I
want to bother you with one more query. When I checked in detailed pane, it
only shows 5 users connected, here I get confused with my license, anyway I
will buy some more licenses. Right now I have device CAL, so can I buy user
CAL now or I have to go with device CAL. And after buying the license, I just
have to increase the number in TS or I have to call Microsoft for activation
of my licenses. Thank you again.
 
When you choose "Per Device" licenses, you made a decision which
can not be changed easily.
You will need a license for every device, even if you have only 5
users. If these 5 users log on from more than 5 workstations, "Per
User" licenses would have been cheaper.

BUT: A Terminal Server can not handle different types of licenses,
so you cannot mix Per User and Per Device if you have a single
Terminal server (it is possible with more than one TS, but never
recommended, because administration becomes a mess).
Only if you have bought your Per Device licenses with Software
Assurance, you are allowed to change them to "Per User". You have
to check this in your paperwork.

I would read the FAQ very carefully before you buy anything. If
your users run around and log on from an ever increasing number of
clients, then *this* is the time to accept your losses, throw away
your Per Device licenses, and buy Per User!

Windows Server 2003 Pricing and Licensing FAQ
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/pric
licfaq.mspx

After you have bought your licenses, you simply install them on
the TS Licensing Server, in Licesning manager. Just follow the
wizard.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
 
I thought that windows 2000 server does not accept per user licensing. You
should check on this before you buy them. In my experience I have not had
luck with the per user only the per device on a windows 2000 server. Windows
server 2003 does give you a choice between per user and per device.
 
Hi Vera,
We bought the licenses and installed it and its working fine but when I
checked the period of the license for particular device it says:
Issued on November 03, 2004 and expires on Jan 08, 2005. Does it mean that I
have to renew it again after that period? All the device connected on
terminal server has the same number of expiration date. Like issued on sep
09, 2004 and expires on Nov 14, 2004. I think I have not something which
needs to be done, please help me with this. Thank you for your great support.
 
This is a feature, Ams, not a bug :-)

All so called "permanent" licenses have an expiration date, 52-89
days from their issueing date. But you don't have to do anything
when they expire, because active clients will renew their license
automatically, starting 7 days before the expiration date.

Licenses that are not used (because the client does not
connect to the TS anymore) will automatically be returned to the
Lisencing Server after the expiration date. This prevents that a
license gets completely lost when you discard a client or re-
install the operating system on a client from scratch.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Back
Top