Hello. i have been experiencing random GlobalProtect disconnects on my home computer. I'm running Windows 10  with GlobalProtect 5.0.8 64-bit connecting back to my office's Palo Alto firewall (not 100% sure of the version). A few times a day, GlobalProtect will just disconnect on its own. I am typically running a Remote Desktop Connection from my home PC to my work PC when this happens and the RD session will freeze and disconnect as well. I started collecting logs when this happens but dont really know how to parse them. I have noticed a few things in various logs.
How would you recommend troubleshooting these disconnects. I'm not familiar enough with the firewall side of things to know how to look at any logging on that side. Is the issue with my home computer/OS/hardware/network? or is it likely something in GlobalProtect and/or Palo Alto that needs attention?
-Firstly I would go for the info in the PanGPS log on the local device.and perhaps paste more info.
also check your PC event viewer - Applications and Service Logs->Microsoft->Windows->Wlan-Autoconfig. operational to see if wifi is playing up.
the palo alto system logs @ Monitor/system may suggest why this happened. i normally see a client disconnect message but at least you then know it's not a firewall issue.
Thank you for the suggestions. Soon after i entered the request, i got stuck at work for the last three weeks and couldn't use GlobalProtect from home at all so i never got around to trying your suggestions. I'm finally home for the weekend and will look for those logs you mentioned and will paste them here after my next disconnect.
Did you ever find a solution to this issue? We are having the same issue. GP works great, but RDP sessions to internal PCs freeze, causing you to have to close the session and RDP back into the machine. Sometimes it happens once a day, sometimes it happens several times an hour. We are running 9.0.7 and GP 5.1.1. We did not have this happen on our old SonicWall SMA410 and NetExtender. It's was definitely introduced along with our Palo deployment 2 weeks ago.
If anyone has a solution to this issue, can you please post it?
I was getting frequent disconnect issues in GP 5.1.1 version, please confirm whether 5.1.3 version is recommended to upgrade, cause this version also has a lot of known issues.\
Fixed an issue where, when the GlobalProtect app was installed on Windows with a different language other than English (for example, Spanish), the GlobalProtect agent was continuously restarted.
Fixed an issue where, after you upgraded the GlobalProtect app from 5.0.x release to 5.1.1 release on a Mac device, users were prompted to re-enter their password even when the saved password was set to
Yes. With this fix, users will not be prompted to re-enter their password after the upgrade. For GlobalProtect to access user credentials from the login keychain, the following Keychain Pop-Up message will appear:
GlobalProtect wants to use your confidential information stored in "GlobalProtect" in your keychain.Users are prompted to enter their password and then select
Always Allowso that the Keychain Pop-Up prompt does not appear again.
Fixed an issue where, when the GlobalProtect app was installed on Windows, two OpenSSL DLL files in 64-bit were not signed by a Palo Alto Networks certificate. This issue caused a problem for some endpoint protection applications.
Fixed an issue where the GlobalProtect app for macOS was disabled and the
Disable Timeout (min)value expired, GlobalProtect could reconnect and user credentials were not preserved.
Fixed an issue where the GlobalProtect app for macOS version 5.1.1 could not be properly installed because the GlobalProtect service failed to launch.
Fixed an issue where the GlobalProtect app on macOS displayed the following error message when all the gateways were configured as
Could not connect to Gateway, Contact your IT administrator
With this fix, the app now displays the following message:
Please select a gateway to connect manually
Fixed an issue on Windows endpoints where, after the endpoint woke up from sleep mode, the GlobalProtect app was disconnected and then attempted to reconnect to the portal or gateway.
Fixed an issue where, when the GlobalProtect app was installed on macOS and Windows, cookie authentication was successful even when the wrong password was used and GlobalProtect was still connected after users sign out of the app. With this fix, authentication cookies are now deleted from the system when users sign out of the app.
Fixed an issue where, when GlobalProtect was installed using the Windows Installer (Msiexec) with on-demand as the connect method, GlobalProtect automatically tried to connect to the portal.
Fixed an issue where the GlobalProtect app displayed the customized
Captive Portal Detection Messagein the wrong format when a different language was used other than English.
Fixed a connectivity issue where, when the GlobalProtect app was installed for macOS Catalina, the GlobalProtect connection was periodically lost.
Fixed an issue where the GlobalProtect app detected the presence of a captive portal even though it was not present.
Fixed a periodic issue where the GlobalProtect tunnel failed to be restored after waking up from sleep mode. This issue occurred when on-demand was used as the connect method.
Fixed an issue where, after upgrading to GlobalProtect 5.0.6, the GlobalProtect HIP check did not detect that Symantec Endpoint Protection 14.2 real-time protection was enabled, which caused the device to fail the HIP check.
Fixed an issue where the GlobalProtect app on macOS failed to find the correct certificate for authentication to the gateway, when the object identifier (OID) was specified in the plist.
With this fix, when you provide the Key Usage OID in the plist, the GlobalProtect app uses the correct certificate.
Fixed an issue where the portal configuration selection criteria failed when the certificate was signed with the version 2 template.
Fixed an issue that caused the GlobalProtect app to install a default route with the same metric as the system default route when split-tunneling based on access route and destination domain was enabled. This issue caused some excluded traffic to go through the tunnel.
Fixed an issue where GlobalProtect failed to connect to the external gateway when the proxy was not reachable outside of the corporate network until the GlobalProtect service or the desktop was restarted.
Fixed an issue in GlobalProtect for macOS endpoints where installing or upgrading the package using a Mobile Device Management (MDM) solution such as JAMF Pro resulted in a GlobalProtect app initialization failure.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!