• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • FREE workshop: Preparing contractors for Autumn : Weds 29th Sep at 7.15pm. More details here.

2 many connections on server when remoting on to it

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    2 many connections on server when remoting on to it

    I need to remote onto a windows server but everytime I login it says 'max connections exceeded', there is a command you can run from command line that kicks off everyone already logged for the life of me I can't remeber it and can't find it on google, anyone know it ?

    #2
    Dunno, but you'll need someone able to log directly onto the server to do anything.

    When I was in a similar situation a while back, I installed PC Anywhere so I could use that if remote desktop wouldn't let me in for some reason.

    Anyway, if you can get a command prompt, you can reboot! Alternatively, stopping/starting the remote service should do.
    Feist - 1234. One camera, one take, no editing. Superb. How they did it
    Feist - I Feel It All
    Feist - The Bad In Each Other (Later With Jools Holland)

    Comment


      #3
      Originally posted by Bumfluff View Post
      I need to remote onto a windows server but everytime I login it says 'max connections exceeded', there is a command you can run from command line that kicks off everyone already logged for the life of me I can't remeber it and can't find it on google, anyone know it ?
      Try starting the RDP client with the "console" flag by typing "mstsc /console" at a command prompt. This will then log you on to the console session on whichever box you connect to.
      Last edited by voodooflux; 24 October 2008, 22:14. Reason: Wrong command
      Where are we going? And what’s with this hand basket?

      Comment


        #4
        Originally posted by PAH View Post
        Anyway, if you can get a command prompt, you can reboot! Alternatively, stopping/starting the remote service should do.
        If you've remoted in to a command prompt, stopping the remote service is easy - starting it again, not so much

        Comment


          #5
          Windows server has a hard limit of 2 RDP connections and 1 console connection (making 3).

          If you want to go above this, you need terminal services... good luck with that.

          TM

          Comment


            #6
            Originally posted by NickFitz View Post
            If you've remoted in to a command prompt, stopping the remote service is easy - starting it again, not so much
            try the...

            shutdown /r /m \\servername

            command from a remote machine

            TM

            Comment


              #7
              In the past I've just used mstsc.exe /console to connect. I believe this will kick off any other console user currently connected. Then, assuming you are admin on the server you can use the remote management tool (not 100% on name) to go and start kicking off anyone else. Used to do this kind of thing all the time in my permie job, when people had left a connection open after going home etc.

              Comment


                #8
                Terminal services manager (admin toolkit) will allow you to see who is connected - then reset them - provided you are an admin.
                Session limits on idle / disconnected or even active sessions can be set either on individual servers or group policy

                Comment

                Working...
                X