Core FTP

The server is fine, because when I switched back to 1853 it connects. When I use 1881, I get the time out error. I switched to a different ftp client, and can connect just fine as well. Just weird that 1881 doesn't like their server, and 1853 doesn't like SHA1 encryption.

1881 didn't like their ftp server at all. Regardless of the SHA1 setting, it would just come back as: FTP connection error - Connection timed out Can't establish connection - [ftp address] @ [date] At least with 1853, I could connect when SHA1 was disabled. And when SHA1 was enable, it just failed t...

We use CoreFtp v.1853 to connect to a customer sftp server. Everything was working fine until they updated their server software (secure transport) that required them to enable their SHA settings. In doing so, we lost our connection ability and received the error: Failed to read binary packet data! ...