This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About nate1
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About nate1
06-23-2022
2Posts
1Like
0Solutions
Jun 23, 2022Last Visited
User
Activity
User
Profile
Latest posts by nate1
| Subject | Views | Posted |
|---|---|---|
| 1749 | 06-23-2022 12:55 PM | |
| 1881 | 05-24-2022 09:34 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 05-24-2022 09:34 AM |
User Badges
Community Statistics
| Member Since | 11-04-2016 11:56 AM |
| Date Last Visited | 06-23-2022 04:16 PM |
| Posts | 2 |
| Total Likes Received | 1 |
06-23-2022
12:55 PM
You have to modify the global protect gateway idle timeout to however long you want them to stay connected as a work around until Palo fixes the bug. Otherwise since it doesn't correctly detect the keepalives it will disconnect as soon as it hits the idle timeout.
... View more
- Tags:
- workaround solution
05-24-2022
09:34 AM
1 Kudo
We had this issue come up with a brand new 3410 running 10.2.1 and found a work-around. The issue is either caused by the keepalives not being sent correctly or not being detected correctly. This was causing every vpn user's connection to reset every 10min, you can imagine how happy they were. We found out is was because the gateway idle timer was set to 10min. Even though the connections were active and passing a lot of traffic the keepalives weren't being detected. We changed the idle timer to 24hrs and it fixed it as a work around. Palo support still hasn't provided any solution for this.
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
06-23-2022
04:16 PM
|
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks