Archived from groups: microsoft.public.windowsnt.terminalserver.client (
More info?)
Could well be that there is a router between your clients and your
server, which sees no traffic and decides that the session must
have ended and throws it out. The solution in that case is to
enable KeepAlives. For the correct registry key, check:
216783 - Unable to Completely Disconnect a Terminal Server
Connection
http://support.microsoft.com/?kbid=216783
Also check this link:
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 ---
"Uncle Ben" <spamfree@nospam.com> wrote on 18 mar 2005 in
microsoft.public.windowsnt.terminalserver.client:
> Idle for maybe 5 to 10 minutes.
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns96188E72BA5D1veranoesthemutforsse@207.46.248.16...
>> Does this happen when you are actually working in the session,
>> or only when the session is idle?
>>
>> --
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>
http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>> "Uncle Ben" <spamfree@nospam.com> wrote on 13 mar 2005 in
>> microsoft.public.windowsnt.terminalserver.client:
>>
>> > My "Remote Desktop Connection" gets timed out very
>> > frequently. I'm running it on WinXP SP2. Is there a way to
>> > make it not time out?
Facebook
Twitter
Instagram