Global Protect VPN frequently getting disconnected

[preetpk]

Hi,

We are facing issue with Global Protect VPN client connectivity for one of the user machine. Below are the details of the issue.

-> Global Protect VPN is very frequently getting disconnected

-> in Global Protect VPN connection stauts - can only see Packets Out , there are not Packets In.

In GP event logs can see "Tunnel is down due to keep-alive timeout" logs

Please let me know what can be the possible reason for GPVPN frequently disconnecting - but once connected there is no connectivity to corporate VPN over GPVPN.

Attaching the Global Protectlogs debug logs took from user n=machine during the time for issue.

Note: Issue is happening on for one user.For rest all users GPVPN is connecting fine.

[MattShuter]

fixed in 10.1.7 for some models...as noted in release notes:

"(PA-3200 Series, PA-5200 Series, and PA-5400 Series firewalls only) Fixed an issue where GlobalProtect IPSec tunnels disconnected at half the inactivity logout timer value.

[emarchetti]

We are also getting timeout errors on GlobalProtect connections after upgrading to 10.1.6-h6 on our PA-3220 happening at 45 mins with the inactivity logout set to 90 mins. Which coincides with the noted fix quoted above: "fixed in 10.1.7 for some models...as noted in release notes:

"(PA-3200 Series, PA-5200 Series, and PA-5400 Series firewalls only) Fixed an issue where GlobalProtect IPSec tunnels disconnected at half the inactivity logout timer value."

 Increased the inactivity timeout to 1200 mins as a work around. Still waiting to see if it fixes the issue. 

[amos.kee]

Hi,

We are also having auto disconnection issue which happened to 25 of our workstation in office, is there a solution?

Thanks

[OtakarKlier]

Hello,

While I do not know of a solution, this is from another vendors recommendations:

• Disable all IPv6 on the client
• Connect with patch cable and not WiFi
• Reboot 'home' internet routers
• Patch 'home' internet routers

Hope one of these might help.

[MattShuter]

What OS version are you running on your firewall?   The issue was reportedly fixed in 10.1.7 for various models.

   Prior to that, a shutdown/power off of the firewall resolved the issue, as recommended by support.    *NOT a reboot*

As noted, if that is not possible to upgrade or pull the power at this time, you could increase the timeout period to double what is needed.