Hi.
After reading this in TDS FAQ:
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.
I need some help to configure TDS as a server in Outpost Pro firewall 2.1.
Security Forums :: View topic - port 8080 is still open.any suggestions?::
I changed my firewall to ZA, just to see what happened.and yep, its still open. i use outpost and it tells that kinda stuff. KDE. Back to top. tikbalang
http://www.security-forums.com/viewtopic.php?t=18678HOME |
W32.Mytob.EE@mm - Symantec Corp.::
products: Read the document: How to configure Norton AntiVirus to scan all files. on, your Windows Firewall is on and you do not need to continue with
http://www.symantec.com/security_response/print_writeup.jsp?docid=2005-061118-3634-99HOME |
Thanks for help.
Pete
Sounds like DiamondCS have "ZoneAlarm"-itis in their FAQ! "Act as a server" simply means allowing incoming connections. To do this in Outpost you could create a rule to allow anything incoming but, security-wise, you really want to restrict this as much as possible by restricting the Local Port to specified values (this is the important one for incoming connections - the Remote Port is important for outgoing).
Your best bet is to run Outpost in Rules Wizard policy and see what (if any) prompts come up for TDS.
Thanks so much for your precious help.
 Red Hat's Rough Recovery From CFO Exit
 Windows Live Finds a New, Pre-installed Home
|
How to configure TDS and Outpost firewall?