Disconnects when viewing local PC

[Adrian]

Using Windows Server 2003

If I am 'viewing' the remote Terminal Server screen my PC never disconnects
from Terminal Server, even if I am not doing anything. However, if I am
viewing my local PC Terminal server will always disconnect within about 5
minutes.

This started happening around the time I changed my local PC from a direct
internet connection to a wireless connection using a Netgear router, but
that may be a coincidence.

Any ideas?

Thanks,

Adrian.

 

[Rebecca Chen [MSFT]]

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.

 

[Adrian]

Rebecca,

Thanks for your detailed reply. I should have been a bit clearer about the
problem, and I have done a bit more testing.

The topology is:

1. There is a terminal server which is running win2k3 server on our office
LAN.
2. I access the terminal server from home with a Windows 2000 PC using a
Netgear router and cable modem to connect to the Internet.

I can leave my home PC connected to the terminal server for hours or
overnight and it will never disconnect PROVIDING I leave it 'viewing' the
remote Terminal Server. If I switch to do something on my local PC it will
always disconnect within 5 minutes.

Since my first post I have tested it with removing the Netgear Router and
connecting my PC directly to the cable modem. If I do this it no longer
disconnects within 5 minutes if I switch to do something on my local PC. It
therefore must be something connected with the Netgear router.

Any ideas?

Regards,

Adrian

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.

 

[Rebecca Chen [MSFT]]

Hi Adrian,

I have more concert idea about the topology.

According to your description, I believe this issue is related to the
Netgear router since this issue disappears when you use a cable modem. Some
routers will automatically drop the idea session if there is no incoming or
outcoming packages go thought the router.

With regards to when 'viewing' the remote Terminal Server screen, probably,
there are some packages go in/out the router when you stay at the "view
screen" since the program need to communicate with the remote terminal
server to return the server status. This explains why the router will end
this session.

You can also take a screen shot of the "view screen" and send it to
(e-mail address removed) for confirmation.

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.

 

[Adrian]

Rebecca,

..Some routers will automatically drop the idea session if there is no incoming or
outcoming packages go thought the router...
..probably, there are some packages go in/out the router when you stay at the "view
screen" ..

I imagine this must be the case.

I wonder if anyone else has come across this and found a solution so that
the Netgear router does not drop the session.

Regards,

Adrian

 

[Vera Noest [MVP]]

Have you tried to enable KeepAlives?

http://terminal.servebeer.com/php/flaky_connections.php

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

 

[Rebecca Chen [MSFT]]

Yes, that is a very good point.

Adrian, if you make sure the router is the case, you refer to the link as
Vera has provided to modify the key, alternatively, you can set the
registry key by enabling the following GPO:

1. Key in "gpedit.msc" in Run box on the win2k3 server.

2. Locate to Computer Configuration\Administrative Templates\Windows
Components\Terminal Services

3. Enable "Keep-Alive connections" policy to set interval less than 5
minutes, for example, set it to 1.



You can use this setting to enable keep-alive connections and ensure that
the session state is consistent with the client state. By default,
keep-alive connections are disabled.

To configure keep-alive connections, enable the setting and set the
Keep-alive interval. The keep-alive interval determines how often, in
minutes, the server checks the session state.

Please refer to the following link about the policy:

KeepAliveInterval
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
guide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/de
ployguide/en-us/263728.asp

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.