Re: 2003 TS Session not going to disconnected
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 10 Jul 2007 14:38:28 -0700
When the network connection is lost, the session is actually
"broken".
Check your settings in
Terminal Services Configuration - RDP-TCP connection - properties -
Sessions
"When session limit is reached or connection is broken"
Have you configured the action there to "Disconnect from session", or
to "End session"?
_________________________________________________________
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?RGFu?= <dmorris@xxxxxxxxxxxxxxxxx> wrote on 10 jul 2007
in microsoft.public.windows.terminal_services:
We have 3 2003 Enterprise Edition SP2 Terminal Servers. We are.
having a problem with when a user is working remotely and the
internet drops. When the users line drops the session should go
to disconnected right. Instead the session is completely logged
off the server.
I have a policy set for our terminal servers in AD to set keep
alives and auto reconnection and we have idle and disconnected
session limits of 3 hours but it logs the session off within 2
minutes after the users loses a network connection. 2 of these
servers are in a load balancing config with session directory
and are experiencing the same issue.
It works fine if the user disconnects the session by clicking on
x. So what gives? Any ideas why the session won't go to a
disconnected state is you drop the network connection?
- Prev by Date: Re: Win98 computers cannot RDP to terminal servers
- Next by Date: Re: RDC6 on Windows XP not working like RDC5 did
- Previous by thread: RDC6 on Windows XP not working like RDC5 did
- Next by thread: Re: 2003 TS Session not going to disconnected
- Index(es):
Relevant Pages
|
