How to allow a program to run as a server in Outpost?

[A884126]

Hi.

I need some help to set up a program acting as a server in Outpost Pro firewall 2.1.

Thanks

PS: http://www.wilderssecurity.com/showthread.php?t=33267

[CrazyM]

Hi A884126

Allowing a program to "act as a server" is another way of saying "allowing inbound connections". First you will need to determine which protocol, application/service and local port you want to listen on, then create your rule to allow this.

Action: Allow
Protocol: TCP and/or UDP depending on what you are listening for
Direction: Inbound
Application: service or application configured to listen on selected port
Local Port: port # you have selected
Local Address: your address or Any
Remote Port: Any
Remote Address: Any

Not sure of the terminology used by Outpost but this guideline should work. You may want to condider if you want to log these connections as well.

Regards,

CrazyM

[A884126]

Thanks so much for your precious help.

This is one example of Outpost rules for TDS that I made. If it helps someone...

For example if I wanted to monitor the Netbus 2.x port I would create the following rule for tds-3.exe.

TDS-3 Netbus 2.x Monitoring
Where protocol is TCP
and Where the direction is Inbound
and Where the local port is 20034
Allow It

Now I can make one rule that allows inbound on all of the local ports I wish to monitor, but I prefer to make a seperate rule for each inbound port. It allows me to easily control inbound communications on a per port basis, and it makes for cleaner logging. More rules means more chances to make a mistake and fewer rules means less flexibility.