webmaster @ January 5, 2009
I can only use a secondary connection with WinMX. I can connect with a primary but NOTHING can be done. No search or download so I use a secondary where everything works fine. i use outpost (of course) and WinMX was entered as a trusted app. I use router and WinMX has the correct two ports open for TCP and UDP. Anyone got some ideas?
FeivelI also used WinMX with v1 without problems, either.
I insist: do you see some blocked connections in your logs?That is a very helpful bit of info MegaHertz. Now after I add the TCP and UDP ports, will they "be open" before a reboot? I am doing a few other things on my computer so I will add those ports later and let you know how it works out but i bet it will solve my problem :)
Feivel the less confusedFeivel,
The Attack detection plug-in operates seperately from the firewall. What you may need to do is modify your protect.lst file to ignore incoming connections on that port. To do this open the protect.lst file in notepad and find the section below and edit it accordingly.
# Outpost will not count any packet to the following local ports as suspicious:
TCP 113 #Ident
TCP 13223 #PowWow Online Pager
Add your protocol & port info here
Originally posted by Feivel
That is a very helpful bit of info MegaHertz. Now after I add the TCP and UDP ports, will they "be open" before a reboot? I am doing a few other things on my computer so I will add those ports later and let you know how it works out but i bet it will solve my problem :)
Feivel the less confused All you should have to do to get the Attack Detection Plug-in to ignore them is restart Outpost. Also make sure you only add the inbound port needed.,Feivel,
It may be worth checking your Attack Detection log for incoming connection attempts. If you see any that are for WinMX (ie using the same port) then you will need to add a rule to WinMX to specifically permit such incoming traffic. While not a WinMX user myself, most P2P networks do impose penalties for users that do not share content, and this could be at the root of your problem.I added the tCP and UDP ports, shut down Outpost then restarted Outpost and now I can be downloaded from and searched but I can't search or download. I will try a reboot and see if that helps.
FeivelWinMX could care less about what users share (or don't share) but personally i hate leeches. Anyway, I did look at my attack detection log and much to my surprise there was a single entry to WinMX. That appears to be my problem but I really don't understand how there can be an attack on a port that has incoming allowed for the attacked application. I mean how much more open can I get WinMX since it is already a trusted app?
Feivel the confusedNo blocked connections. I can connect fine as a primary just can't search or be seen by anyone. Secondary works fine so I'm not sure if it's an Outpost problem. I can say I had WinMX working fine before Outpost (even with the router).
FeivelI've doing some tests with WinMX and Outpost 2 and haven't had any problem, both on primary or secondary connection (although the rules needed some work; but that shouldn't be a problem if you put WinMX in the trusted list).
Are you seeing some blocked connections on your logs?I guess i better clarify that I'm using outpost 1.
Feivel#If you have any other info about this subject , Please add it free.# |
|
edit