On Mon, 11 Jun 2007, ·å Í¿ wrote:

> $ curl -v ftp://tf:1983026@10.132.140.23/ --socks5 10.132.140.229:1081
> --trace-ascii trace.log

[...]

> 0000: 229 Extended Passive mode OK (|||38424|)
> == Info: Trying 10.132.140.229... == Info: connected
> == Info: Connecting to 10.132.140.229 (10.132.140.229) port 1081
> == Info: Can't complete SOCKS5 connection to 9.140.140.229:38424. (1)

This shows that curl connects to the proxy (again) on the correct port (1081)
but it then fails to get a connection through that proxy to the remote site
9.140.140.229 on port 38424.

Sorry, but I don't see where curl behaves wrong here. Admittedly I'm not
fluent in socks details so perhaps there's some lurking bug in lib/socks.c.

Any chance you can debug this since you obviously see this happening all the
time?

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html