About NathanFink

NathanFink · ‎01-29-2023

Found my issue and leaving this up in case it comes up in a search and their issue was the same. I was creating Service Ports and groups so quickly, that when I created the TCP-25 service I put port 25 in both the destination and source fields...so it would have only allowed traffic to port 25 if it was also originating from port 25.

NathanFink · ‎01-29-2023

Having an issue with a PA-820 that isn't recognizing standard ports and instead flagging them as unknown and blocking them as Not-Applicable even though there is a policy with service ports specified allowing them through i.e. on-prem Exchange Server. It's blocking smtp on port 25 but allowing owa/ecp on ssl port 443 with no issues. I can get the traffic to go through if I remove the service ports and instead use Application filtering and choose random applications that have the ports I need...like it knows port 25 is smtp-base because it's already in the application list and if I use that instead of service with protocol tcp port 25 it allows it through just fine. I have a 3220 at another site that is setup this exact way, just using service ports instead of Apps with ZERO issues and it recognizes the traffic as smtp port and allows it through.

Member Since	‎01-28-2023 02:43 PM
Date Last Visited	‎01-30-2023 02:25 PM
Posts	6

Online Status	Offline
Date Last Visited	‎01-30-2023 02:25 PM

About NathanFink

Re: Not recognizing standard ports like smtp. Instead showing as Not-Applicable and blocking

Not recognizing standard ports like smtp. Instead showing as Not-Applicable and blocking

Re: Not recognizing standard ports like smtp. Instead showing as Not-Applicable and blocking

Not recognizing standard ports like smtp. Instead showing as Not-Applicable and blocking