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
Then you'll need to allow Inbound communication for the port(s) that you are going to use. For example if I wanted to monitor the Netbus 2.x port I would create the following rule for tds-3.exe.
MU Online [Archive] - GamerzPlanet - For All Your Online Gaming Needs!!::
Help to create a Mu server. How could I make MU run faster? Multi client for mu global how allow reveal port? worthwhile cheat blast!get in. Hack autoskill
http://www.gamerzplanet.net/forums/archive/index.php/f-59.htmlHOME |
Cannot Find Server::
Go to Start then Run and type in cmd, press enter. I had the exact same problem and it was a clash between Outpost firewall free and Kaspersky.
http://www.bleepingcomputer.com/forums/topic89330.htmlHOME |
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 you can make one rule that allows inbound on all of the local ports you 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.
The easiest way to do it is tom ake an rule allowing inbound communication on whatever port TDS listens on. Do you happen to know what port(s) it uses?
I have DL'd TDS-3 which features exactly are you trying to use? It appears that each utility calls up a seperate executable which is good because then we only need to allow inbound communication for the applications that need it.
Sounds a bit like the "evil port monitors" that Steve Gibson (GRC.COM) dislikes.
Unless you are looking for things that you CAN control or eliminate on your own network, opening ports for the purpose of monitoring attacks on them is a rather pointless excercise.
Got it. Thanks. I am waiting for Jooske's answer as she will know better then me.
Trying to use the sockets option.
I Use a Firewall - How should I configure TDS-3?
Your firewall probably won't allow many of the connections to reach TDS-3, so it's probably better to use TDS-3 "socketless". Sockets Configuration in TDS-3 allows you to enable/disable various sockets, but if you DO want TDS-3 to be able to interact with sockets through the firewall, you should allow TDS-3 to act as a server.
Thanks so much for your precious help.
I also posted a question for Jooske over in your thread at Wilder's.
However you could simply place Outpost in Allow Most mode and watch your logs as TDS does it's thing tro see what ports) and protocol(s) you need to allow for it.
 Red Hat's Rough Recovery From CFO Exit
 Windows Live Finds a New, Pre-installed Home
|
