Technical: Microsoft – Windows – Remote Desktop – Unable to connect – The terminal server has exceeded the maximum number of connections


On a Mac, trying to connect to one of my MS Windows boxes, but really unable to connect.  Once I enter my user credentials (Username & password), I am being greeted with a message stating “The terminal server has exceeded the maximum number of allowed connections.”

MS Windows - Remote Desktop - Exceeded Number of Connections

Problem Discussion

Getting a bit frustrated knowing that I really need to connect to add a cname record for my Linux / CentOS machine.

I really need to get comfortable with invoking MS Windows Command from a Linux host.  I think it will help, but really not so sure of what Command Line (CLI) commands are available for MS Windows DNS Server.

But, that will wait for another day.


Fixes – Remote Control Software – Tools – CORD

One of the remote server connection tools available on Mac is CORD.

Once CORD is launched, one can create a profile for each server one wants to connect to or just use the “Quick Connect” short-cut.

I prefer registering individual servers.  And, from the server list, select the server we want to connect to.

From the ServerList, invoking the “Show Inspector” option.  Once the server is chosen then choose to Inspect the server:

  • Menu / View / Show Inspector
  • From the Server list, from the bottom bar choose the “i” option
  • In the Inspector window, ensure that “Control to console session” is checked

Current Settings:

CORD - Server - Inspector (v2)

Revised Settings:

CORD - Server - Inspector (v3)

Fixes – Remote Control Software – Tools – Remote Desktop Connection

Remote Desktop is available from

Launch the Remote Desktop tool and enter the server-name or IP Address.

Append the “/console” option to the server name.

Remote Desktop Connection for Mac

Disconnect previous connections

Once you ‘re connected, let us disconnect existing connections that are holding on to our precious two (2) maximum non-console sessions.

To disconnect our non-console sessions:

  • Launch “Terminal Services Manager”
  • If you ‘re trying to control another server, please use the menu option “Connect to Computer”
  • There are two tabs that are pertinent to us – Users and Sessions
  • The console session has a ID of 0, we want to “affect” the sessions that have IDs that are non-zero and Type is not “Console”
  • Right click the session and bring up the drop-down menu.  From the drop-down menu, select the “Disconnect” option
  • One is prompted and asked whether it is OK to proceed with the disconnection —  “Each selected Session will be Disconnected – OK or Cancel
  • We chose OK

Terminal Services Manager – User

Terminal Services Manager -- Tab - User

Terminal Services Manager – Session

Terminal Services Manager -- Tab - Session

Terminal Services Manager – Session – Each Selected Session will be Disconnected


Terminal Services Manager -- Each Selected Session will be disconnected


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s