cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mlajoie
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 1 of 4

Firewall Blocking

Jump to solution

We employ a whitelist, through the firewall, of applications that can communicate with our proxy server.  It works pretty well but, sometimes, we're presented with a block that looks like this:

Time:     02/18/2022 14:21:16

Event:  Traffic

IP Address:  yy.yy.yy.yy

Description: 

Path: 

Message:      Blocked Outgoing TCP  -  Source  xx.xx.xx.xx :  (27499)   Destination  yy.yy.yy.yy : http (80)

Matched Rule:  NNS Block All Access to Proxy

 

We have no idea what this phantom traffic.  Any idea on what we can do here?

1 Solution

Accepted Solutions
ktankink
Employee
Employee
Report Inappropriate Content
Message 4 of 4

Re: Firewall Blocking

Jump to solution

Hi @mlajoie When the DESCRIPTION and PATH values are <blank>, this means the network traffic is being sent through the PID0 process (System Idle).  Please contact the vendor responsible for that traffic to request a reason why the traffic being sent through PID0 vs the application executable PID number.

For PID0 traffic, application executables cannot be defined within the ENS Firewall rule and must be left blank to apply to PID0 traffic.

View solution in original post

3 Replies
pv
Employee
Employee
Report Inappropriate Content
Message 2 of 4

Re: Firewall Blocking

Jump to solution

Hi @mlajoie ,

Thank you for reaching us on community!

Matched Rule:  NNS Block All Access to Proxy - This is the rule blocking it.

User defined rule "NNS Block All Access to Proxy " is blocking the traffic on port 80. This can be fixed by allowing outbound traffic on port 80 within the rule.

Hope this helps!

Thanks 

GPV

mlajoie
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 3 of 4

Re: Firewall Blocking

Jump to solution
As I mentioned above, we only allow specific applications access to the proxy so we already have port 80 open.

The problem, in this case, is that there is no specific application (as the description and path are both blank) so it is denied.

Is the only fix, then, to allow all applications access to the proxy servers? If so, that's not a good solution for us.
ktankink
Employee
Employee
Report Inappropriate Content
Message 4 of 4

Re: Firewall Blocking

Jump to solution

Hi @mlajoie When the DESCRIPTION and PATH values are <blank>, this means the network traffic is being sent through the PID0 process (System Idle).  Please contact the vendor responsible for that traffic to request a reason why the traffic being sent through PID0 vs the application executable PID number.

For PID0 traffic, application executables cannot be defined within the ENS Firewall rule and must be left blank to apply to PID0 traffic.

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from product experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by employees.
Join the Community
Join the Community