The connection to the Remote Web Workplace is frequently interrupted or lost.

Cause:  The Remote Web Workplace contains a built-in timeout feature for security reasons. When your session has been inactive for a specified period of time, you are logged off automatically. The Remote Web Workplace will timeout after 20 minutes of inactivity by default if you use the site from a public or shared computer. If the computer is not public or shared, the timeout is 120 minutes by default.

Solution:  If you would prefer the 120-minute timeout, you can access the Remote Web Workplace from a computer that is not public or shared, and clear the I'm using a public or shared computer check box on the logon page.

If you need more time, contact your network administrator. The timeout values for the Remote Web Workplace can be manually configured. However, seriously consider the security implications of a longer timeout.

Cause:  If you run a backup program or antivirus scan while remote users are connected to the network, Remote Web Workplace remote desktop sessions may be disconnected. If this occurs, the error message "An Internal Error has occurred" appears, and users are returned to the Remote Web Workplace computer selection page or log on page. At this point, users can log back on to the remote computer and resume work.

Solution:  A supported fix is available from Microsoft. For more information, see Knowledge Base article 821438 at the Microsoft Product Support Services Web site (http://go.microsoft.com/fwlink/?LinkId=19635).

noteNote
As a best practice, backups and antivirus scans should be scheduled for times when users are least likely to be logged on to a remote session.

Cause:  Certain Internet connection types, such as dial-up and PPoE connections, may be subject to timeouts due to inactivity.

Solution:  This is by design. Contact your Internet service provider if you require a longer timeout period.

Cause:  Intermittent drops in connectivity may result from wireless or faulty network connections.

Solution:  Ensure that network hardware is not resetting. See your hardware vendors documentation.

Community Additions

ADD
Show: