Non-standard Socks port (non-1080) unusable??

[smokinggun]

Hi:

I've moved into a new apartment complex with free broadband, except they seem to be blocking all outbound connections to port 6699.

I'm using 3.54b4 and I can connect using 1080 Socks4 proxies (with limited up/down speeds of 15~20KB/s max), but I have access to more reliable & faster non-1080 Socks servers which would be preferable.

However when I switch to non-1080 proxies, I can't seem to connect via Secondary to any backbone nodes. I've inputed the Socks with the address:port format they describe.

What's strange is using TCPView I can see that WinMX is actually trying to connect on standard port 1080 and not the assigned port!

Is this just a bug in the program?

[Bearded Blunder]

you may need to restart winmx to use a non standard port, you do for port changes in the normal way.. i can't say i've used winmx often via proxy...

you might also want to try using the new beta patch here as it is possible the complex will allow UPnP auto configuration of ports although I wouldn't place too much hope on that..  but if they do you won't be needing to use a proxy at all.

*edit* url adjusted to point to winmxgroup front page, 3.1 beta installer no longer available  BB