Prev: Access application on remote server
Next: universal do not map network printers switch?
From: zooeyhallne on 15 Apr 2010 12:26
I have a problem where RDP Terminal Server sessions are timing-out after 15
minutes of user inactivity. It is a consistent and regular disconnect after
15 minutes of inactivity. I have timed it.

If user remains active in their session, no disconnects occur. It's not a
"bad network" issue.

Everything was working fine for months with my Terminal Server, until the
last round of Windows updates were applied the other day.

No router changes have been made.

This is a 2000 Terminal server and a member in a 2003 Domain.

Checked Terminal Services Configuration-->Connections-->Sessions-->and set
Idle Session Limit to "Never". No good.

I was told to open Group Policy on the W2K terminal server, and go to Local
Computer Policy\Computer Configuration\Administrative Templates\Windows
Components\Terminal Services\Sessions folder and make changes there. However
there is no Sessions folder under that path. Just a "Client" folder.

There are no screen savers on either the server or the user's pc.

I ran into this problem a few months back on another site with the exact
same setup (W2K TS in a 2003 Domain). After much, much ado and a lot of luck
I got the problem fixed. However I can't recall all the steps I took to fix
it that time, and would really like someone to point me to the solution.

This seems to be quite a common issue, so any help is truly appreciated!


From: Kudrat Sapaev on 16 Apr 2010 03:42
Hi,

Is this server member of Windows 2003 Domain?
If yes, you have to modify a GPO linked to the OU containing your Windows
2000 Terminal Server. In that GPO you should be able to find
Computer Policy\Computer Configuration\Administrative Templates\Windows
Components\Terminal Services\Sessions
 | 
Pages: 1
Prev: Access application on remote server
Next: universal do not map network printers switch?