A week ago I got a bsod relating to filtnt.sys (part of outpost). And since then I can’t seem to get Internet explorer to connect to normal http sites, but it connects to secure sites.
Naturally I thought it was a firewall problem, but now having (possibly) exhausted that route, I’m starting to think it’s something to do with the ashwebsv.exe
If I remove the rules for ie and ashwebsv from outpost. When I try to access http in ie, it’s as though it can’t connect to the web. Whereas if I connect to https, it works fine, outpost pops a ‘create rule’ for https.
Why doesn’t outpost report that ashwebsv is running? And is this a known problem??
The other odd thing is that opera and firefox can connect fine, it’s just ie that’s giving me problems!
My system:
win xp pro
outpost 3.0.543.5722 (431)
avast pro 4.6
As an outpost pro 3.0 user (same build as you) I would have to say it is not a known problem (to me).
I did have a problem 2 days ago where whilst browsing I kept getting an alert window, blocking connection to the web pages I was trying to browse. On checking the logs it said it related to blocked ports, UDP and TCP, but it did show web shield was running. Web Shield was in my trusted list but web pages were still being blocked. I terminated web shield and access was restored, so I deleted the entry for web shield in OP started web shield and OP asked permission (as it should) I allowed it and all was resolved.
However, it was different for me in that it didn’t matter which browser I used all were blocked, except if I was accessing an https page, which doesn’t get monitored by web shield.
So it seems that web shield is working otherwise you wouldn’t have been able to browse with the other browsers and it may require an IE repair as Eddy suggested.
Have you had a browse of the Outpost forums and see if there is anything relating to this in the new build?
I’d rather leave the WebShield-related questions to Lukor - but regarding the bluescreens, I’ve heard of similar problems from somebody else, without any relevance to avast!. So, I’d rather say it’s a bug in the new Outpost…