firewall is blocking everything

[Guest can]

hi, I recently did an update and now the firewall has started blocking the required processes

 

 

 

 

unblock button doesn't work

there it says no usable rules found. firewall running in automatic mode, no special configuration done

[Marcos 4,841]

What actual problem does it cause? If you allow the communication as a workaround, does it it work?

[Guest can]

@Marcos    almost everything is blocked. I can't even connect to the virtual machine on localhost. When I disable the firewall, the problem goes away.

 

 

 

 

antivirus even blocking its own connections?

[itman 1,595]

10 hours ago, Guest can said:

I can't even connect to the virtual machine on localhost.

Refer to this posting: https://forum.eset.com/topic/37260-issues-with-1012046-update/?do=findComment&comment=170107 for creating an outbound rule to allow all outbound network traffic for "Allow all traffic within the computer." Hopefully, that will resolve the VM network localhost connectivity issue.

As far as all the other network traffic being blocked, I suggest you remove all existing network connections that ver. 16.2 created. Upon exiting from that Eset GUI section, Eset network processing will create new network connection/s. Now test to determine full network connectivity has been resolved.

Edited August 3 by itman

[Marcos 4,841]

Please carry on as follows:

1. Enable advanced logging under Help and support -> Technical support
2. Reproduce the issue
3. Stop logging
4. Collect logs with ESET Log Collector and upload the generated archive here (only the ESET staff can access attachments).

All inbound erkn as well as localhost communication is allowed by default v16.2 rules, however, it's blocked in the policy-based mode. Couldn't it be that you are using the firewall in the policy-based mode? The messages "No usable rule found" suggest so. Switching to automatic, interactive or learning mode should resolve the issue.

[Marcos 4,841]

Please check if installing v16.1.13 from https://forum.eset.com/files/file/117-eset-security-16213/ resolves the issue.

[Guest can]

hi, with the update (16.2.13) that came this morning, the problem is solved. thank you for your help.