Please help

i have remote windows 98 clients running RDP client connecting to a windows 2000 terminal server. The terminal server is within a windows NT domain. The clients can connect to the terminal server without any problems. However, as soon as the terminal session is minimized and runs in the backgroud, the session is dropped within minutes.

The connection configuration is set as follows

1. End a disconnected session - 2 hr
2. Active session limit - 3 hr
3. Idle session limite - 3 hr

The following registry settings have also been modified;

4. HKLM\System\current control set\control\terminal server\KeepaliveEnable is set it to
5. Both keepAlivetime and KeepAliveInterval under TCP/IP parameters in the registry have also been changed
6. HKLM\System\CurrentControlSet\Services\Tcpip\parameter\TcpMaxDataRetransmissions has been changed to 1

The remote users are connecting to the terminal server via DSL, private WAN. Does anyone have any idea why this is happening? Your help will be much appreciate

Carol,

Does your firewall have a session timeout setting? We were using a SonicWall
Pro 200 and we had to increase the timeout. Do the users ever get
disconnected if they are actually working in the session?

My bet would be your firewall. Do you have a VPN in place, the reason I ask
is that you could test the theory by connecting them over the VPN then see
if the connection times out.

I have customers that I can TS to all day over VPN but if I do it direct to
the firewall IP I get disconnected by the firewall timeout.

Good luck
Greg
(E-Mail Removed)

"Carol" <(E-Mail Removed)> wrote in message
news:72C47C71-A681-4826-9086-(E-Mail Removed)...
> Please help!
>
> i have remote windows 98 clients running RDP client connecting to a
windows 2000 terminal server. The terminal server is within a windows NT
domain. The clients can connect to the terminal server without any problems.
However, as soon as the terminal session is minimized and runs in the
backgroud, the session is dropped within minutes.
>
> The connection configuration is set as follows;
>
> 1. End a disconnected session - 2 hrs
> 2. Active session limit - 3 hrs
> 3. Idle session limite - 3 hrs
>
> The following registry settings have also been modified;
>
> 4. HKLM\System\current control set\control\terminal server\KeepaliveEnable
is set it to 1
> 5. Both keepAlivetime and KeepAliveInterval under TCP/IP parameters in the
registry have also been changed.
> 6.
HKLM\System\CurrentControlSet\Services\Tcpip\parameter\TcpMaxDataRetransmiss
ions has been changed to 10
>
> The remote users are connecting to the terminal server via DSL, private
WAN. Does anyone have any idea why this is happening? Your help will be
much appreciated
>
>
>
>

Hello Carol,



I am having the exact same problem and I have not figured
it out yet either.... running hundreds of end-users and
getting serious complaints every single day.

Besides the firewall timeout possibility, any MVP out
there would know the answer to that one ???

:-)

Francois




>-----Original Message-----
>Carol,
>
>Does your firewall have a session timeout setting? We
were using a SonicWall
>Pro 200 and we had to increase the timeout. Do the users
ever get
>disconnected if they are actually working in the session?
>
>My bet would be your firewall. Do you have a VPN in
place, the reason I ask
>is that you could test the theory by connecting them over
the VPN then see
>if the connection times out.
>
>I have customers that I can TS to all day over VPN but if
I do it direct to
>the firewall IP I get disconnected by the firewall
timeout.
>
>Good luck
>Greg
>(E-Mail Removed)
>
>"Carol" <(E-Mail Removed)> wrote in
message
>news:72C47C71-A681-4826-9086-(E-Mail Removed)...
>> Please help!
>>
>> i have remote windows 98 clients running RDP client
connecting to a
>windows 2000 terminal server. The terminal server is
within a windows NT
>domain. The clients can connect to the terminal server
without any problems.
>However, as soon as the terminal session is minimized and
runs in the
>backgroud, the session is dropped within minutes.
>>
>> The connection configuration is set as follows;
>>
>> 1. End a disconnected session - 2 hrs
>> 2. Active session limit - 3 hrs
>> 3. Idle session limite - 3 hrs
>>
>> The following registry settings have also been modified;
>>
>> 4. HKLM\System\current control set\control\terminal
server\KeepaliveEnable
>is set it to 1
>> 5. Both keepAlivetime and KeepAliveInterval under
TCP/IP parameters in the
>registry have also been changed.
>> 6.
>HKLM\System\CurrentControlSet\Services\Tcpip\parameter\Tcp
MaxDataRetransmiss
>ions has been changed to 10
>>
>> The remote users are connecting to the terminal server
via DSL, private
>WAN. Does anyone have any idea why this is happening?
Your help will be
>much appreciated
>>
>>
>>
>>
>
>
>.
>

Carol,


I am (desperatly) looking for a clock (tiny - digital)
that will launch with an "Always On Top" option and
refresh itself every single second... I believe this could
perhaps be sufficient network traffic to keep the
connection from stopping.... However, I have not been
able to find a clock that does NOT have a systray
reference.... An issue for me as the TS users do not have
systray visible (GPO) and all clocks I have found created
a mem or systray failure (as systray is not there and
somehow the clock icon is looking for the taskbar without
success.... [see softwaremaniacs.com's DeskClock for an
example of what I am talking about] .... could work
perfectly.... but the systray ref for me is a problem...

Anyway, perhaps this could help generate a per second
network traffic which could keep the connection alive....

I have yet to prove though...

;-)

Francois



>-----Original Message-----
>Please help!
>
>i have remote windows 98 clients running RDP client
connecting to a windows 2000 terminal server. The terminal
server is within a windows NT domain. The clients can
connect to the terminal server without any problems.
However, as soon as the terminal session is minimized and
runs in the backgroud, the session is dropped within
minutes.
>
>The connection configuration is set as follows;
>
>1. End a disconnected session - 2 hrs
>2. Active session limit - 3 hrs
>3. Idle session limite - 3 hrs
>
>The following registry settings have also been modified;
>
>4. HKLM\System\current control set\control\terminal
server\KeepaliveEnable is set it to 1
>5. Both keepAlivetime and KeepAliveInterval under TCP/IP
parameters in the registry have also been changed.
>6.
HKLM\System\CurrentControlSet\Services\Tcpip\parameter\TcpM
axDataRetransmissions has been changed to 10
>
>The remote users are connecting to the terminal server
via DSL, private WAN. Does anyone have any idea why this
is happening? Your help will be much appreciated
>
>
>
>
>.
>

What you try to do with a clock is exactly what the KeepAlive
registry entry does. It sends a heartbeat every second (by
default, you can change this), to prevent sessions from being
disconnected because the router sees no traffic.
Have you enabled KeepAlives?
Here are the details:

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

Unfortunately, this won't help the original poster Carol, since
she already did this.

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

<(E-Mail Removed)> wrote in news:152d101c4460f
$f4be1c10$(E-Mail Removed):

> Carol,
>
>
> I am (desperatly) looking for a clock (tiny - digital)
> that will launch with an "Always On Top" option and
> refresh itself every single second... I believe this could
> perhaps be sufficient network traffic to keep the
> connection from stopping.... However, I have not been
> able to find a clock that does NOT have a systray
> reference.... An issue for me as the TS users do not have
> systray visible (GPO) and all clocks I have found created
> a mem or systray failure (as systray is not there and
> somehow the clock icon is looking for the taskbar without
> success.... [see softwaremaniacs.com's DeskClock for an
> example of what I am talking about] .... could work
> perfectly.... but the systray ref for me is a problem...
>
> Anyway, perhaps this could help generate a per second
> network traffic which could keep the connection alive....
>
> I have yet to prove though...
>
> ;-)
>
> Francois
>
>
>
>>-----Original Message-----
>>Please help!
>>
>>i have remote windows 98 clients running RDP client
> connecting to a windows 2000 terminal server. The terminal
> server is within a windows NT domain. The clients can
> connect to the terminal server without any problems.
> However, as soon as the terminal session is minimized and
> runs in the backgroud, the session is dropped within
> minutes.
>>
>>The connection configuration is set as follows;
>>
>>1. End a disconnected session - 2 hrs
>>2. Active session limit - 3 hrs
>>3. Idle session limite - 3 hrs
>>
>>The following registry settings have also been modified;
>>
>>4. HKLM\System\current control set\control\terminal
> server\KeepaliveEnable is set it to 1
>>5. Both keepAlivetime and KeepAliveInterval under TCP/IP
> parameters in the registry have also been changed.
>>6.
> HKLM\System\CurrentControlSet\Services\Tcpip\parameter\TcpM
> axDataRetransmissions has been changed to 10
>>
>>The remote users are connecting to the terminal server
> via DSL, private WAN. Does anyone have any idea why this
> is happening? Your help will be much appreciated