Outpost fails to work in Rules mode but I can't see why
January 5th, 2009The rule set I am using is exactly the same as a friend of mine uses successfully on their PC. They use Broadband and I have Wannadoo dialup and I know that there are no ISP specific references to IP addresses in the rules. The problem is, that on my PC, I cannot use anything that accesses the internet, eg MSN Messenger, Internet Explorer or Outlook Express. If I change to "Allow most" mode, all is fine.
The only references I see in the log are related to SVCHost or SYSTEM and if I change both of these to "trusted", it makes no difference so I've ruled those out as the problem.
My ISP is Wannadoo and it is configured to use a proxy server on port 8080 for FTP and HTTP. Do I need to add a rule to cover this (If so, what and where?)? or am I barking up the wrong tree?
The fact that I'm getting nothing to work in rules mode tells me that there is a rule that's blocking everything but there are no log entries that help me find out what. I further assume that the fact nothing works means that the problem is either a global rule or SVCHost / System, which as I said above, I hope I proved are not the culprits.
If anyone can help with this, I'd be grateful as it is frustrating
Thanks in advance
If you are using your friend's config file file, did you try to install OP from scratch and build your own rules?
I also reinstalled Outpost and used the rules that it generates. The result is the same.
me
P.S I dont think you need to use the proxy either.When i used freeserve on dialup i didnt notice any great improvement using the cache , so i just used port 80 with no proxy for my internet settings.
try 'New configuration' from Outposts' File -menu and see if it makes
any difference. Remember to save created configuration on a different
name (I guess OP does it automatically), so you can revert back if needed.
#If you have any other info about this subject , Please add it free.# |
Posted in dballastages.com | edit