Symantec client Firewall

[Itsu]

Hello,

just installed SC, and seems to work perfectly.
One point is that on the outgoing PC (the PC which needs remote support),
i everytime have to agree to the Symantec Client Firewall popup to allow (i say "permit allways") this outgoing connection.
I would expect when saying "permit allways" the next time it "remembered" this rule, but appearently not.

When looking in the statistics of the firewall, it seems that the SC exe (winvnc) is starting from a different directory all the time, probably causing the firewall to "think" its a different programm all the time, like this

C:\Documents and Settings\Administrator\Local Settings\Temp\7zS13.tmp\winvnc.exe

and the next time

C:\Documents and Settings\Administrator\Local Settings\Temp\7zS14.tm\winvnc.exe etc.

Any solution to get this minor poblem overcome?

Regards Itsu

[poutnik]

It remembers the rule, but for full pathname, not for all files with the same filehash.
So, there is no sense for making permanent rule for one time only program.
Use permit once option, with no rule creation.

[Itsu]

OK, that makes sense
However, it will be necessary everytime when VNC SC is started to answer the Firewall popup to permit always/once?
There is no way somehow to have the firewall "understand" that this
WINVNC program is allowed ALL the time?

I ask because this is the PC my (old) father uses, and i will need to do regular remote connections to his PC to clean things up , and i want to have this remote connection procedure to be as simple as possible, so without to many popups etc.

Itsu.

[poutnik]

I understand this. For very most cases this fw behavior makes sense, but here brings troubles.

Not very familiar with symantec, using its security suite at common user level in big enterprice enviroment.

I know more FW has this problem, at least Kerio/Sunbelt 4.x and Kerio 2.x,
maybe comodo 2.4 too ( running at my home PC, socannot check now )