Incoming connections on private (trusted) network profile are blocked

[xwolverine 1]

in 16.1 version when your network is set to private (same as in windows) all incoming connections were allowed, unlike on public.

in 16.2.13.0 even due to the fact my network is set to private (trusted) eset firewall is still blocking all types of incoming connections, such as LPD printing service. u need to add a rule for those connections by unblocking them or doing it by yourself as well. 

is this how it is supposed to work by now or a bug? dunno

[Marcos 5,234]

Please carry on as follows:

1. Enable advanced logging under Help and support -> Technical support
2. Reboot the machine
3. Reproduce the issue
4. Stop logging
5. Collect logs with ESET Log Collector and upload the generated archive here.

[itman 1,741]

14 minutes ago, xwolverine said:

in 16.1 version when your network is set to private (same as in windows) all incoming connections were allowed, unlike on public.

On Win 10/11, the default Windows firewall profile is Public. If it was set to Private on your Windows installation, you must have set it manually some time in the past.

Open Win firewall settings and verify that the current firewall profile is Private. It may have been set to Public at Eset 16.2 update time for some unknown reason.

[Marcos 5,234]

I assume that the private network is not set up correctly in Windows. Inbound communication from is 192.168.1.54 blocked but it should be allowed in a trusted network.

Please check the Network connections and make sure your LAN is set as trusted and uses the private connection profile:

 

 

[xwolverine 1]

8 hours ago, Marcos said:

I assume that the private network is not set up correctly in Windows. Inbound communication from is 192.168.1.54 blocked but it should be allowed in a trusted network.

Please check the Network connections and make sure your LAN is set as trusted and uses the private connection profile:

 

 

i have all set to Private: windows settings,  windows firewall and eset firewall.

seems to be a bug. before i updated from 16.1 to 16.2 all was good.

on 16.2 all incoming connections are blocked even if the network is set to private, u need to add a rule for each type of connections. 

[itman 1,741]

One thing you could try is deleting your existing Eset Ethernet network connection. Upon exit from that Eset GUI section, Eset will create a new network connection. It is possible the existing network connection settings got hosed in the upgrade process.

Upon creation of the new network connection, verify that its profile shows as Private for the Eset generated connection.

Edited August 27, 2023 by itman

[demonlight 0]

On 8/27/2023 at 2:10 PM, itman said:

One thing you could try is deleting your existing Eset Ethernet network connection. Upon exit from that Eset GUI section, Eset will create a new network connection. It is possible the existing network connection settings got hosed in the upgrade process.

Upon creation of the new network connection, verify that its profile shows as Private for the Eset generated connection.

Thanks, Ill give this a try.   When you say delete, the only option I see is "Forget" under 'Network Connections' and clicking the 3 dots next to 'My Network' local domain.   Does 'Forget' do they same thing?

[itman 1,741]

14 hours ago, demonlight said:

Does 'Forget' do they same thing?

Yes. It removes the network connection.