Remote Desktop disconnects when window is minimized

[Guest]

Whenever a user minimizes their Remote Desktop window, it disconnects them.
I have user connecting through Site-to-Site VPN and from home. All users
have this same issue.

Thank you,

 

[Vera Noest [MVP]]

From http://ts.veranoest.net/ts_faq.htm

Q. Remote Desktop session window won't stay minimized

A. The Remote Desktop session window keeps popping to the foreground
every five minutes when it is idle and minimized.
Solution: before minimizing the Remote Desktop session, resize the
window so it is not in full screen mode. Then the session will stay
minimized and not periodically pop up.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

There is no issue of the window popping to the foreground. This has nothing
to do with my problem. My problem is users Remote Desktop Connection has
been disconnected within 5 to 30 seconds of minimizing the RDC window.

 

[Vera Noest [MVP]]

OK, I understand.
Then it could be that there is a router between your users and your
server, which sees no traffic and drops the connection. If that's the
case, it might help if you 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
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

I also have the same problem.

As long as i have Remote Connection open in full screen, it stays connected,
if i minimize the app to check my email or whatever, my connection is lost
within 30 seconds.

I have referenced the TID's supplied with no luck, they reference making
registery edits to fields that do not exist in Windows XP.

Any other ideas

 

[Guest]

have referenced the TID's and still no luck.

TID 216783 references making registry edits to fields that do not exist.
specifically with win xp -

Windows XP and Windows Server 2003
To work around this issue, follow these steps:1. Click Start, click Run,
type gpedit.msc, and then click OK.
2. Expand Computer Configuration, expand Administrative Templates, expand
Windows Components, and then click Terminal Services.
3. In the right pane, double-click Keep-Alive Connections.
4. Click Enabled, and then click OK.
5. Close Group Policy Object Editor, click OK, and then quit Active
Directory Users and Computers.

When checking my XP config i do not have a Keep-Alive connections setting.

The other TID is completly useless pertaining to this problem.

 

[Vera Noest [MVP]]

Usually, KeepAlives are enabled on the server, not the client.

If a registry key doesn't exist, it means that your system is
running with the default value for that registry entry.
So if you want to have a non-default value, you create the key.
That's also stated on
http://terminal.servebeer.com/php/flaky_connections.php

"create or edit the DWORD value of KeepAliveEnable"
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___