Hi, I have a client that is very frustrated about Remote web workplace disconnecting after 10-15minutes. I have many other clients with SBS 2003 that can remote desktop for hours without disconnecting. I ahve followed other troubleshoot like checking off public shared computer when logging in. I have also checked registry keys for private timeout they are all set to 2 hours. Could it be an update conflicting. How can I get through this. I have also checked other time out period in IIS, ASP and other all set to 2 hours or more. Need help.Sung

Have you looked at the power management setting for the NIC in the computer? Uncheck the "allow computer to turn off"-box if it's applicable.Technet Forums Moderator | Solution Specialist | Ask The Experts IT-forum

Based on my experience, disconnection issues are usually caused by the following reasons. - The network connection is not stable. - Some routers between your client and server have idle time limitation. - Terminal server has configured to disconnect an idle session after a specified period of time. Please perform the following suggestions to see whether they can be of assistance: Suggestion 1 --------------- Because terminal service is such a low bandwidth protocol, when a user is idle or some network packets are lost, some network devices will interpret a connection that is in the idle state for an extended period of time to be a dead connection, and thus will terminate the socket. However, when the user comes out of the idle state, the terminal services client can no longer contact the terminal server because the socket is dead. Please follow the steps described in the following Microsoft Knowledge Base article to configure the [Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Keep-Alive Connections] group policy on all host computers that a remote client connects to: 216783 You cannot completely disconnect a Terminal Server connection http://support.microsoft.com/default.aspx?scid=kb;EN-US;216783 In addition, I suggest that you set the [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TerminalServer\KeepAliveInterval] registry value to 1 on the terminal server. In the system, we have a Keep Alive thread that "wakes up" every (KeepAliveInterval/# sessions) interval (adjusts each time with number of sessions), finds a session, and then polls it. One session is polled each time the thread "wakes up". The default KeepAliveInterval is 4 minutes. Let us set it to 1 minute so that the disconnected session can be recognized soon. After this, please restart the terminal server to test again. This method can help us to alleviate the issue. - Add the following DWORD values and modify them to a value of 1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TerminalServer\KeepAliveInterval - The server must be rebooted after this change. Suggestion 2 ---------------- Please check your router to see whether there are any idle timeout settings. If so, please disable it or increase the timeout. You may also enable the clock on the taskbar in the terminal session to test whether this problem continues. This will make sure at least one update is sent every minute to keep the session alive. As this issue is related to terminal service, I suggest that you post to the Terminal Service forum if the problem continues so that the problem can be resolved successfully: http://forums.technet.microsoft.com/en-US/winserverTS/threads/