I have just done a format and reinstall and now Outpost will not allow Mozilla to access the Internet!
I have rules set to allow access, all standard ports (80 etc, based on the standard detection of Outpost as for Mozilla when the rules dialog comes up)
But no matter what is allowed in the rules, outpost Refuses to allow Mozilla access to the world. Logs show "OUT REFUSED". I have deleted the rules and allowed Outpost to recreate them, I have recreated them manually, The only thing that works is to add it to the trusted programs section.
Has any one got any Idea what on earth is going on?
I must admit that this one has me *really* stumped.
1. Make sure the Global Rules are default.
How do you mean by this?
2. Delete your current application rule for Mozilla. Make sure there are not duplicate entries. Search the whole application list.
Done that.
3. Verify that no Blocked applications, for example svchost.exe or services.exe are at fault.
There are no blocked applications at all. I have gone as far as completly stripping out all apps that use HTTP ports, and they are fine, just to see if it was a local (Mozilla) or a global issue. It is a local issue!
4. Exit and Shutdown Outpost.
5. Delete the file called modules.ini from the directory where Outpost is installed.
I dont use the modules function, it annoys me immensly to have to wade thru hundreds of dialogs for every DLL a app calls. In the case of the MS progs this is quite a few calls!
6. Reboot the system and try it again.
I think my next bet is to start with a "Fresh" install of outpost.
thompsonmike,
Wow, I have to admit that you seem to have done your troubleshooting here. I recommend that following each of these instructions in order. Do them all:
1. Make sure the Global Rules are default.
2. Delete your current application rule for Mozilla. Make sure there are not duplicate entries. Search the whole application list.
3. Verify that no Blocked applications, for example svchost.exe or services.exe are at fault.
4. Exit and Shutdown Outpost.
5. Delete the file called modules.ini from the directory where Outpost is installed.
6. Reboot the system and try it again.
I am not sure if that will work. But, it is the only thing that I can suggest at the moment.
Keep us advised of your progress. :)
Have you tried to create a New Configuration? Of course, this may only be possible with the PRO version of Outpost
Umm, just tried that and no joy. So i uninstalled, restarted and reinstalled, restarted again. When I launched Mozilla low and behold, it worked. Outpost allowed it. I then re-loaded my old config and it worked again. I updated to the latest build of outpost, restarted (I really hate windows for that) and it worked!
I can only assume that it was a botched first install or upgrade. All working fine now. Odd odd odd.
I normally use Netscape v.7 (which is essentially the same thing as Mozilla). Not this morning!
I haven't been using a separate firewall for more than a year (since I installed Win XP). I downloaded this because a maillist friend suggested it as an ad blocker.
I installed Outpost four hours ago. I looked through the options and selected what seemed rational, given my browsing habits. Then I went online. Outpost seems to be somehow blocking me from using Netscape, :mad: as I get the following message:
The connection was refused when attempting to contact [site name].
I tried a variety of sites, but the message remained the same.
I am running the following:
Win XP Home (with ALL applicable security updates)
Netscape 7.0
Eudora Pro 3.0.3
Norton System Works 2003
MailWasher 1.32
Ad Aware 6.0
I first tried putting Outpost in disable mode. No joy. Then I decided to uninstall it. I saw the message about giving a reason for uninstalling, so I copied the URL. Completed the uninstall, restarted, and tried again to go online. I still couldn't get Netscape to work.
IE works like a charm. I HATE, LOATHE and ABHOR IE. It's ugly (minor), it doesn't have tabs (bigger), and it is SO vulnerable to various viruses, worms, etc. (killer). And MS will never, ever find all the holes. :mad:
I've tried going back and doing what was suggested to David, insofar as it appears applicable. On the first install, I did not block any apps, nor did I install any. There is no modules.ini file in the Outpost folder, nor is it in any of the sub-folders.
I did find svchost.exe in the display of blocked connections, but how did it get there?? If that's the problem, how do I fix it??
thompsonmike,
Incredible. I do not have Mozilla currently installed, but I have used it without issue in the past. This problem really has me confused.
By Default Global rules, I mainly meant to suggest that the global rules should be checked for potential conflicts. But, that was a stretch.
Have you tried to create a New Configuration? Of course, this may only be possible with the PRO version of Outpost.
Other than that, a fresh install may be the only option.
However, I have one more stretch. If you are using Windows XP, you might try deleting the files in C:WindowsPrefetch and rebooting. Again, I am reaching with this one.
 Red Hat's Rough Recovery From CFO Exit
 Windows Live Finds a New, Pre-installed Home |
HOME