"Daniel Crichton" <(E-Mail Removed)> wrote in message
news:3f4224c2$0$12640$(E-Mail Removed). ..
> Daniel Crichton <(E-Mail Removed)> wrote:
> > Ian Gibbons <(E-Mail Removed)> wrote:
> >> As per subject, I have a problem with it blocking access to anything
> >> in the .microsoft.com domain, which being an XP user is a huge
> >> disadvantage as I cant access Windows Update, MSN Messenger etc..
> >
> > Has this just started happening? I've been dealing with someone on
> > IRC who can't get to the Windows Update sites (even
> > v4.windowsupdate.microsoft.com) and it appears that his ISP has a
> > different IP for that host than the rest of us do. It might be to do
> > with microsoft.com having just undergone a huge move to Akamai web
> > caching hosts for their hosts, and blocked direct access to their IIS
> > servers. Some ISPs DNS ignore the timeout values in the SOA records
> > and stick to their own ... it could be days or even weeks before this
> > gets resolved for you.
>
> And after reading the OP again, I notice you say it works if ZA is
disabled.
> Hmm. How about ZA caching old DNS responses, so when it's running it's
> trying to get at the old pre-Akamai hosts for the microsoft.com domain?
>
> Dan
>
>
Dont think it was that, if definately seemed to be an issue with ZA's true
vector monitor service.
Eitherway I found a far better firewall called Kerio (mentioned in another
thread) which does pretty much the same thing and uses md5 hashes for
protecting against program impersonation. GRC's leaktest cant connect
through it, and I show up full stealth on the test page, so I guess all's
well

Also it has a more specific rules list, which I find quite handy.
If anyone knows of a url for a real security test (free), that'd be helpful.
Ian