Francesco Della Morte

Hi Kelepe, we actually realized the mistake. Changing port 5900 from remote to local now everything works fine. Thanks so much for the support!

Hi Marcos, attached you can find logs extracted from ESET Log Collector from my PC. Thank you in advance ees_logs.zip

Hi all, I work as System Administrator in a small enterprise where we use ESET Endpoint Security for Windows centralized with an ESET Protect Cloud UI where we configure rules and criteria. Since yesterday we're encountering an issue on the Eset Firewall. We use TightVNC Server installed on all Windows clients and listening on port 5900 in order to connect and support our colleagues, but the rule is no longer working correctly. I verified on some clients and, temporarily disabling ESET Firewall, I'm able to connect through VNC, as soon as I enable again it, the connection stops working. We did NOT change any rule on the Protect Cloud side, so we cannot figure out why the rule is no longer working because it seems set up correctly: I verified the Trusted Zone (Area attendibile) was set correctly and it includes every IP subnet we actually use at work. Could you help me facing up this very annoying issue? It is preventing us to connect to other clients that need support. I'm fully open to every suggestion. Thanks in advance