UrbanViking
IS-IT--Management
I am having an issue with Terminal Services on Server 2000. We have an off site location that connects to an application server in our noc over a VPN.
They can connect fine and the Remote Desktop session seems stable, but when they leave it idle for even a few minutes sometimes the connection drops.
This wouldn't be a big problem, but they are not able to reconnect to the dropped session, and the software they are using (Quickbooks) requires a login to access the company files. This means that since the program is still running on the server Quickbooks says they are allready accessing the file and doesn't allow them to open another copy. The only way to resolve the problem is to log off the dropped session from within TS Manager.
We tried setting TS to end a dissconnected session after 1 minute, but it won't ever end the disconnected sessions and you have to do it manually. I also tried making some registry changes on the TS so it sends a "heartbeat" (KeepAlive) to Remote Desktop sessions every few seconds to keep them from being "idle". We also decreased the KeepAlive interval.
The registry changes seemed to make the drops less frequent, but they still happen.
My question is this; is there a way to force a user to reconnect to their last session if it is still running, and if anyone has anymore tips to avoid the idle timeout problem. Thanks
They can connect fine and the Remote Desktop session seems stable, but when they leave it idle for even a few minutes sometimes the connection drops.
This wouldn't be a big problem, but they are not able to reconnect to the dropped session, and the software they are using (Quickbooks) requires a login to access the company files. This means that since the program is still running on the server Quickbooks says they are allready accessing the file and doesn't allow them to open another copy. The only way to resolve the problem is to log off the dropped session from within TS Manager.
We tried setting TS to end a dissconnected session after 1 minute, but it won't ever end the disconnected sessions and you have to do it manually. I also tried making some registry changes on the TS so it sends a "heartbeat" (KeepAlive) to Remote Desktop sessions every few seconds to keep them from being "idle". We also decreased the KeepAlive interval.
The registry changes seemed to make the drops less frequent, but they still happen.
My question is this; is there a way to force a user to reconnect to their last session if it is still running, and if anyone has anymore tips to avoid the idle timeout problem. Thanks