Hi Adrian,
I am not very clear about your network environment. I assume the current
topology is as follows:
1. There is a remote terminal server which is running win2k3 server.
2. There is a XP machine running in the LAN.
When you terminal to the win2k3 server, the session will never be
disconnected. However, when you remote desktop to WinXP in the LAN, the
session will be disconnected in 5 minutes.
Based on my research, there are several possible causes, including the new
router. Please use the following steps to isolate this issue:
Step 1: Check win2k3 serve session settings
=================================
NOTE: If win2k3 terminal server is not the problem, please ignore all steps
about win2k3.
To increase the timeout for idle session in Windows Server 2003, there are
two ways:
1. Configure the Rdp-tcp connection property.
2. Configure the group policy [Computer Configuration\Administrative
Templates\Windows Components\Terminal Services\Session\Set a time limit for
active but idle Terminal Services sessions] and [User Configuration ->
Administrative Templates-> Windows Components -> Terminal
Services->Sessions].
The group policy setting overrides the RDP-tcp connection property; and the
Computer Configuration group policy setting overrides the User
Configuration group policy setting overrides.
To configure the RDP-tcp connection, please perform the following steps:
1. Open the Terminal Services Configuration snap-in.
2. Select "Connections" item, right click the RDP-Tcp connection, and click
Properties.
3. In the Sessions tab, you can configure the setting for "Idle session
limit". If you set it to "Never", idle session will not be disconnected.
Step 2: Check local policy
===================
To configure the group policy, please do the following on both win2k3 or XP
machine:
1. Click Start, click Run, type "gpedit.msc" (without the quotation marks),
and then press ENTER.
2. Double-click the following items and set "set a time limit for active
but idle terminal services sessions":
- Computer Configuration
- Administrative Templates
- Windows Components
- Terminal Services
- Session
3. Refresh the group policy.
1) Click Start -> Run, type "cmd" in the text box, and press OK.
2) Type the following command in the Command window:
GPUpdate /Target:Computer /Force
This information is stored in
HKLM\Software\Policy\Microsoft\WindowsNT\TerminalServices\MaxIdleTime
registry key.
For more information, please refer to:
294751 Terminal Services Group Policy Objects
http://support.microsoft.com/?id=294751
Step 3: Check the new router
=======================
According to my experience, some routers will drop the incoming package is
certain the idea period.
Therefore, you can try to remote desktop to the XP client in LAN to see if
this issue occur.
If possible, please change back to your old router to test this issue.
Any update, let us get in touch!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.