FTP Library Options and Filezilla

[wilgeno]

In version 2.4 and above there used to be an option to switch FTP libraries. For the past couple of days I have been trying to resolve why BC3 cannot connect to a Filezilla server. It hangs and the connection closes on the "CLNT Beyond Compare v3.3.8" command.

To try to resolve this I reverted back to a trial version of BC2 and found that if I switched to the "Indy 9" library the connection works perfectly.

Now I went back to BC3 because that is the version my employer has licensed and this option does not exist. How do you make a FTP connection to a Filezilla server?

Thanks

[Chris]

It might help to try switching between active and passive mode FTP. BC2 defaulted to active mode, BC3 defaults to passive mode.

To change modes in BC3, select "Tools > FTP Profiles". Select the profile that matches your server. Go to the "Connection" tab. Uncheck "Use default". Uncheck "Passive transfers (PASV)" and save the changes.

If that doesn't resolve the issue, what version of Filezilla server is running on the server that you're trying to connect to?

[wilgeno]

Chris, I've tried working with every FTP setting and not this is not working. Passive vs active makes no difference.

This is Filezilla Server 0.9.41.

As I stated this problem occurs in BC2 and BC3. The only way to get around this in BC2 was to change the FTP Library. It appears that the SmartFTP Library isn't very smart.

[Zoë]

Beyond Compare 3 uses a newer version of the Indy9 library, so it has nothing to do with that. We've tested BC3 against FileZilla successfully, and I can't find anything in their documentation about blocking specific clients based on the CLNT response. I have found several references online to firewalls that drop connections if they see an FTP command they don't recognize, CLNT being one of them, and I suspect that's what's going on here. Make sure your FileZilla server is running the most recent version and see if you can connect using BC from a different location.