Re: New Terminal Server Client Disconnects other Client

Tech-Archive recommends: Speed Up your PC by fixing your registry



The User who gets disconnected gets a message from terminal server telling
them that they are being disconnected and the User which causes the
disconnect does not get anything and at this time I do not know if the
eventlog has anything in it I will check that and get back to you.

"Vera Noest [MVP]" wrote:

> Are there any messages, either for the user who is being
> disconnected, or the user which causes the first user to be
> disconnected?
> Anything in the EventLog?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?Rml0emNv?= <Fitzco@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
> 08 nov 2005 in microsoft.public.windows.terminal_services:
>
> > No they are not connecting as that. I have just activated a new
> > Terminal Server computer on their domain this makes 2 and I am
> > getting the same problem it looks like I can get at most 4
> > connections on to terminal server it is looking more more to me
> > like I am having an ISP problem but I have all the remote users
> > get in on VPN connection to the main server but after that I
> > have only seen 4 users being able to get in to terminal server
> > at any one time. As I said this problem started after we had to
> > change ISP's and change the VPN software from Symantec to
> > Microsoft.
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Then they are maybe connecting to the console (= session 0),
> >> either with mstsc /console or the remote Desktops utility from
> >> the Resource Kit? The console session is always limited to one
> >> session only (which is restricted to Administrators).
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?Rml0emNv?= <Fitzco@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
> >> on 07 nov 2005 in microsoft.public.windows.terminal_services:
> >>
> >> > First thing I did. Each user has their own account they can
> >> > all connect to rdp at the sametime. The first one can
> >> > connect to Terminal Server but the next one to connect to
> >> > terminal server knocks off the first from terminal server
> >> > only not from rdp. The third one to connect knocks off the
> >> > second from terminal server and so on.
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> Sounds like they are:
> >> >> 1) sharing a single user account
> >> >> 2) allowing only a single rdp session per user
> >> >>
> >> >> I would recommend to keep setting 2) but give each user an
> >> >> unique user account.
> >> >> _________________________________________________________
> >> >> Vera Noest
> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> >> TS troubleshooting: http://ts.veranoest.net
> >> >> ___ please respond in newsgroup, NOT by private email ___
> >> >>
> >> >> =?Utf-8?B?Rml0emNv?= <Fitzco@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >> >> wrote on 04 nov 2005 in
> >> >> microsoft.public.windows.terminal_services:
> >> >>
> >> >> > I am working for a Company which is using a windows 2000
> >> >> > server for the terminal server with terminal server
> >> >> > licensing turned on and 10 Licenses installed in addition
> >> >> > we are running a other Windows 2000 as a file server. We
> >> >> > have just moved offices and had to change ISP's and
> >> >> > becuase of this have had to change the way the remote site
> >> >> > connect to the network we had a fixed IP and the users
> >> >> > would connect to a Symantec VPN firewall and then to the
> >> >> > terminal server with the new ISP their equipment will not
> >> >> > work with the Symantec Box the users use Remote Dail-in to
> >> >> > the Windows 2000 file server and then use terminal server
> >> >> > client. Which has been working for all but one of the
> >> >> > remote sites at one site only one person at a time can
> >> >> > connect to terminal services if one person is connected
> >> >> > and one of their other computers at that site tries to
> >> >> > connect the first user is disconnected but this is only at
> >> >> > one site out of seven. All Servers are up to date
> >> >> > with all patchs and fixes.
>
.



Relevant Pages

  • RE: Terminal Services has ended your session
    ... unreliable network connection. ... 216783 - Unable to Completely Disconnect a Terminal Server ... tried remote desktops and get the same result. ...
    (microsoft.public.windows.terminal_services)
  • Re: user sessions remain in disconnect state forever...
    ... policy on our backup win2K3 domain controller. ... Ultimately I would like to have those Terminal Server policy settings on the ... 216783 - You cannot completely disconnect a Terminal Server ... I have configured user session time limits etc... ...
    (microsoft.public.windows.terminal_services)
  • Re: while disconnecting its shows other user name - Terminal Serve
    ... And that they have a personal, unique profile? ... MCSE, CCEA, Microsoft MVP - Terminal Server ... To Log out the remote session, instead of Log off option the ... order to disconnect from their session. ...
    (microsoft.public.windows.terminal_services)
  • Re: smart card removal problem
    ... Windows Security and Identity ... They connect to a windows 2008 terminal server to run our ... The shop staff enter a smartcard and this automatically takes them into ... When they remove the smartcard it should then disconnect ...
    (microsoft.public.windows.terminal_services)
  • Re: smart card removal problem
    ... Windows Security and Identity ... They connect to a windows 2008 terminal server to run our ... The shop staff enter a smartcard and this automatically takes them into ... When they remove the smartcard it should then disconnect ...
    (microsoft.public.windows.terminal_services)