In message <[EMAIL PROTECTED]>, "Barrie Selack" writes:
>PASV
>227 Entering Passive Mode (24.www.xxx.yy,253,112)
Okay, so that would mean it's not a bug in FTPClient. The FTP server
is sending back 24.www.xxx.yy as the IP address for the data connection
instead of the 207.www.xx.yy it should be sending. I couldn't see any
way in the code for FTPClient to cause a local IP to be used, so that's
consistent. Unfortunately, it means your FTP server is at fault (or
some library it depends on, maybe getsockname is buggy).
>happens much more. Just FYI, I switched the code to use edtFTPj and
>tested several times with no problems.
If edtFTPj is working, then it won't work with FTP servers that have
have multiple interfaces/IP addresses because it must not be parsing the
PASV reply.
I'm not sure how to proceed. I'm hesitant to special-case a workaround
for a buggy FTP server. Any suggestions?
daniel
-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
s a v a r e s e # In distant lands, I hear the call of my home.
software research # Yet my work is not done. My journey's just begun.
http://www.savarese.com/ # -- http://www.sleepandthetraveller.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
