Re: Trouble with client connection

The server is remote from my network. I can connect to many other ftp servers including ones identifying themselves as Windows NT. I can also connect to this server using a different FTP client on the same machine through the same network connection. When I compare the connection logs between the working FTP client and Filezilla, I see the following:

Filezilla
Command: PASV
Response: 227 Entering Passive Mode (208,47,211,120,220,242).
Command: LIST
Response: 425 Can't open data connection.
Error: Failed to retrieve directory listing

WS_FTP
PASV
227 Entering Passive Mode (208,47,211,120,220,255).
connecting data channel to 208.47.211.120:220,255(56575)
Failed to connect data channel to 208.47.211.120:220,255(56575)
PORT 192,168,1,84,223,197
200 PORT command successful.
LIST
150 Opening ASCII mode data connection for /bin/ls.
transferred 136 bytes in < 0.001 seconds, 1088.000 kbps ( 136.000 kBps), transfer succeeded.
226 Transfer complete.


The difference is when the PASV command fails to connect the data channel a PORT command is sent with the local IP of the client machine. After the PORT command is sent the client is able to work normally. Is there a way to get Filezilla to mimick this behavior? Or is there a workaround for this. Again, this only happens for this one FTP server that is at a vendor site.

A follow up to this. I put the client in active mode and it appears to work. I tried this previously but it apparently did not get saved. Now Filezilla will send the PORT command and can transfer files. So my new question is can Filezilla do this automatically when the default (Passive) connection method does not work can it switch to Active mode (Like ws_ftp)?