On Fri, Nov 24, 2006 at 08:42:34AM -0800, Scott Fletcher wrote:
> I took the liberty of downloading the Windows cURL and
> test it on my laptop. I still get this same problem.
>
> The command I issued is
>
> --snip--
> curl -v -T "file_testcase.txt" --disable-epsv
> --disable-eprt --ftp-pasv --ftp-ssl -u "***:***"
> "ftp://onlinefiletransfer.suntrust.com:20021//ARAUTOAC"
> --snip--
>
> And the response I got is below. The reason I got
> error is the incorrect connection to the 2nd IP
> address below...
>
> --snip--
> * About to connect() to
> onlinefiletransfer.suntrust.com port 20021 (#0)
> * Trying 167.181.46.51... connected
> * Connected to onlinefiletransfer.suntrust.com
> (167.181.46.51) port 20021 (#0)
[...]
> > PASV
> * Connect data stream passively
> < 227 Entering Passive Mode (10,49,53,32,78,82)
> * Trying 10.49.53.32... Timed out
> * couldn't connect to host

The host responds to the PASV ccommand with the address 10.49.53.32, so
that's what curl connects to. Since that address is an internal address
that clients cannot connect to, the server is broken.

Luckily, this brokenness is common enough that curl has an option to overcome
it: --ftp-skip-pasv-ip That tells curl to ignore what address the server
says to use and just connect to the original IP address.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved