GlobalProtect not properly disconnecting

[Claw4609]

We have GlobalProtect configured as always-on and the option to disconnect with comment. Sometimes when a user disconnects the GP app shows as disconnected, but they are in fact still connected, they have an IP from the gateway and still route through the gateway. The only way the user can get disconnected is by connecting to a different GP portal or restarting the service. This does not happen every time but its enough to be noticed. We are running GP 6.0.5. 

Has anyone experienced anything similar/have any ideas?

[kiwi · Accepted solution]

Hi @Claw4609 ,

You might want to check to GP logs.

There's a known issue in 6.0.4 and 6.0.5 where disconnect failed with the following error:

04/25/23 15:14:02:560 ----Disable starts----
04/25/23 15:14:02:560 GlobalProtect disabling was blocked due to signature mismatch.
04/25/23 15:14:02:560 ProcessServerDisableAgent failed
04/25/23 15:14:02:560 Error processing receive data from client
04/25/23 15:14:02:560 close client socket

You might want to check the logs or confirm with support if you're hitting the same issue.  Last I heard is this should be fixed 6.1.2, 5.2.14, 6.0.6.

Kind regards,

-Kim.

[Claw4609]

We are in fact getting GlobalProtect disabling was blocked due to signature mismatch in the debug logs. I apologize, I thought I mentioned that in my original post, I did not. Thank you for the info though!

[natsuki_kurita]

Bug ID GPC-17227.
The release notes indicate that the issue has been resolved in GP App 6.0.7.