The Snowman
Premium
join:2007-05-20
 ·Verizon Online DSL
| reply to Qwerky
Re: Kerio 4.2.3 packet filter rule
Having some issues are you......suggestion....could it be that both programs use the same ports ?
Check the setting in windows messenger...it's calling out for a reason.....locate the reason......update,etc.......do you have it set to start-up when windows starts....if so change that.
Why have you not just blocked messenger ? Get it over with. Un-block it when you use it only.
This is a brief comment but may give you some ideas. Find which ports each program needs......work from there. |
|
Qwerky
join:2006-05-24
Adanac
| Hello Snowman. I do thank you for the reply.
The problem is, that there is only one program, but Kerio sees it as two different programs.
In the log, Kerio shows the absolute path, and both are the identical executable file. But, Kerio describes one as 'Windows Live Messenger' and describes the other as 'Any other application' which sound to me like a default. Rules are created for a specified executable (the Windows Live Messenger app in this case); there is no way to create a rule for something called 'Any other application', nor would I want to do that, as I don't know what such a rule would then permit to access the net.
It's not set to run at startup; I start it manually each day. But it runs all day during business hours, because I need to use it for work.
Yes, it is calling out for a reason... the intended reason. But the problem is that half the time it is silently permitted by the rules which I have created for 'Windows Live Messenger', and the other half of the time Kerio requests permission for the same address which, when I permit, shows up as 'Any other application' in the log, instead of showing as Messenger.
I'm really at a loss as to why Kerio is doing this. And very disappointed that the Kerio forum was closed--there were some real Kerio experts there!
--
Mr. Qwerky - The Lone Stranger
Hi-Ho Tinfoil, Away!
|
|
anon101
@verizon.net
| Sorry I can't help any further as I don't have Kerio, but
I found this. Hope it helps:
»messenger-support.spaces.live.co···33.entry
|
|
Qwerky
join:2006-05-24
Adanac
| anon101, thanks very much for the reply and the link. I appreciate your taking the time to find it!
The screenshots in that link are accurate--that is indeed the firewall which I am using. However, the text is sadly misleading when it says that you must allow Windows Live Messenger in both the in and out directions, for both the trusted and internet zones. That site, it would seem, is just a Microsoft shill, which tells one to allow anything Microsoft wants, because Microsoft can do no wrong. Microsoft knows what's good for you, even if it isn't.
In point of fact, one need only allow the outbound direction for the internet zone only, and Messenger will sail happily along without ever a prompt. In fact, that is what I have resorted to over the last week, in lieu of what I really want, which is a packet filter rule. It is the packet filter rule that is giving the problems as described earlier in this thread. Oh how I wish the Kerio experts had not vanished.
anaon101, please don't take the above rant personally, as it was not directed at you in any way, but rather at M$. I do appreciate your taking the time to help, and don't wish to discourage you from doing so in the future 
--
Mr. Qwerky - The Lone Stranger
Hi-Ho Tinfoil, Away!
|
|
anon101
@verizon.net
| No problem. Glad to be of some help. Good luck.
PS: rants are always allowed here otherwise there would be no members.  |
|
