Socket Errors 10060, 10061, 10064, 10065

A socket error in the 10060 range is a Winsock error. It is generally caused by either outgoing connection problems or connection problems on the host end.

Outgoing connections can be affected by the presence of firewall or anti-virus software on the local computer or network connection. Either can block the ports needed to make a successful FTP connection to the remote server. For a regular FTP session, either disable the firewall or anti-virus software or configure them to allow CuteFTP to establish an FTP session over ports 20 and 21.  Consult the documentation or help file for your specific firewall or antivirus software product for instructions. Usually the manufacturer of the device or software will also have specific instructions available on their Web site. If you continue to receive the same error after insuring ports 20 and 21 are open, contact the administrator of the site you are trying to connect to.

ICON_CuteFTPNote.gif

For more error code information, refer to Knowledge Base article 10140 at http://kb.globalscape.com.

WSAETIMEDOUT (10060)

10060 is a connection-timeout error that usually appears when the client does not receive a response from the server for a specific command. This error often occurs when you try to connect in PASV mode to a server that prefers PORT for data connections. If you see an error log similar to the one below, in the Site Properties of the problem site, click the Type tab, then change the Data Connection Type to Use PORT.

COMMAND:> PASV

227 Entering Passive Mode (xxx,xx,xxx,xx,x,xxx).

COMMAND:> LIST

STATUS:> Connecting ftp data socket xxx.xx.xxx.xx:xxxx...

ERROR:> Can't connect to remote server. Socket error = #10060.

ERROR:> Failed to establish data socket.

If you still receive a 10060 error, the server may be trying to send a listing for a very large directory (with many thousands of files) causing the client to time-out while waiting. Try increasing the time-out value in the Global Options dialog box (Tools > Global Options > Transfer > Reconnect and resume in [ n ] seconds if nothing received ) to a higher value, such as 45 or 60 seconds.

  1. The connection fails due to an error or timeout.

  2. Verify that the destination IP address is correct.

  3. Increase the connection timeout threshold under Global Settings > Connection.

  4. Switch to the opposite data connection type (PASV or PORT) under Site Settings > Type tab.

  5. Verify that the problem is not local by trying to connect to an alternate server.

  6. If a server name was used, verify it resolves to the correct address.

  7. If using a local server table for server name resolution, check to see that it doesn't resolve to an obsolete address.

  8. Try pinging the address. (See Troubleshooting Tips for details.)

  9. If you are using a router, verify the router is up and running (check by pinging it and then ping an address outside of the router).

  10. Do a traceroute to the destination to verify all routers along the connection path are operational. (See Troubleshooting Tips for details.)

  11. Verify that your subnet mask is setup properly.

WSAECONNREFUSED (10061)

10061 is a Connection Refused error sent to you by the server. You could not make a connection because the target computer actively refused it. The most common cause is an incorrectly configured server, full server, or incorrect Port specified by the client.

To change your connection Port for an FTP site

  1. Open the Site Manager, then click the site.

  2. On the main menu, click File > Properties.

  3. Click the Type tab.

  4. In the Port box, type the correct port number.

Sometimes a 10061 error is caused by either a firewall or anti-virus software presence on the local computer or network connection.  Either one may be blocking the ports needed to make a successful FTP connection to the server.

For a regular FTP session, please either disable the firewall or anti-virus software or configure it to allow CuteFTP to establish an FTP session over ports 20 and 21. Please consult the documentation or help file for your specific firewall or antivirus software product for further instructions. Usually, the manufacturer of the device or software has specific instructions available on their Web site.

If you continue to receive the same error after insuring ports 20 and 21 are open, please contact the administrator of the site where you are trying to connect.

  1. The remote host actively refused the attempt to connect to it.

  2. Verify that the destination server name or IP address is correct

  3. Verify that the connection port number is correct (under Site Settings > Type tab).

  4. The remote server may be temporarily or permanently inaccessible (try again later).

  5. Verify that you have chosen the right protocol (SSH2, SSL, FTP, etc.) and have setup all required options for that protocol.

  6. Verify that the destination IP address and port numbers are correct.

  7. The remote server may be refusing multiple connections from the same client. Try using only one connection thread when connecting to this particular server (Site Settings > Options).

  8. Try pinging the address.

  9. If you are using a router, verify the router is up and running (check by pinging it and then ping an address outside of the router).

  10. Do a traceroute to the destination to verify all routers along the connection path are operational.

  11. Verify that your subnet mask is setup properly.

WSAESERVERDOWN (10064)

WSAESERVERUNREACH (10065)