I have read through dozens of websites looking for some help on this, but nothing is really solving the issue at hand. We have remote connections to a Windows 2008 R2 Terminal Services server, running RemoteApp. Users at one site, connecting over Comcast, and where we have control over the network have no issue. Users connecting at a different site, where the hospital runs the network, are having issues with the RemoteApp hanging and then disconnecting. Most of the time this happens when the RDP client is not in the foreground. The latency from the hospital network to the TS server is okay, but it's definitely not as good as the Comcast latency (a more direct route).
I have tried to enable Keep-Alive packets using both Group Policy and the registry entries on the client and on the server, which was suggested on dozens of sites:
and GPO (#3):
I also tried to enable Keep Alive on the TCPIP parameters registry key as well, to no avail.
When I run Wireshark to analyze the packets going from my desktop on the LAN to the TS server, I do not see any Keep Alive packets being sent. I do see a "Continuation" packet (not at the interval specified = 1 minute but at anywhere from 30 seconds to 500 seconds), but this does not appear as a Keep Alive packet. I do see Keep Alive packets being sent from my MS SQL Server box to this TS box, at the interval requested.
Is there another way to be sure that the Keep Alive is enabled, and working properly? To me, it does not look like it is. And I cannot figure out another way to turn it on. Has anyone had this problem before? The RemoteApp is practically useless if it cannot be minimized or lose focus while checking other systems in this medical practice.
Thanks so much for any help,
Brian