Connection Blocked After Timeout TeamViewer Free: Resolving the Authentication Issue with Cisco Web Security Appliance

When using TeamViewer, a popular remote desktop software, you may encounter an issue where the connection is blocked after timeout due to authentication requirements from the Cisco Web Security Appliance (WSA). This problem arises when the WSA is configured to use cookies as surrogates in identities and the TeamViewer application does not provide domain credentials.

In explicit mode, using a PAC file or browser proxy settings, it is crucial to ensure that the 'Apply same surrogate settings to explicit forward requests' option is checked. This setting ensures that the client's credentials are cached for a period equal to Surrogate Timeout (default = 1 hour) once they access any website(s) using their browser.

However, if WSA is configured to use cookies as surrogates in identities, the authentication exemption is required. The TeamViewer Agents do not work with authentication, and when the WSA requests authentication from the TeamViewer application, the application may not provide domain credentials. As a result, the TeamViewer Agent times out and access logs show entries containing 401 or 407 errors indicating 'Proxy Authentication Required.'

To resolve this issue, it is necessary to exclude the TeamViewer connection from authentication. This can be achieved by configuring WSA to bypass authentication for specific URLs or domains associated with TeamViewer. Alternatively, you can disable authentication altogether if your organization does not require it.

In conclusion, the connection blocked after timeout issue with TeamViewer and Cisco Web Security Appliance is caused by the incompatibility of the two systems. By understanding the underlying causes and implementing necessary configurations, administrators can resolve this problem and ensure seamless communication between the two applications.

Connection blocked after timeout teamviewer free