Rigo

Just to be clear, did you try disabling HTTP/3 traffic scanning? That was the solution for me and the other user here. Having the correct network connection profile alone is not enough. I only ask because you marked my post as the solution but Marcos' post is the actual solution.

With this profile. I am able to connect to my other devices. Is this a bad approach?

Disabling HTTP/3 traffic scanning worked! Thank you! I already had a network connection profile with the IP ranges needed so I didn't need to add an IP set but the first solution did the trick. Hopefully this works for OP as well.

I've attached my logs. I enabled advanced logs then replicated the issue as follows: - Ping w/ ESET running - No response - Disabled ESET firewall - No Response - Disabled network traffic scanner - Response! - Re-enabled ESET Firewall - Response! - Re-enabled network traffic scanner - No response Disabled logs and collected. eis_logs.zip

I am having the same exact issue. I also found that disabling "network traffic scanner" allows the ping to go through. I have 3 PC's using the same config. The 2 that are working correctly are on version 17.0.16.0, The one that is no longer working as intended is on 17.1.9.0. This definitely seems like a bug. If i manually disable all the features that "network traffic scanner" enables, I still can't ping. That option is doing more filtering behind the scenes that we don't know of.