PC Review


Reply
Thread Tools Rate Thread

Clients disconnected after 60min regardless of settings

 
 
Debbie
Guest
Posts: n/a
 
      2nd Mar 2004
On Windows 2000 Terminal Services, using Remote Desktop
Connection from 2000 and XP clients, the session is
disconnected after exactly 60 minutes idle (i.e. they have
minimized their session and not returned back to it). I
can recreate this both across the internet, and here
locally.

The End a Disconnected Session, Active Session Limit, and
Idle Session Limit on the users are all set so this should
not happen. Even the RDP-tcp connection where you can
override individual user sessions is not set to override
(i.e. no global settings are causing this). I've even
tested this with a user whose settings were all set to
Never.

This is happening at several different sites as well as in-
house, so I have ruled out firewall idle connection
timeouts (plus verified that this is NOT the case here in-
house).

Since RDP-tcp is a socket connection, could there be
something in Windows sockets that is doing this?

Thanks for any help,
Debbie
 
Reply With Quote
 
 
 
 
Rajneesh Mahajan \(MSFT\)
Guest
Posts: n/a
 
      5th Mar 2004
Do users get a 2 minute warning before they are disconnected? If disconnect
is issued by TS for an idle session, it gives a 2 minute warning to users.

On windows XP and server 2003, we also have a group policy (both user and
computer) that can be used to override idle session timeout. However, I
don't think this policy is available on win 2000, so that should not be a
problem in your case.

Rajneesh

--
This posting is provided "AS IS" with no warranties, and confers no rights.
TS FAQ:
http://www.microsoft.com/windows2000...minal_faq.mspx



"Debbie" <(E-Mail Removed)> wrote in message
news:590901c40087$ae669580$(E-Mail Removed)...
> On Windows 2000 Terminal Services, using Remote Desktop
> Connection from 2000 and XP clients, the session is
> disconnected after exactly 60 minutes idle (i.e. they have
> minimized their session and not returned back to it). I
> can recreate this both across the internet, and here
> locally.
>
> The End a Disconnected Session, Active Session Limit, and
> Idle Session Limit on the users are all set so this should
> not happen. Even the RDP-tcp connection where you can
> override individual user sessions is not set to override
> (i.e. no global settings are causing this). I've even
> tested this with a user whose settings were all set to
> Never.
>
> This is happening at several different sites as well as in-
> house, so I have ruled out firewall idle connection
> timeouts (plus verified that this is NOT the case here in-
> house).
>
> Since RDP-tcp is a socket connection, could there be
> something in Windows sockets that is doing this?
>
> Thanks for any help,
> Debbie



 
Reply With Quote
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Only the PC Clients get disconnected??? =?Utf-8?B?Y2JkcmFrbzk5?= Microsoft Windows 2000 Terminal Server Clients 6 4th Nov 2004 10:40 PM
I need advice on disconnected clients Peter Morris [Droopy eyes software] Microsoft ADO .NET 4 6th Jul 2004 02:45 PM
Clients disconnect after 60min idle regardless of settings Debbie Microsoft Windows 2000 Terminal Server Applications 1 4th Mar 2004 10:44 PM
RDP clients disconnected. =?Utf-8?B?SGVucmlr?= Microsoft Windows 2000 Terminal Server Clients 1 22nd Oct 2003 09:55 PM
Clients get disconnected Scott Microsoft Windows 2000 Terminal Server Applications 0 9th Jul 2003 06:38 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 08:53 PM.