Network loss causes loss of TS session

[Guest Nick-Mars]

I'm having this problem with two terminal servers that we maintain (differant

clients). When a user loses their network connection, the terminal server is

killing their session instead of disconnecting it. As a result, they lose

all of the work they had open instead of being able to reconnect to their

session after the network connection is restored.

 

I was able to test this on my own computer by pulling the plug out and

watching as the session disapeared from the server about 30 seconds later.

 

I looked through the group policy settings we employ on both servers.

"Keep-alive connection" and "automatic reconnection" are both enabled.

 

Any ideas?

[Guest Mike Schumann]

Re: Network loss causes loss of TS session

 

Check the User Properties on the server. On the Session tab, you specify

whether a broken connection results in a Disconnect or Ending the Session.

 

Mike Schumann

 

"Nick-Mars" <nickmars@news.postalias> wrote in message

news:91983C6F-56D8-4742-A3B7-41B8881C19CE@microsoft.com...

> I'm having this problem with two terminal servers that we maintain

> (differant

> clients). When a user loses their network connection, the terminal server

> is

> killing their session instead of disconnecting it. As a result, they lose

> all of the work they had open instead of being able to reconnect to their

> session after the network connection is restored.

>

> I was able to test this on my own computer by pulling the plug out and

> watching as the session disapeared from the server about 30 seconds later.

>

> I looked through the group policy settings we employ on both servers.

> "Keep-alive connection" and "automatic reconnection" are both enabled.

>

> Any ideas?

[Guest Morgan che]

RE: Network loss causes loss of TS session

 

Hi,

 

Thanks for posting here.

 

From your description, I understand the terminal server session is

unexpectedly terminated. You concern how to keep every session active

rather other to be terminated. If I misunderstood, please let me know.

 

To troubleshoot this issue, please perform the following steps:

 

Step 1: Terminal Services Configuration snap-in

-----------------------------------------

If the "End a disconnected session" option is set to a very low value or

the action is chosen as "End session" when session limit is reached or

connection is broken, the terminal session will be ended when the network

connection is broken and users will be unable to reconnect to the original

session.

 

- Open the Terminal Services Configuration snap-in.

- Select "Connections" item, right click the RDP-Tcp

connection, and click Properties.

- In the Sessions tab, check the first "Override user settings"

item.

- Configure the "End a disconnected session" list to a large

time frame.

- Select the second "Override user settings" item and choose

"Disconnect from session".

- Click OK.

 

Step 2: Check group policy

---------------------------------

If some options is grayed out in the Terminal Services Configuration

snap-in, there are some group policy to configure them.

 

[Computer Configuration\Administrative Templates\Windows

Components\Terminal Services\Sessions\Sets a time limit for disconnected

sessions]

[user Configuration\Administrative Templates\Windows Components\Terminal

Services\Sessions\Sets a time limit for disconnected sessions]

[Computer Configuration\Administrative Templates\Windows

Components\Terminal Services\Sessions\Terminate session when time limits

are reached]

[user Configuration\Administrative Templates\Windows Components\Terminal

Services\Sessions\Terminate session when time limits are reached]

 

To check whether you have configured this setting and which policy has

defined it, let us use the rsop.msc tool:

 

1. Logon as a problematic user to the terminal server, click Start -> Run,

type "rsop.msc" in the text box, and click OK.

2. Locate the [Computer Configuration\Administrative Templates\Windows

Components\Terminal Services\Sessions] item.

3. Check the " Sets a time limit for disconnected sessions" item to see

whether this policy is defined. If so, the "Source GPO" column displays the

policy that defines this policy. Please set an appropriate session limit.

4. Check the "Terminate session when time limits are reached" item to see

whether this policy is defined. If so, the "Source GPO" column displays the

policy that defines this policy. If you do not want to terminate session,

please set this policy as "Not Configured".

5. Repeat the Step 2 and 3 for the other 2 policies.

6. Click Start -> Run, type "cmd" in the text box, and click OK.

7. Run the following command to refresh policy on both the domain

controller and the terminal server:

 

Gpupdate /force

 

8. Wait for a while so that the group policy is replicated and then try to

connect to the server again.

 

Hope this helps. If everything is unclear, please post back.

 

Have a good day!

 

Sincerely

Morgan Che

Microsoft Online Support

Microsoft Global Technical Support Center

 

Get Secure! - http://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.

 

 

--------------------

--->Thread-Topic: Network loss causes loss of TS session

--->thread-index: AcimUK0ASeY2kWTaQMybIRuYB/DM4Q==

--->X-WBNR-Posting-Host: 207.46.192.207

--->From: =?Utf-8?B?Tmljay1NYXJz?= <nickmars@news.postalias>

--->Subject: Network loss causes loss of TS session

--->Date: Thu, 24 Apr 2008 14:18:01 -0700

--->Lines: 13

--->Message-ID: <91983C6F-56D8-4742-A3B7-41B8881C19CE@microsoft.com>

--->MIME-Version: 1.0

--->Content-Type: text/plain;

---> charset="Utf-8"

--->Content-Transfer-Encoding: 7bit

--->X-Newsreader: Microsoft CDO for Windows 2000

--->Content-Class: urn:content-classes:message

--->Importance: normal

--->Priority: normal

--->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992

--->Newsgroups: microsoft.public.windows.terminal_services

--->Path: TK2MSFTNGHUB02.phx.gbl

--->Xref: TK2MSFTNGHUB02.phx.gbl

microsoft.public.windows.terminal_services:17190

--->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149

--->X-Tomcat-NG: microsoft.public.windows.terminal_services

--->

--->I'm having this problem with two terminal servers that we maintain

(differant

--->clients). When a user loses their network connection, the terminal

server is

--->killing their session instead of disconnecting it. As a result, they

lose

--->all of the work they had open instead of being able to reconnect to

their

--->session after the network connection is restored.

--->

--->I was able to test this on my own computer by pulling the plug out and

--->watching as the session disapeared from the server about 30 seconds

later.

--->

--->I looked through the group policy settings we employ on both servers.

--->"Keep-alive connection" and "automatic reconnection" are both enabled.

--->

--->Any ideas?

--->

[Guest Morgan che]

RE: Network loss causes loss of TS session

 

 

Hi,

 

How are you?

 

I am writing to see if you have any update about this post. If you

encounter any break/fix issue, please feel free to let me know.

 

Have a good day!

 

Sincerely

Morgan Che

Microsoft Online Support

Microsoft Global Technical Support Center

 

Get Secure! - http://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.

 

 

--------------------

--->Thread-Topic: Network loss causes loss of TS session

--->thread-index: AcimUK0ASeY2kWTaQMybIRuYB/DM4Q==

--->X-WBNR-Posting-Host: 207.46.192.207

--->From: =?Utf-8?B?Tmljay1NYXJz?= <nickmars@news.postalias>

--->Subject: Network loss causes loss of TS session

--->Date: Thu, 24 Apr 2008 14:18:01 -0700

--->Lines: 13

--->Message-ID: <91983C6F-56D8-4742-A3B7-41B8881C19CE@microsoft.com>

--->MIME-Version: 1.0

--->Content-Type: text/plain;

---> charset="Utf-8"

--->Content-Transfer-Encoding: 7bit

--->X-Newsreader: Microsoft CDO for Windows 2000

--->Content-Class: urn:content-classes:message

--->Importance: normal

--->Priority: normal

--->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992

--->Newsgroups: microsoft.public.windows.terminal_services

--->Path: TK2MSFTNGHUB02.phx.gbl

--->Xref: TK2MSFTNGHUB02.phx.gbl

microsoft.public.windows.terminal_services:17190

--->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149

--->X-Tomcat-NG: microsoft.public.windows.terminal_services

--->

--->I'm having this problem with two terminal servers that we maintain

(differant

--->clients). When a user loses their network connection, the terminal

server is

--->killing their session instead of disconnecting it. As a result, they

lose

--->all of the work they had open instead of being able to reconnect to

their

--->session after the network connection is restored.

--->

--->I was able to test this on my own computer by pulling the plug out and

--->watching as the session disapeared from the server about 30 seconds

later.

--->

--->I looked through the group policy settings we employ on both servers.

--->"Keep-alive connection" and "automatic reconnection" are both enabled.

--->

--->Any ideas?

--->