Smart questions
Smart answers
Smart people
Join Tek-Tips Forums
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Remote Desktop has exceeded the maximum number of allowed connections

Nikolas1987 (Programmer) (OP)
9 May 13 5:08
At my office we still use Windows 2000 Server standard edition.

After 2 users have connected remotely to the server, the following users get the following message "the system has reached its licensed logon limit. please try again later windows server 2000"

I understand that w2k allows up to 2 users to be connected to the server.

I would like to know whether there is a way of extending the users allowed limit to 3 or 4.

Thanks.
strongm (MIS)
9 May 13 7:19
There are two modes for Terminal Services (as it is more correctly known on w2k), Remote Admin Mode or Application Mode.

Remote Admin mode does not require any extra licensing (i.e. cost) and is restricted to a maximum of 2 simultaneous connections. This is the two users you are talking about.
Application Mode, which would allow multiple connections requires a Terminal Server licensing server and purchase of licenses for each connecting client.

On W2k3 there is a workaround in Remote Admin Mode that allows a 3rd connection (by connecting to the server's console session)by using the /console flag for the mstsc command, but this does not work on W2K
Nikolas1987 (Programmer) (OP)
9 May 13 7:45
Can you please be a bit more specific about the Application Mode?

Is my current server not a Terminal Server?
In the Application Mode do i also get a default of 2 connections so that i only buy the extra licenses? Or if i wanted to allow 4 simultaneous connections i would have to buy 4 licenses?
strongm (MIS)
9 May 13 10:10
>Is my current server not a Terminal Server?

Well, not really, no ...

Let's have a quick overview for W2K:

Terminal Services is an optional component. When installed, it enables the "Terminal Server role" of your server. But this does not really make it a Terminal Server, because of the two modes the Terminal Services can be installed in: Remote Admin mode and Application Server Mode. Your server is really only a Terminal Server when Terminal Services are installed in Application Server mode (and note that the terminology changed for subsequent Windows server OS releases).

A quick overview of the two modes:

1) Remote Administration mode
Not really a terminal server. You can connect with a maximum of 2 sessions simultaneously, by default only for Administrators. This mode does not require additional licensing, and does not support multiple users running applications on the server.
2) Application Server mode
This is the real terminal server mode, i.e. your terminal server is now configured to handle multiple users, which run applications in a session on the terminal server. This mode requires a Terminal Services Licensing Server (this can be the same physical Windows server) and additional (paid for) licensing for all connecting users (TS CALs).

>Or if i wanted to allow 4 simultaneous connections i would have to buy 4 licenses?
As far as I recall, yes. And it is a CAL and a TS CAL you need
itsp1965 (IS/IT--Management)
10 May 13 8:49
I know this worked in Win2K3, but have you tried accessing a direct console connection (which essentially gives you 3 connections). Although this has to be executed from the command prompt
mstsc /v:<servername> /console (or /admin)
strongm (MIS)
10 May 13 11:33
>have you tried accessing a direct console connection

Already discussed in my first response.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close