Need a solution to disconnect problem

I have taken over a client with a terminal server that is open through the
firewall on the default RDP port of 3389. There are no settings implemented
to force disconnect or log off after any particular period of time. So users
can stay connected, idle or not forever.

On user in particular who has a new Dell latop running Windows XP Pro SP3,
can stay connected forever so long as he does not open the internet on his
local PC. If he minimizes the RDP session, opens the internet and then is
idle in the RDP session, the session will freeze after 3-5 minutes forcing
him to close the session and log in again. If he has internet open on his
local PC but stays active in the RDP session it will operate indefinately so
long as he is not idle for that 3-5 minutes.

I am at a loss on this one. Any help would be appreciated.

Thanks
Tony

 

First of all, is this user connected to the TS like any other user? For
example, if he is over DSL, there are known issues in this case where the
connection may drop after a while.
Tweaking the TCP stack may help (look for TCPMaxDataRetransmissions and
KeepAlives on Google).

Cláudio Rodrigues
CEO, WTSLabs Inc.



Citrix CTP
Quest Provision Networks VIP

"Tony Vrolyk" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> I have taken over a client with a terminal server that is open through the
> firewall on the default RDP port of 3389. There are no settings implemented
> to force disconnect or log off after any particular period of time. So users
> can stay connected, idle or not forever.
>
> On user in particular who has a new Dell latop running Windows XP Pro SP3,
> can stay connected forever so long as he does not open the internet on his
> local PC. If he minimizes the RDP session, opens the internet and then is
> idle in the RDP session, the session will freeze after 3-5 minutes forcing
> him to close the session and log in again. If he has internet open on his
> local PC but stays active in the RDP session it will operate indefinately so
> long as he is not idle for that 3-5 minutes.
>
> I am at a loss on this one. Any help would be appreciated.
>
> Thanks
> Tony
>
>
> <!--colorc--><!--/colorc-->

 

I don't believe other users from his remote locations experience the problem
but then their job function may not require them to be on the internet at
all. So situation may be unique.

I will look into the settings you mention. Thanks

Tony


"Cláudio Rodrigues [MVP]" <CludioRodriguesMVP@discussions.microsoft.com>
wrote in message news:C5E5CBDE-017D-4036-A154-604B59CBF700@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> First of all, is this user connected to the TS like any other user? For
> example, if he is over DSL, there are known issues in this case where the
> connection may drop after a while.
> Tweaking the TCP stack may help (look for TCPMaxDataRetransmissions and
> KeepAlives on Google).
>
> Cláudio Rodrigues
> CEO, WTSLabs Inc.
>
>
>
> Citrix CTP
> Quest Provision Networks VIP
>
> "Tony Vrolyk" wrote:
><!--coloro:green--><span style="color:green <!--/coloro-->
>> I have taken over a client with a terminal server that is open through
>> the
>> firewall on the default RDP port of 3389. There are no settings
>> implemented
>> to force disconnect or log off after any particular period of time. So
>> users
>> can stay connected, idle or not forever.
>>
>> On user in particular who has a new Dell latop running Windows XP Pro
>> SP3,
>> can stay connected forever so long as he does not open the internet on
>> his
>> local PC. If he minimizes the RDP session, opens the internet and then is
>> idle in the RDP session, the session will freeze after 3-5 minutes
>> forcing
>> him to close the session and log in again. If he has internet open on his
>> local PC but stays active in the RDP session it will operate indefinately
>> so
>> long as he is not idle for that 3-5 minutes.
>>
>> I am at a loss on this one. Any help would be appreciated.
>>
>> Thanks
>> Tony
>>
>>
>> <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->