• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 458
  • Last Modified:

Terminal Server ends client connections after about 5 minutes of idle time.

Running a brand new 2003 server.  Installed terminal server in APP mode.  XP clients using 32bit TSC are connecting to the 2003 TS just as they were the 2000 TS just a few days ago.  The 2000 TS never ended the connection due to idle time.  The 2003 server is ending the session within 5 - 10 min of inactivity.  This is becoming a real head ache and causing database corruption problems with one of the apps we are running on the TS machine.

I have changed the screen saver to none on each client logon.  I have changed the TS Configuration to override client setting and to allow 1 day of idle time.  I am at a loss as to where to go from here.  Please help!

Thanks

Tim
0
leadingsx
Asked:
leadingsx
1 Solution
 
What90Commented:
0
 
leadingsxAuthor Commented:
I looked at the GPO settings pertaining to TS and everything is showing up as not configured.  If the status is set to Disabled or Not Configured, time limits for active sessions are not specified at the Group Policy level.  However, an administrator can specify time limits for active sessions in the Terminal Services configuration tool.

In the TSCC, RDP-Tcp Properties, Sessions, I have check "Override user settings" and I have set the "End a disconnected session" to 1 hour.  I have set the "Active session limit" to 1 day.  I have set the "Idle session limit" to 1 day.  Everything else is left unchecked or unconfigured.

I am downloading the TS client you pointed me towards.  I don't think that will help but I will try it.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now