FYI:

This is why I use the Vista Firewall Control utility:

From http://reviews.cnet.com/4520-3513_7-6690672-1.html
"Outbound protection is.where?
In an e-mail, Rowan Trollope, Vice President of Consumer Engineering at
Symantec, offered this interpretation: "We have discovered that though
Vista's outbound firewall is 'on' by default, all outbound connects that do
not match a rule are allowed. In the default configuration, there are no
outbound 'block' rules, only allow rules. In other words, even though [the
Windows Firewall outbound protection is] on, it is not doing anything."

"CZ" <(E-Mail Removed)> wrote

> FYI:
>
> This is why I use the Vista Firewall Control utility:
>
> From http://reviews.cnet.com/4520-3513_7-6690672-1.html
> "Outbound protection is.where?
> In an e-mail, Rowan Trollope, Vice President of Consumer Engineering at
> Symantec, offered this interpretation: "We have discovered that though
> Vista's outbound firewall is 'on' by default, all outbound connects that
> do not match a rule are allowed. In the default configuration, there are
> no outbound 'block' rules, only allow rules. In other words, even though
> [the Windows Firewall outbound protection is] on, it is not doing
> anything."

But it can be configured. You can change the default to disallow all
outbound, and then make rules for what to allow. VFC caused a process to
continuously read a file in the \wfp\ subfolder of \system32 when it was
running. I had to disable it.

--
Rock [MS-MVP User/Shell]