This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
About RobertPratt
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About RobertPratt
01-31-2023
2Posts
2Likes
0Solutions
Jan 31, 2023Last Visited
User
Activity
User
Profile
Latest posts by RobertPratt
| Subject | Views | Posted |
|---|---|---|
| 1569 | 12-22-2021 06:22 AM | |
| 2791 | 07-22-2020 01:16 PM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 12-22-2021 06:22 AM | |
| 1 Like | 07-22-2020 01:16 PM |
User Badges
Community Statistics
| Member Since | 06-25-2020 08:31 AM |
| Date Last Visited | 01-31-2023 10:23 AM |
| Posts | 2 |
| Total Likes Received | 2 |
12-22-2021
06:22 AM
1 Kudo
Hello the issue was with the fqdn. I put a catch all rule at the bottom and used ip address instead of fqdn and we havent had the issue since. Thanks.
... View more
07-22-2020
01:16 PM
1 Kudo
My company has had an issue for over a year and Palo Alto cant figure it out. We're using Azure's Palo Alto offering. * We have a security rule that is sourced from our trusted paas and destined to Azures Paas storage. Port 1433 app id: mssql db encrypted. * Multiple times a week traffic all of a sudden goes from being allowed under a specific rule to being denied without changes being made.(its being denied under interzone-default policy which of course is deny. * The only way to fix the issue is to make any change and hit commit, then the packets start hitting the rule again. * We put a fall back rule source any destination any port 1433 and any application and this still doesn't resolve the issue. * Packets hitting other rules with different ports and app id's doesn't have this issue only packets. Has anyone experienced this issue?
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks