Rules error

Discussion in 'other firewalls' started by PCJohn, Mar 27, 2006.

Thread Status:
Not open for further replies.
  1. PCJohn

    PCJohn Registered Member

    Joined:
    Feb 5, 2006
    Posts:
    101
    I tried the Filseclab firewall yesterday and it shut down after after a few minutes because of one error in the firewall rules. This problem occured before with Outpost free.
    Are they just bad firewalls or is there another problem that i am not aware of?
     
  2. trickyricky

    trickyricky Registered Member

    Joined:
    Mar 27, 2005
    Posts:
    475
    Location:
    London, UK
    They are both very good firewalls, so what you've seen is unusual. What was the specific error message you got with each one? Did you create any rules of your own or were you just running with the default set coupled with learning mode?
     
  3. PCJohn

    PCJohn Registered Member

    Joined:
    Feb 5, 2006
    Posts:
    101
    The Filseclab firewall shut down after i launched firefox and i was figuring out how this firewall works.
    I think there was a error in the xml rules file?
    Previous there was a similair problem with Outpost but never this fast.
    Usually i use the default rules and learning mode with Outpost.
    The Filseclab firewall was set to medium.
     
  4. trickyricky

    trickyricky Registered Member

    Joined:
    Mar 27, 2005
    Posts:
    475
    Location:
    London, UK
    How strange. I've never seen such an error with either firewall before, nor with any others come to that. Have you tried asking if this is a know issue over in the relevant support forum? (http://www.outpostfirewall.com/forum/ for Outpost - I'm not sure about Filseclab's support as I've never used it myself).

    Are you on Windows XP, SP2, or something else?
     
  5. PCJohn

    PCJohn Registered Member

    Joined:
    Feb 5, 2006
    Posts:
    101
    I used Outpost for a long time.
    But this problem occurs now and then.
    Sometimes when i point the arrow on the ? to see what is happening it shutsdown suddenly.
    Also the "active content" logs are blank regularly.
    My OS is Windows 98.
     
  6. Eldar

    Eldar Registered Member

    Joined:
    Jul 12, 2004
    Posts:
    2,126
    Location:
    Vilvoorde (Belgium)
    Although I tried FilseClab myself, I never encountered that error.
    Did you reinstall FilseClab by any chance?
    Or maybe a driver from a previous firewall is loaded at startup so it creates
    conflicts with your current one. :doubt:
    You could have a look inside your startup to see if it loads something from a previous firewall.

    Also when uninstalling FilseClab, close the firewall first and run the Safemode.bat.
    Afterwards you can uninstall FilseClab completely.
    Not performing the above leads to conflicts with other firewalls. o_O
    I've contacted Tom Liu, the developer, some time ago and received a response within 3 weeks time.
    Not quite fast, but nonetheless I received the information I asked for. :)

    I hope this helps a bit. ;)
     
  7. trickyricky

    trickyricky Registered Member

    Joined:
    Mar 27, 2005
    Posts:
    475
    Location:
    London, UK
    It does indeed. Many thanks ;)
     
  8. PCJohn

    PCJohn Registered Member

    Joined:
    Feb 5, 2006
    Posts:
    101
    After all this i used a backup program and restored the pc.
    Other problems reocurred but i fixed them.
    The Filseclab firewall looks nice but it didn`t work yesterday (unfortunatly).
    I wish it did because there are not many new firewalls for W98.
    Antivir always worked fine with Outpost.
    But there must be something that causes these errors.
    Thank you for your advise.
     
  9. Eldar

    Eldar Registered Member

    Joined:
    Jul 12, 2004
    Posts:
    2,126
    Location:
    Vilvoorde (Belgium)
    My pleasure trickyricky. ;)
    I'm sure there must be a conflict somewhere or else it didn't install quite right. :doubt:
    Hope you'll find what's causing it, because it's a fine firewall.
    Good luck. ;)
     
Loading...
Thread Status:
Not open for further replies.