Outpost Problems
Common problems and errors, their causes and solutions.
Problem: Script error 2765
Cause: Missing or damaged scripting controls
Solution: Download the latest here
Problem: VMWare virtual machines fail to access network
Cause: Outpost Firewall blocks transit packets and this prevents VMWare virtual machines from accessing the network.
Solution: If you use NAT:
- Open the Virtual Machine Control Panel.
- Click the Hardware tab.
- Select NIC 1.
- Under Connect to the following network select NAT: Used to share the host's IP address.
If in bridged mode, create the following global rule to allow traffic from the virtual machine:
Where the local host is VM_ADDRESS
Allow it
where VM_ADDRESS is your virtual machine IP address.
Problem: "Another Firewall Found" message appears at startup, but I have no other firewall installed.
Cause: Outpost can misread certain services
Solution:
- Open the Outpost.ini file from the Outpost installation folder in a plain text editor (e.g. Notepad).
- In the [Interface] section find the parameter DisableFwCheck and set it to Yes.
- Save the file and restart Outpost.
Problem: Some applications cannot access the network
Cause: The application is probably blocked by Outpost configuration
Solution: Make sure the Rules Wizard firewall policy is on. This will help you
control all the connections that are not come under any rule.
If the problem persists, go to Log Viewer > Blocked Connections. Find out what is blocked and why (the Reason column). If you do not see the Reason column, right-click the column names in the right part of the main Log Viewer window, select Reason and click OK. Modify the appropriate rule.
If this does not help either, try to disable all the Outpost Firewall plug-ins and find out what is blocked this time.
Problem: Outpost Firewall blocks The Bat! or Outlook and I cannot receive e-mail. Kaspersky AntiVirus is installed on my computer
Cause: A rule hasn't been created for both applications
Solution: Where the protocol is TCP
Where the direction is Outgoing
Where the remote host is 127.0.0.1
Where the remote port is 1110
Allow
Also, include the Kaspersky Antivirus executable (KAVMM.EXE or KAVSVC.EXE depending on the version) into the Trusted applications or create allowing rules for the executable when the Rules Wizard window appears for that application.
Problem: Outpost Firewall's icon appears in the lower right corner of the screen and after approximately one minute it disappears
Cause:Inactive icons are hidden by windows
Solution: Clear the Hide inactive icons check box in the taskbar properties window (right-click the taskbar and select Properties)
Problem: System hangs up or crashes (BSOD) Outpost Firewall and F-Secure antivirus
Cause:F-Secure antivirus contains F-Secure internet shield, which is actually a
firewall, two firewalls can cause system instability
Solution:
1. Uninstall F-Secure internet shield
2. Open Control panel
3. Double-click System
4. Select the Hardware tab
5. Select Device Manager
6. Select View > Show hidden devices
7. Find Non-Plug and Play Drivers group
8. Remove F-Secure Firewall Driver
9. Restart your computer
Important! Simply uninstalling F-Secure internet shield without removing driver will not solve the incompatibility problem as F-Secure Firewall Driver will stay active even after uninstalling F-Secure internet shield.
Problem: I cannot remotely manage a Windows XP machine with Outpost through Remote Desktop
Cause:The problem occurs only when trying to log on through Remote Desktop
under a username that is different from the username currently active
on the machine you're connecting to
Solution:
- Make sure that the account you're trying to remotely log onto has local administrative rights on the machine you're trying to connect to.
- If Outpost runs in Service mode, restart the service using the Services MMC Snap-In.
- If Outpost is running in Normal mode, then exit and shutdown the Outpost interface and service and then start the service again using the Services MMC Snap-In.
- Log on through Remote Desktop and stop the Outpost service, then start Outpost again in Application mode.
Now your Remote Desktop session is ready. After you finish working with the session, you need to restore the original Outpost service status. To do this:
Otherwise, if Outpost was first started in Normal mode, simply run outpost.exe
Problem: Outpost slows down the sending and receiving of Email
Cause: Mail servers (as well as IRC and FTP servers) traditionally try to get
your identification when you send e-mail, so they attempt to connect to
TCP port 113 on your PC. Outpost Firewall blocks this request by
default and does not let your computer reply. Most mail servers wait a
few seconds for a possible response and only then allow you to send the
e-mail.
Solution:To eliminate this delay open the Options dialog and select the System tab. Click Rules under Global System and Rawsocket Rules and select Allow inbound identification. This solves the delay problem, however please note that your port 113 will not be in "stealth" mode to any scanning sites such as www.grc.com or www.pcflank.com. To revert to stealth mode you should allow inbound identifications only to specific remote hosts that you connect to using FTP, SSH, SMTP and Telnet protocols.
Search the Agnitum Knowledgebase