From: Corunna, Ontario
I used to have winmx working but about 6 months ago had to rebuild my isa server. Of course when I finally got round to re-enabling winmx - it didn't work.
It appears that my older version of winmx (sorry, it was either 2.2.x or 3.2.1 (not sure which)) was trying to connect to some winmx.com servers that it couldn't resolve (find). I updated to 3.31 and the problem went away.
Anyone who tries the following setup without success should try updating to winmx 3.31 before giving up
(1)port 6699 TCP inbound, no secondaries
(2)port 6699 TCP outbound, no secondaries
(3)port 6257 UDP send/receive, no secondaries
(4)port 6257 UDP receive/send, no secondaries
allow, selected protocols, all the above ie 1 to 4.
IP Packet Filters
(5) Custom, UDP protocol, direction both, fixed local port 6257, remote port all.
(6) Custom, TCP protocol, direction both, fixed local port 6699, remote port all.
Server Publishing Rules
(7) (int ip as required), external IP default, map using rule (4) above.
(8) (int ip as required), external IP default, map using rule (1) above.
Outgoing TCP Connection - connect direct
Incomming TCP - listen on port 6699
In/out UDP - send & receive datagrams on port 6257
Host name resolution - use operating system
Network - make a primary connection
Firewall Client (probably unnecesary)
app winmx, localbindtcpports, 6699
app winmx, localbindudpports, 6257
The above works with winmx installed on a pc on a lan behind an ISA server - may need to change if running on the isa itself.
It allows primary connects, including uploads (although they seem slow - not a bad thing ).
Disable packet filter (6) to prevent uploads.
Without the UDP rules I could get a connection, but didn't receive any search responses.
Other than the last few comments I'm not sure which of these rules are mandatory and which can be omitted. You are welcome to refine...