Welcome to ! ???

  • I started my computer this evening, and Agnitum Outpost Firewall Pro 2.1 first presented me with a messagebox saying nothing but "tcp". When I loaded up the main interface, the only options in the menu on the left are:

    My Internet
    + - Allowed
    + - Blocked
    Plug-Ins

    And in the main scree on the right I have:


    Wlecome to !

    Thanks for using , the comprehensive solution for protecting you and your family online.

    No lengthy configuration is needed. starts protecting you against all kinds of attacks as soon as it is installed.

    Thanks for choosing as your security provider!

    None of the options work and messageboxes like the one I described above constantly pop up across the screen every time I attempt to do something. I tried to uninstall and then reinstall, but the uninstaller quits on "INVALID INSTALL.LOG"

    -- Update --

    After a couple of hours of fiddling, I eventually managed to uninstall Agnitum. I reinstalled it, but then I received another problem - Agnitum works, but it then disables the TCP/IP services. When the computer first starts, Norton AntiVirus springs up about 100 message boxes with the title "Email Proxy", and any Internet Connections do not work. I checked the services, and the 'Windows Firewall/Internet Connection Sharing' service was disabled due to the error of dependance on TCP/IP, which reported Error 2: The System cannot find the specified file.

    I used system restore to return to a period where I have [B]no[/B} firewall installed to use the Internet.

    It seems I can have either the Internet without Agnitum, or Agnitum without Internet - both of which are two pretty stupid options.

    Any help would be most appreciated, thankyou.
    Stephen Eyre (alsotop)


  • SP2 Release Candidate 2 works on some machine, does not work on other.
    As Microsoft stated, this release, even if it is a RC, should not be installed on production environment. You can do it but at your own risk as there is no support from Microsoft, and let's be honest you cannot expect one from Agnitum.


  • Alsotop,

    There should be an install.log file in your Outpost program files folder. Check it to see if any errors were reported during the installation.

    Another possibility, if you have been connected to the Internet without a firewall, is that your system has been compromised and changes made preventing an Outpost installation. A check with an updated anti-virus/anti-trojan scanner would be a prudent step in this case along with installing software that allows you to control which applications Windows runs (such as System Safety Monitor (http://maxcomputing.narod.ru/ssme.html?lang=en) or Process Guard (http://www.diamondcs.com.au/processguard/)).

    However, I would suggest that your SP2 build is a more likely cause of this problem.


  • I have been running the XP Service Pack 2 release candidate since it was released, and Outpost has reported no problems so far. (Is Outpost Firewall going to support the Security Center's Firewall status checker on public release?) I don't think it is the SP itself, but something else that may have affected the registry or the datafiles. I'm curently performing the steps in the link Paranoid 2000 provided. Hopefully, if the install doesn't alter my TCP/IP settings again, it should be plain sailing.

    If it does create problems, its not exactly the end of the world, since I still have access to my hard drive, it would be easy for me to backup my files to a computer on my network and perform a format and restore to factory settings.

    Thanks for your help, I will reply with the results afterwards.

    Stephen Eyre (alsotop)


  • You said it worked with others RC. I guess you mean RC1. I do know exactly the difference between RC1 and RC2 but something might have changed.
    Anyway when you install SP2 it asks to perform a backup of the system, you can at least get your backup version and avoid a reformat which is pretty hard. Maybe you even made a ghost you could use...


  • Alsotop,

    Wow, sounds like a truly messed-up install there. I would advise uninstalling and reinstalling (following the 1) but checking that you are not running anything that could interfere with the installation of a driver or service - this includes anti-virus/anti-trojan software and process protection software like Abtrusion Protector (run this in install mode) or Process Guard (disable the block on Driver/Service installs). If in doubt, please give details of the software involved.

    While your second install seems to have proceeded further, there is a good chance that whatever messed up your first one also nuked the second so I would still recommend a reinstall.

    Norton Antivirus will need an Outpost rule since it runs as a proxy server in scanning emails - it should be given the same rules as an email client. Please check 1 for more details on rules creation (while it addresses Outpost v1, most of it applies to v2 also).


  • There should be an install.log file in your Outpost program files folder. Check it to see if any errors were reported during the installation.
    During the installation, the install.log was fine, when I attempted to uninstall however, the removal program kept repeating that the install.log was either invalid, missing or corrupted. I took a look, and it wasn't to be seen, and a lot of other files that were originally there were too missing.

    Another possibility, if you have been connected to the Internet without a firewall, is that your system has been compromised and changes made preventing an Outpost installation. A check with an updated anti-virus/anti-trojan scanner would be a prudent step in this case along with installing software that allows you to control which applications Windows runs (such as System Safety Monitor or Process Guard).

    I too had presumed that some trojan may have breached my computer in a short period if my firewall had been disabled (although I can't recall ever turning it off or disabling it completely) but both Ad-Aware and Norton AntiVirus 2004 found nothing.

    However, I would suggest that your SP2 build is a more likely cause of this problem.
    You said it worked with others RC. I guess you mean RC1. I do know exactly the difference between RC1 and RC2 but something might have changed.
    When I was referring to having a release candidate of the Service Pack 2 installation on my computer, I did mean RC2 - I hadn't performed any upgrade which could have caused Outpost to stop working - I had been using RC-2 (Build 2149) for some time before it stopped working.

    avoid a reformat which is pretty hard. Maybe you even made a ghost you could use...
    I performed a reformat, and installed from my Windows XP CD (which already includes Service Pack 1) so I'm now running Windows XP Service Pack 1. Outpost Pro succesfuly installed with no major hickups, and everything seems to be performing well. It's already begun configuring for the programs I'm using, and Automatic Updates is patching my system in the background. I will try my test system with a trial copy of Agnitum on Service Pack 2 to see if I have any problems, but leave this computer, as the main gateway on Service Pack 1 for the time being.

    Thankyou very much for all your help! :D ;)

    Stephen Eyre (alsotop)


  • I know that quite a few testers reported problems with OP and several builds, 2149 in particular, I think but I can't seem to find those posts. I must not be using search right.


  • Further, XP SP-2 RC-2 is still a beta. It's very possible that this is causing the problem. Several SP-2 builds totally broke OP. A PC with this software should be a test machine and such problems expected. Your best solution might be reverting to SP-1 until SP-2 is a public release.


  • Well, it seemed even after following all the steps, twice, the Outpost Firewall continues to corrupt the TCP/IP drivers (For what reason I do not know) But the Windows Firewall/Internet Connection Sharing Service and the RPC Service keep failing to start due to dependencies on TCP/IP which reports Error 2: The System cannot find the specified file.

    I can't understand the errors, so I'm going to perform a reformat and put things back the way they were. Hopefully, I can install Outpost and finally purchase the product.

    Stephen Eyre (alsotop)


  • I'm running Outpost Pro 2.1 (Build 314) on Windows XP Home SP-2 RC-2. I have never installed Zone Alarm on this PC since it was last reformatted and restored to factory settings, and I don't have the Windows Firewall running.

    I'm using Internet Connection Sharing to allow other computers on my home network access the Internet, but this has been working fine until all of a sudden.

    Thanks again,
    Stephen Eyre.


  • I would try a scan with an actual anti-trojan software. Norton Anti-Virus and Ad-aware will not find trojan's. Try TDS-3 (Trojan Defense Suite 3) or Trojan Hunter 3 to get the best results for trojan scans.


  • alsotop, Welcome to the forum
    First off can you post what version of Outpost
    your running?
    What version of windows your running
    Do you have another firewall running also?
    Have you ever or do you now have ZA firewall?


  • I'll also check around the Microsoft Windows Beta newsgroups to see if anyone else had this problem also.







  • #If you have any other info about this subject , Please add it free.#
    Your name:
    E-mail:
    Telphone:

    Your comments:


    If you have any other info about Welcome to ! ??? , Please add it free.

    5 January 2009 | cameltoepants.com | edit