Search

GlobalSCAPE Knowledge Base

SFTP21 error = #0 (The file being transferred in ASCII mode appears to be a Binary file. Proceed anyway?)

CuteFTP

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • CuteFTP Pro®, v8.3.2 and earlier 
  • If you are using CuteFTP 8.3.3 or later, see related KB article ID 10606.

SYMPTOMS

When attempting a connection using the SFTP protocol, the following error is encountered:

STATUS:>   Getting listing ""...

STATUS:>   Initializing SFTP21 module...

STATUS:>   Connecting to SFTP server... 192.168.20.135:22 (ip = 192.168.20.135)...

ERROR:>     The file being transferred in ASCII mode appears to be a Binary file. Proceed anyway?

ERROR:>     Can't connect to 192.168.20.135:22. SFTP21 error = #0.

STATUS:>   SFTP21 connection closed.

CAUSE

This error is the result of a timeout of an SFTP operation.  The first line of error text is irrelevant and should be disregarded.  There are two known possible causes for this error:

  1. This problem may be caused by a misconfigured firewall.
  2. This is a known problem when using CuteFTP versions 8.0.0 through 8.0.7 and attempting an SFTP connection to a server computer running Titan FTP Server.  This issue was fixed in CuteFTP 8.1.
  3. Also see related SFTP21 error = #0. 0

RESOLUTION

  1. Check the firewall settings and ensure that port 22 is open and enabled for SFTP transfers.
  2. If you are connecting with a server computer running Titan FTP Server, update to CuteFTP 8.1 or greater.
Details
Last Modified: 8 Years Ago
Last Modified By: GlobalSCAPE 5
Type: ERRMSG
Rated 1 star based on 23 votes.
Article has been viewed 27K times.
Options
Also In This Category