Guest steve Posted September 4, 2008 Posted September 4, 2008 Hello We have just deployed an application to our users using Windows 2003 terminal services. As far as I can tell, all of our timeout values for idle/disconnected sessions seem to be working fine. The only problem is that when users work on other applications for a while and leave the terminal app idle (for maybe 30 minutes or more), the terminal app is frozen/hung for 30 seconds or so when they return to it. For instance, they will click a menu in the terminal application and nothing will happen. If they do nothing and wait for 20 seconds or so, all the sudden the menu appears and everything works as it should. No notification from the terminal server appears for them. I've also seen this type of thing happen when I have an RDP session open to a server that I leave alone for a while and then go back to work on. Any ideas on how to fix this? Like I said, all of our terminal server session values seem to be working fine. They are all set by GPO for a maximum of one day. Regards, Steve
Recommended Posts