Hello, maybe someone here can help me understand. There are two websites i'm a member of that I cannot reach. I'm getting "refused" "packet to closed port" messages using outpost firewall. All other sites are fine. Other people have checked and they can reach these sites. Thanks for your help. these two sites: http://www.gfxoasis.com/board/index.php?act=idx http://www.aero-soft.com/
Odd, I can get to those sites with no problems! I think your firewall is not set properly, ahhhh I just don't understand what's going on with your computer.
come one nadirah, I just stated above: ..and I already know it's my firewall - I just don't know how to fix it. Even if I put any browser in "trusted" it still won't connect to those sites
It appears you have a router, either your software firewall, or your router is the cause of the problem. If you do have hardware firewall it shouldn't be a big dea to drop the software firewall to test to see if it is Outpost.
Well, the fact that it is logged in my software firewall logs - wouldn't that indicate that it's Outpost? Or will a hardware block show in software logs? BTW, thanks for responding -
You just asked another question instead of testing a theory, you don't know its the software firewall, but it is the likely source.
I've been trying to edit my post for the last 5 or more minutes but got some kind of hang anyway - **edit - ok I disabled soft wall - I still cannot reach those sites. How is it my hardware is blocking only those two sites?
Are you sure Outpost is disabled? It's possible that the service is still running even though the GUI isn't perhaps? Did you set the service to disabled or manual?
I'm thinking its problem with the routers dns server, if not just relaying a bad dns entry, but I can't explain why udp 53 would come back closed from the router, if it wasn't somehow a weird problem with the outpost configuration.
Am I sure? Right click tray icon, select "Exit and shut down Outpost firewall" - apparently rules that changed suddenly to not allow 2 websites. I have DNS disabled in services and using "per application" rules
Is this problem consistent with your change to per application DNS rules? Any other blocked DNS querries showing up in your logs when you try to access these sites? For troubleshooting, try creating a global rule for DNS to your ISP's DNS servers only, any application and see if that resolves the issue. Regards, CrazyM
I'll try that. I have not had any problems until now. here is what I have set up http://img145.exs.cx/img145/975/17wz.gif - i've been using "per app" since 3 versions ago - never any problems