kelepe

Hello, shown policy is applied on clients tried to receive VNC connection on port 5900? If so, it is not correctly configured, because you should open port 5900 on local port as your direction is IN, and remote port use any, or ephemeral ports. On your server open OUT communication on port 5900 as remote port. Make sure your profile "Qualsiasi" is correctly applied. If you want to debug, make rule that enable communication on port 5900 - direction IN, enable logging (level warning), put it in front of your rules and see your communication what you should enable. YOu can post screen of that log, that we can help you out...

I have just tested to use only EP10 mirror folder, and also detection engine has updated. So I was misled with the structure from EP9. My bad.

Thank you Marcos. I have just double checked our cmd, pretty much the same, except we do not explude ep9 product. EP9 mirror structure \mirror\eset_upd\ep9\dll\update.ver (all dll.nup files) and \mirror\eset_upd\ep9\update.ver (all engine updates *.nup). EP10 folder structure \mirror\eset_upd\ep10\dll\update.ver (all dll.nup files) not \mirror\eset_upd\ep10\update.ver and therefore no *.nup files.... Running Mirror tool v1.0.1560.0 on differernt computers, none of them give me \mirror\eset_upd\ep10\update.ver. Or am i missing something???

Marcos, what version of Mirror toll are you using? Or can you post cmd what are you using. In our case only EP9 folder has nup files for Detection engine. EP 10 folder has only DLL folder , and dll.nup files....

Same problem. Using offline update via Mirror tool. In our case , we did not receive FW module updates. Why, because updates via Mirror tool for EP10 has only DLL folder, and not detection engine updates. So we were using EP9 folder for offline updates... Please can you repair EP10 structure created by Mirror tool, also include engine updates? THank you. As workaround we copy DLL folder from EP10 to EP9 and FW modules for v10 endpoints has updated, and all FW rules are working...