Knowledge Base

• CuteFTP Home (All Versions)
• CuteFTP Professional (All Versions)

During an FTP session, the following error is encountered:

ERROR:>  Can't read from control socket. Socket error = #10054.

A socket error 10054 may be the result of the remote server or some other piece of network equipment forcibly closing or resetting the connection.  In some other situations a change to the default CuteFTP connection settings may be needed for connections to this particular remote FTP server.

1. The most common cause for a socket error 10054 is the use of an invalid FTP host address.  Double-check to make sure that you are using the correct FTP host address.
   
   
2. Before making any changes to the default configuration for CuteFTP, wait and retry your connection later.  A socket error 10054 can also be caused by any of the following reasons:
• The remote server was stopped or restarted.
• The remote network interface is disabled for some reason.
• There are too many users logged on to the server.
• Your account on the remote server is restricted for some reason.
  
   
3. If this error started happening after a recent upgrade to your Web browser, (for example, after upgrading to Internet Explorer 7.0) please browse to KB Article ID 10294 for instructions.
   
   
4. If you are satisfied that the remote server or user account is not at fault, and you encountered this error either when first establishing the connection or when starting a file transfer, then it may be necessary to change the data connection type.  CuteFTP uses passive (PASV) mode by default but for this remote server you may need to use active (PORT) mode instead.
• To make the switch from PASV mode to PORT mode in CuteFTP Home, open the Site Manager and click once on the the name of the problem site on the left side of the window.  On the Type tab change the Data Connection Type to Use Port. 
• If you are using CuteFTP Professional, in the Site Manager, right-click on the name of the problem site and click Site Properties.  On the Type tab, change the Data Connection Type to Use Port.
• Note:  If changing the data connection type has no effect then you should return this setting to the default of Use global settings.
  
  
5. In some other situations, the remote FTP server may have difficulty dealing with some of the more advanced capabilities used by the default configuration of CuteFTP Professional.  In such situations, configuring CuteFTP Professional so that only one file at a time is transferred, may help.
   
   
6. If the solutions provided above do not resolve this problem then it is possible that the transfer send and receive buffer size may be set too high.  See the resolution provided in KB Article ID 10293 for further instructions.