Kerio - Windows Update

  • Thread starter Thread starter jonah
  • Start date Start date
J

jonah

I am trying Kerio 4.7

Nice firewall, only thing it won't do is allow me to connect to
Windows Automatic Updates site correctly and download updates. It does
not ask me to "allow" apps it just causes downloads to fail.

Tried V2.1.5 also with same result.

Tried Kerio who told me to enable several apps (they were already) no
good.

Anybody got a clue here? Somebody must have seen this before.

I know its the Firewalll cos all is OK when it is disabled.

TIA

Jonah
 
jonah said:
I am trying Kerio 4.7

Nice firewall, only thing it won't do is allow me to connect to
Windows Automatic Updates site correctly and download updates. It does
not ask me to "allow" apps it just causes downloads to fail.

Tried V2.1.5 also with same result.

Tried Kerio who told me to enable several apps (they were already) no
good.

Anybody got a clue here? Somebody must have seen this before.

I know its the Firewalll cos all is OK when it is disabled.

TIA

Jonah
Click to expand...

Win2k + Kerio 2.1.5 works fine with Windows Update here.

More than likely has to do with the ruleset you are using, or perhaps
the lack of a rule.

Set Kerio to "Ask me first" and temporarily disable any "block all" rule
you may have at the end of your ruleset... then try Windows Update
again. Kerio will popup with a window telling you what is asking for
access. You can create a new rule with the window, then modify it later.

Just be sure to reinstate your "block all" rule and that it is the last
rule in your ruleset.
 
Win2k + Kerio 2.1.5 works fine with Windows Update here.

More than likely has to do with the ruleset you are using, or perhaps
the lack of a rule.

Set Kerio to "Ask me first" and temporarily disable any "block all" rule
you may have at the end of your ruleset... then try Windows Update
again. Kerio will popup with a window telling you what is asking for
access. You can create a new rule with the window, then modify it later.

Just be sure to reinstate your "block all" rule and that it is the last
rule in your ruleset.
Click to expand...

Ta Joe

Jonah
 
Win2k + Kerio 2.1.5 works fine with Windows Update here.

More than likely has to do with the ruleset you are using, or perhaps
the lack of a rule.

Set Kerio to "Ask me first" and temporarily disable any "block all" rule
you may have at the end of your ruleset... then try Windows Update
again. Kerio will popup with a window telling you what is asking for
access. You can create a new rule with the window, then modify it later.

Just be sure to reinstate your "block all" rule and that it is the last
rule in your ruleset.
Click to expand...

Joe I found the offending rule/s

I don't know much about firewall rules, I am using Kerio 2.1.5 at the
moment on XP SP2.

I deleted 3 Rules as the log files pointed them out as the offenders,
I can now connect to MS Update.

I am assuming that by deleting the default rules I will be asked to
allow / deny should a incoming/outgoing package wish to connect with
no rule in place? When I got MS update to work only 1 "ask" dialogue
appeared, I deleted 3 rules so I must have ovedone a tad.

Can you confirm my assumption, if I am wrong I can re-install the
default rules and start again.

Thanks
 
jonah said:
Joe I found the offending rule/s

I don't know much about firewall rules, I am using Kerio 2.1.5 at the
moment on XP SP2.

I deleted 3 Rules as the log files pointed them out as the offenders,
I can now connect to MS Update.

I am assuming that by deleting the default rules I will be asked to
allow / deny should a incoming/outgoing package wish to connect with
no rule in place? When I got MS update to work only 1 "ask" dialogue
appeared, I deleted 3 rules so I must have ovedone a tad.

Can you confirm my assumption, if I am wrong I can re-install the
default rules and start again.

Thanks
Click to expand...

That depends.

If you have a "block all" rule at the end of your ruleset then Kerio
won't ask you anything... it will just block everything.

If you don't have a "block all" rule then Kerio will ask if it is set to
"Ask Me First".

If you don't have it I suggest setting up a "block all" rule and placing
it at the end of your ruleset.

Description: Block All
Protocol: Any
Direction: Both Directions
Address type: Any Address
Rule valid: Always
Action: Deny

This blocks any incoming/outgoing communcations that is not allowed by
one of your previous rules. With this setup, you won't see any more
windows displayed by Kerio... unless you disable the "block all" rule.

So, how to know what is trying to communicate yet being blocked?

Disable the "block all" rule and set Kerio to "Ask Me First" then engage
the program and watch your windows.
 
If you don't have it I suggest setting up a "block all" rule and placing
it at the end of your ruleset.

Description: Block All
Protocol: Any
Direction: Both Directions
Address type: Any Address
Rule valid: Always
Action: Deny
Click to expand...

Isn't that going about things the hard way? I would have thought it
much easier - and quicker - to simply to change the Kerio setup
selector from "ask me first" to "deny unknown".
 
Andrew said:
Isn't that going about things the hard way? I would have thought it
much easier - and quicker - to simply to change the Kerio setup
selector from "ask me first" to "deny unknown".
Click to expand...

I suppose I'm somewhat paranoid about having a "block all" rule. ;)

I like backups or in this case extra insurance.
 
snip

OK Joe, thanks I got it sorted now, block all rule in place and
everything that should be working is working so far.

Cheers

Jonah
 
Back
Top