If necessary, Citrix session reliability (also known as Citrix CGP 'Common Gateway Protocol') can be enabled by IBM Cloud. Therefore, the network session for 'inactive' sessions can be lost/dropped in as little as 2 minutes. This time can be longer than some corporate firewall inactivity timeouts (for example 90 seconds).If one of these heartbeats is lost (for example, because of an unreliable network) then the time between heartbeats will be a minimum of 120 seconds. This causes a 'heartbeat' network connection ('ping' between the client device and the Citrix server) to occur every 60 seconds.The IPS can drop the packets.īy default, Citrix systems typically have ICAKeepAlives enabled but 'session reliability' disabled. Scenario #2 - Corporate Firewall intermittently blocking network connectionįor example, there may be an Intrusion Prevention System (IPS) enabled on the firewall.In some scenarios, this time-frame it too short. This meant that if there was no network communication for 90 seconds, then the firewall would kill the connection. In one real-life (IBM Cloud) customer example, the customer's corporate (on-premise) firewall had a TCP timeout set to 90 seconds. Scenario #1 - Network appliance (for example firewall) TCP timeout setting too restrictive.There are many possible causes for this network interruption, for example: The network connection (between the end user's PC and the Citrix server) has had an interruption (typically a temporary disconnection).
0 kommentar(er)
