Skip to main content

The terminal server has exceeded the maximum number of allowed connections

If you are using Microsoft’s Remote Desktop utility over a network to connect to other remote Windows machines then you must have encountered an error message while connecting to the machine -

“The terminal server has exceeded the maximum number of allowed connections”

This problem usually occurs due to following reasons :
  1. In Windows, normally  only 2 users at time can connect to the same  remote windows machine, thus if a third user wants to connect to the same remote windows machine then he will get this error.
  2. After using the remote desktop connection on a remote windows machine, users normally disconnects the remote connection just by clicking on the cross button coming up on their screen. This practice only closes the remote desktop window opened on the user’s screen but it doesn’t closes the session made on that remote windows machine for the user. Thus, user’s session is still running although he has closed the window.  This leads to a situation where no user is currently accessing the remote windows machine but when anyone try to connect to it, we get the above error.  We should always log off form the remote machine  instead of just clicking the cross button.

Even in this situation, Remote Desktop Connection utility have a mechanism to connect remotely to the windows machine,  kill the existing remote connections and even do our work on that remote system. Executing the Remote Desktop Connection utility with some parameters provides a third connection to the remote windows system :

mstsc -v: x.x.x.x /f -console

Replace the x.x.x.x with the IP Address of the remote system and execute the above command through Start -> Run.

Comments

Popular posts from this blog

Exploring Node.js Internals

I found a great article explaining Node JS internals, must read :

https://www.smashingmagazine.com/2020/04/nodejs-internals/


Some other articles :

Introduction to Node.jsBeing an official website, Node.dev explains what Node.js is, as well as its package managers, and lists web frameworks built on top of it.“JavaScript & Node.js”, The Node Beginner BookThis book by Manuel Kiessling does a fantastic job of explaining Node.js, after warning that JavaScript in the browser is not the same as the one in Node.js, even though both are written in the same language.Beginning Node.jsThis beginner book goes beyond an explanation of the runtime. It teaches about packages and streams and creating a web server with the Express framework.LibUVThis is the official documentation of the supporting C++ code of the Node.js runtime.V8This is the official documentation of the JavaScript engine that makes it possible to write Node.js with JavaScript. x

How to check if environment variable is set using shell script?

If you are wondering how can we check whether an environment variable is set or not in the system, here are few methods :
1. Manually a. Run “set” command on the shell prompt, it will list out all the variables set in the system : # set b. Run “echo” command on the shell to print the value of the environment variable : # echo $<environment variable>
2. Through Shell Script Let say we intent to check whether environment variable “envVar” is set or not?
a. Method 1 – checking if “envVar” is set to “” (no value) : if [ "$envVar" == "" ] then echo “envVar is not set” else echo “envVar is set” fi
b.Method 2 – checking if “envVar” is non NULL : if [ -n "$envVar" ] then echo “envVar has non NULL value, it is set.” else echo “envVar has NULL value, it is not set.” fi