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 pdasari
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About pdasari
10-08-2020
1Post
0Likes
0Solutions
Oct 08, 2020Last Visited
User
Activity
User
Profile
Latest posts by pdasari
| Subject | Views | Posted |
|---|---|---|
| 1706 | 04-02-2020 10:50 PM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 2 Likes |
User Badges
Community Statistics
| Member Since | 06-21-2017 01:24 PM |
| Date Last Visited | 10-08-2020 03:30 PM |
| Posts | 1 |
04-02-2020
10:50 PM
@Mick.Ball I like it how you said 4hrs or 8hrs is safer bet.We use WMI probing.The current timeout we have now set is 10hrs. The probe time is set to 20min. At our company as all of has work from home situation users are jumping on and off the VPN to avoid latency with Zoom/Webex or bypass the FW rules or whatever. Because of this, the IP addresses becomes free and the new user logging onto Pulse gets them.The firewall hasn't reached its 10hour period and the new user gets the old user's User ID and the new user happened to be an executive and gets the block page. What is the ideal way to resolve such issues when the IPs are so frequently changed, default of 45min? But what happens if something chnages in that 45min time period? Is there more real time information for firewall somehow?
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks