Connected to xxx.xxx.xxx.xxx:990 on 5/15/2009 @ 1:02:09 PM < 220 zzz.org X2 WS_FTP Server 7.0(88343478) > PBSZ 0 < 200 PBSZ=0 > PROT P < 200 PRIVATE data channel protection level set > USER zzzzz < 331 Enter password > PASS zzzzz < 230 User logged in > MODE S < 200 Transfer mode set to STREAM > PWD < 257 “/” is current directory > TYPE A < 200 Transfer mode set to ASCII > PASV < 227 Entering Passive Mode (192,xxx,xxx,xxx,19,126). > LIST
Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by JJ (had 3294 views)
Just after your ftp object is created, set the UseRemoteAddress to true. (Option available in the latest versions of Xceed FTP for .Net) This will cause the address that was used to establish the initial connection to be used again for the data channel.
Otherwise, the Xceed FTP component tries to connect to the address it has received from the ftp server (shown as 192,xxx,xxx,xxx in your log) and this is the local server ip address as seen at the remote site and you can’t connect to that address. Normally, the NAT (Network Address Translation) at the other end should translate the local ip but, in this case, clearly, it does not.