• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 246
  • Last Modified:

Remote desktop

I'm trying to connect to a server and I get the following error.
"The terminal server has exceeded the maximum number of allowed connections."

Other people can connet to the server.  Any ideas?
1 Solution
looks like you terminal licence is expired as other users still have their licences onward so they can login.
one thing to check is make sure on your server the license is set to per user instead of per device(by default)
Do this by going into administrative tool >> terminal connection manager.
other to check is on your terminal server  expand the server by double clicking it and it will show you all the users with their license can you post that in your next reply.
i will post you more after looking on tht
Aaron StreetInfrastructure ManagerCommented:
by default a windows 2003 server only allows a max 3 sessions i think.. one to the consol and two remotley..

if you get terminal server manager, you can see who has legft them selves loged on and you can even disconnect them..


The posts above are talking about haveing a terminal server lincing server. this is when you can have a central limit for log on sessions. this is usefull if you have lots of log on to servers by lots of different people.

however for just admin tasks usual 3 log ons is plenty (if people log of) so there is no need for a licencing manager.
the terminal server manager is simple to use and a nice tool to have on your desk top. you simple open it connect to the server you are having problems with and you will see a list of connect users..

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Aaron StreetInfrastructure ManagerCommented:
oh if another people are already logged (not logged of correctly) on they will be able to log back on..
Rob WilliamsCommented:
To elaborate on the others' comments:

Server 2003 has 2 modes for remote access; administration mode, and terminal services mode.
By default all Server 2003 servers have administration mode enabled, and it can be enabled on server 2000. This allows only 2 simultaneous connections, plus the console session. If you exceed those 2 sessions you will receive your error message.

Terminal services or application mode has to be installed on both 2003 and 2000 servers, from add/remove programs, windows components. Doing so will also force you to enable a terminal server licensing server (within 90-120days). The number of connections is limited by the number of licenses you have installed. If you exceed the number of licenses, you will also receive a message similar to what you have above, however, I believe it will also mention licenses within the message. You can see the status of your licenses by going to administrative tools, Terminal server Licensing. If the licenses are the issue, you should see a 1000, 1003, or 1004 error in the event logs.

Are you sure the existing remote users are logging off, and not disconnecting and leaving their sessions open?
Aaron StreetInfrastructure ManagerCommented:
sorry although i know about a licencing server we dont actuly use one. as we have no real need becasue like rob explained myuch better then me. the different modes and we only log on to server to administer them.

Rob, when you say the number of licences you have installed. dows this mean you have to buy licences. or is it taken from the licencing of the OS systems you have installed?

IE if i enabled it would you have to buy termal licences, or would you get some becasue of the server already. (which currently in admin mode have two each?)

Try this command:
mstsc /v:servername(or IP address) /console
it will RDP you to a server giving you better chance to successfuly log on.
Rob WilliamsCommented:
All Windows servers allow 2 connections, so they effectively have 2 licenses. However, if you enable "full blown" terminal services, you get 120 days with server 2003, and 90 days with Server 2000, where you have unlimited temporary licenses. After that time you will be forced to set up a licensing server (add/remove programs, windows components, terminal server licensing server). The server is then activated and you have the option to add your licenses. The licenses are Terminal Server CAL's (Client Access Licenses) and are independent of your O/S CAL's. You can set up the licensing server at any time, and it will show the status of your temporary licenses, as well as any new licenses you have added. Seems to me the CAL's are about $125 US/Cdn

If you do not have full terminal services installed think about it carefully first. A domain controller should definitely not be a terminal server. Making a server a terminal server changes its optimization from background services to foreground services (applications), so think about the primary use of the server. And, finally licensing, you can have per device, or per user. Per device is default, and as I recall you have a 1 time opportunity to convert your licenses to per user. There are advantages to both. E.g. If 1 user connects from his office PC, home PC, and a mobile device, he would be better with per user. If you had a call center with 20 people sharing one PC, they would be better off with per device.
on server, type net session /delete
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now