Mar 22, 2021 The issue could also be due to Citrix Gateway configuration for Citrix Receiver Policy vs Citrix Receiver for Web. In this case, the grey, white or black screen issue could be caused due to Citrix Gateway configuration and could work without issues when connecting either from native Citrix Workspace App or via a Web browser session. You can configure Auto Client Reconnect to prompt users to reauthenticate when reconnecting to interrupted sessions. If you use both Session Reliability and Auto Client Reconnect, the two features work in sequence. Session Reliability closes, or disconnects, the user session after the amount of time you specify in Seconds to keep sessions active. 0 = do not reconnect to any existing sessions. 1 = reconnect on application launch. 2 = reconnect on application refresh. 3 = reconnect on application launch or refresh. 4 = reconnect when Receiver interface opens. 8 = reconnect on both Windows logon and power resume. 11 = combination of both 3 and 8.
Objective
This article explains how to configure Automatic Client Re-connection.
Instructions
Users can be disconnected from their sessions because of unreliable networks, highly variable network latency, or range limitations of wireless devices. With the Auto Client Reconnect feature, Receiver can detect unintended disconnections of ICA sessions and reconnect users to the affected sessions automatically. When this feature is enabled on the server, users do not have to reconnect manually to continue working. Receiver attempts to reconnect to the session until there is a successful reconnection or the user cancels the reconnection attempts.
Configure Auto Client Reconnect using the following policy settings:- Auto client reconnect. Enables or disables automatic reconnection by Receiver after a connection has been interrupted.
- Auto client reconnect authentication. Enables or disables the requirement for user authentication upon automatic reconnection
- Auto client reconnect logging. Enables or disables logging of reconnection events in the event log. Logging is disabled by default. When enabled, the server's System log captures information about successful and failed automatic reconnection events. Each server stores information about reconnection events in its own System log; the server farm does not provide a combined log of reconnection events for all servers.
Auto Client Reconnect incorporates an authentication mechanism based on encrypted user credentials. When a user initially logs on to a site, the server encrypts and stores the user credentials in memory, and creates and sends a cookie containing the encryption key to Receiver. Receiver submits the key to the server for reconnection. The server decrypts the credentials and submits them to Windows logon for authentication. When cookies expire, users must reauthenticate to reconnect to sessions.
Cookies are not used if you enable the Auto client reconnection authentication setting. Instead, users are presented with a dialog box to users requesting credentials when Receiver attempts to reconnect automatically.
Note: For maximum protection of users’ credentials and sessions, use SSL encryption for all communication between clients and the server farm.
Citrix Workspace Download
Install Citrix Workspace Windows 2010
Disable Auto Client Reconnect on Citrix Receiver for Windows by using the icaclient.adm file. For more information, see the Receiver for Windows documentation, in eDocs.
Settings for connections also affect Auto Client Reconnect.
Configure connections for Automatic Client Reconnection
By default, Auto Client Reconnect is enabled through policy settings at site level. User reauthentication is not required. However, if a server’s ICA TCP connection is configured to reset sessions with a broken communication link, automatic reconnection does not occur. Auto Client Reconnect works only if the server disconnects sessions when there is a broken or timed out connection.
In this context, the ICA TCP connection refers to a server's virtual port (rather than an actual network connection) that is used for sessions on TCP/IP networks.
By default, the ICA TCP connection on a server is set to disconnect sessions with broken or timed out connections. Disconnected sessions remain intact in system memory and are available for reconnection by Receiver.
The connection can be configured to reset, or log off, sessions with broken or timed out connections. When a session is reset, attempting to reconnect initiates a new session; rather than restoring a user to the same place in the application in use, the application is restarted.
If the server is configured to reset sessions, Auto Client Reconnect creates a new session. This process requires users to enter their credentials to log on to the server.
Automatic reconnection can fail if Receiver or the plug-in submits incorrect authentication information, which might occur during an attack or the server determines that too much time has elapsed since it detected the broken connection.
Additional Resources
Let's say that you have a session running and it gets dropped for whatever reason. If you have auto client reconnect set, when the farm is trying to reconnect:- the farm has the session marked as disconnected, and
- the user sees that the session has disconnected, and an attempt is being made to reconnect.
Citrix Workspace For Mac
If Session Reliability is in play:
- the farm has the session marked as Active and
- the screen freezes on the last frame during the attempted reconnect process, without any indication to the user.
Follow the link for more info: https://docs.citrix.com/en-us/xenapp-and-xendesktop/7/cds-manage-wrapper-rho/cds-maintain-session-activity/cds-auto-client-reconnect.html
Disclaimer