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

JUnit – Run unit test in an Sequence / Order

In JUnit, we can use @FixMethodOrder(MethodSorters.xxx) to run the test methods in a sequence or order.

import org.junit.FixMethodOrder;import org.junit.Test;import org.junit.runners.MethodSorters;importstatic org.hamcrest.CoreMatchers.is;importstatic org.junit.Assert.assertThat;//Sorts by method name@FixMethodOrder(MethodSorters.NAME_ASCENDING)publicclassExecutionOrderTest{@TestpublicvoidtestB(){assertThat(1+1,is(2));}@Testpublicvoidtest1(){assertThat(1+1,is(2));}@TestpublicvoidtestA

Create Runnable Jar - Eclipse Options

When exporting to a Runnable Jar, there are three options in eclipse Helios. Extract required libraries into JARPackage required libraries into JARCopy required libraries into sub folder next to JAR. What are differences : Extract required libraries into JAR - Extracts the actual .class files from the libraries your app uses and puts those .class files inside the runnable JAR. So, the runnable JAR will not only contain the .class files of your application, but also the .class files of all the libraries your application uses. Package required libraries into JAR - Puts the actual JAR files of the libraries into your runnable JAR. Normally, a JAR file within a JAR file cannot be loaded by the JVM. But Eclipse adds special classes to the runnable JAR to make this possible. Copy required libraries into sub folder next to JAR - Keeps the library JARs completely separate from the runnable JAR, so the runnable JAR will only contain the .class files of your application. Option #2 is convenient be…