GlobalProtect Portal Connection Timeout when not connected to Portal

Y.Tsushima — Tue, 04 Feb 2025 10:29:27 GMT

Hello everyone,

Please tell me about the settings and expected behavior of GlobalProtect.

*I am using a Prisma Access Cloud Managed environment.

I understand that the Portal Connection Timeout can be changed in Prisma Access's Connection Behavior Settings > Portal Connection Timeout.

https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-globalprotect/globalprotect-app-settings

However, if the GP agent has never connected to the portal (if there is no cache), the timeout value is unknown because the Portal Connection Timeout value has not been obtained from Prisma Access.

1. In the above case, will the Portal Connection time out by default on the GP app side?

2. Do you know the default timeout number of seconds for GP6.3.1 in the above case?

3. If there is a portal config cache, will the gateway connection not be established using the cache until the Portal Connection Timeout time has elapsed?

For example, if I set the Portal Connection Timeout to 600 seconds, if I am unable to connect to the portal due to factors such as an unstable connection, will the gateway connection be attempted using the cache only after 600 seconds have passed?

Re: GlobalProtect Portal Connection Timeout when not connected to Portal

Vickynet — Sun, 09 Feb 2025 01:36:03 GMT

@Y.Tsushima wrote:

Hello everyone,

Please tell me about the settings and expected behavior of GlobalProtect.

*I am using a Prisma Access Cloud Managed environment.

I understand that the Portal Connection Timeout can be changed in Prisma Access's Connection Behavior Settings > Portal Connection Timeout.

https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-globalprotect/globalprotect-app-settings

However, if the GP agent has never connected to the portal (if there is no cache), the timeout value is unknown because the Portal Connection Timeout value has not been obtained from Prisma Access.

1. In the above case, will the Portal Connection time out by default on the GP app side?

2. Do you know the default timeout number of seconds for GP6.3.1 in the above case?

3. If there is a portal config cache, will the gateway connection not be established using the cache until the Portal Connection Timeout time has elapsed?

For example, if I set the Portal Connection Timeout to 600 seconds, if I am unable to connect to the portal due to factors such as an unstable connection, will the gateway connection be attempted using the cache only after 600 seconds have passed?

Hello @Y.Tsushima to give your questions a shot;

1. If the GlobalProtect (GP) agent has never connected to the portal and there is no cache, the GP app will use a default timeout value. This default timeout is typically 300 seconds (5 minutes)

2. For GlobalProtect version 6.3.1, the default timeout value remains 300 seconds (5 minutes) when the agent has not connected to the portal and there is no cache.

3. If there is a portal config cache, the gateway connection will not be established using the cache until the Portal Connection Timeout time has elapsed. So, if you set the Portal Connection Timeout to 600 seconds, the gateway connection will be attempted using the cache only after 600 seconds have passed.

I hope you above response helpful.

Thank you,

Vickynet

topic GlobalProtect Portal Connection Timeout when not connected to Portal in Prisma Access Discussions

GlobalProtect Portal Connection Timeout when not connected to Portal

Re: GlobalProtect Portal Connection Timeout when not connected to Portal