1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Cannot connect to disconnected sessions

Discussion in 'Windows Home Server' started by Ben Scaithe, Aug 24, 2009.

  1. Ben Scaithe

    Ben Scaithe Guest

    I am trying to determine why so many of our Terminal Service sessions end up
    being disconnected. When our users reconnect, they are given new sessions.
    I try to connect to a disconnected session in the TS Manager to shut it down
    the right way, and it asks for a password. I put in the correct password,
    and it comes back with an error 1326, telling me that it's incorrect. The
    only way I can currently clear out these sessions is to reset them, which
    isn't very proper. Any idea why I can't connect to these sessions?
     
  2. What is the Windows version of Terminal Services are you running?
    Can you please confirm is the server setting 'Restrict each user to a single
    session' is set to 'yes'?
    You can find this setting in TSConfig.msc (or Tscc.msc if win2k3 and
    earlier).
    Thanks
    Soo Kuan


    --
    This posting is provided "AS IS" with no warranties, and confers no rights.

    "Ben Scaithe" <quixotic68@hotmail.com> wrote in message
    news:%23XcSwnRJKHA.4292@TK2MSFTNGP03.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >I am trying to determine why so many of our Terminal Service sessions end
    >up being disconnected. When our users reconnect, they are given new
    >sessions. I try to connect to a disconnected session in the TS Manager to
    >shut it down the right way, and it asks for a password. I put in the
    >correct password, and it comes back with an error 1326, telling me that
    >it's incorrect. The only way I can currently clear out these sessions is
    >to reset them, which isn't very proper. Any idea why I can't connect to
    >these sessions?
    > <!--colorc--><!--/colorc-->
     
  3. Ben Scaithe

    Ben Scaithe Guest

    We are running running TS on Windows Server 2003 R2 64bit. Restrict each
    user to a single session is already set to "Yes".


    "Soo Kuan Teo [MSFT]" <sookuant@online.microsoft.com> wrote in message
    news:e6TCuuaJKHA.4376@TK2MSFTNGP03.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > What is the Windows version of Terminal Services are you running?
    > Can you please confirm is the server setting 'Restrict each user to a
    > single session' is set to 'yes'?
    > You can find this setting in TSConfig.msc (or Tscc.msc if win2k3 and
    > earlier).
    > Thanks
    > Soo Kuan
    >
    >
    > --
    > This posting is provided "AS IS" with no warranties, and confers no
    > rights.
    >
    > "Ben Scaithe" <quixotic68@hotmail.com> wrote in message
    > news:%23XcSwnRJKHA.4292@TK2MSFTNGP03.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >>I am trying to determine why so many of our Terminal Service sessions end
    >>up being disconnected. When our users reconnect, they are given new
    >>sessions. I try to connect to a disconnected session in the TS Manager to
    >>shut it down the right way, and it asks for a password. I put in the
    >>correct password, and it comes back with an error 1326, telling me that
    >>it's incorrect. The only way I can currently clear out these sessions is
    >>to reset them, which isn't very proper. Any idea why I can't connect to
    >>these sessions?
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     

Share This Page