Re: One user disconnected from TS...
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 20 Jul 2006 14:49:00 -0700
OK, this can be done in 2 different ways:
1. by a GPO, in User Configuration - Administrative Templates -
Windows Components - Terminal Services - Sessions
"Set a time limit for active but idle Terminal Services sessions"
For this to apply to a single user, the Security filtering of the
GPO would have to be set specifically to apply only to this user
(or a user group which only contains this user account)
Note: This setting appears in both Computer Configuration and User
Configuration. If both settings are configured, the Computer
Configuration setting overrides.
2. Directly on the TS:
Terminal Services Configuration - rdp-tcp connection - properties -
Session - Idle session limit
By *unchecking* the box "Override user settings"
AND then configuring in Active Directory User & Computers, in the
User account properties - Sessions - Idle session limit
Seems unlikely to me that someone would deliberately modify the
default settings to such a short idle time-out limit for a single
user, but there's no harm in checking.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"centre21" <centre21@xxxxxxxxx> wrote on 20 jul 2006 in
microsoft.public.windows.terminal_services:
Thanks for the prompt response, but I'm inclined to think that.
it's probably the individual timeout settings for two reasons:
1. I didn't set up this network, so I'm not really sure what
they've got
2. There's no router between the server and the clients, this is
all on a local network.
So, if you have any suggestions about how to set the individual
timeout settings, I'm all ears.
B
Vera Noest [MVP] wrote:
It is possible to set time-out limits on a per-user basis, but
it seems unlikely that this is the case, if you are not aware
of it.
Another possible cause for inactivity time-outs is a router
between your client and your server, which sees no traffic and
decides that the session must have ended and throws it out.
Since this happens after only 3-5 minutes of idle time, my
guess is that it is a router. The solution in that case is to
enable KeepAlives. For the correct registry key, check:
216783 - Unable to Completely Disconnect a Terminal Server
Connection
http://support.microsoft.com/?kbid=216783
Also check this link:
http://terminal.servebeer.com/php/flaky_connections.php
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"centre21" <centre21@xxxxxxxxx> wrote on 20 jul 2006 in
microsoft.public.windows.terminal_services:
Here's a strange one - I have an office of about 10 users and
they all connect to Terminal Server for their e-mail,
applications, etc. One user gets disconnected from her
session if she's idle for 3-5 minutes, but no one else has
this issue. Is there a way to set an individual time out?
Could this be due to network errors? This one really baffles
me.
- References:
- One user disconnected from TS...
- From: centre21
- Re: One user disconnected from TS...
- From: Vera Noest [MVP]
- Re: One user disconnected from TS...
- From: centre21
- One user disconnected from TS...
- Prev by Date: Re: One user disconnected from TS...
- Next by Date: Lock Down Remote Users but Not Interactive/Console Users
- Previous by thread: Re: One user disconnected from TS...
- Next by thread: Re: Removing Terminal Services
- Index(es):
Relevant Pages
|
Loading