Troubleshooting 

F

AILED TO ESTABLISH DATA SOCKET

This error usually occurs when trying to connect in PASV mode to a site that only accepts 

PORT mode connections. Change the connection type from PASV mode to PORT mode to 

connect to the site.  

To switch from PASV to PORT mode  

1. In 

the 

Site Manager, select the problem site. 

2.  From the menu, choose File > Properties.  

3. Select 

the 

Type tab.  

4. In 

the 

Data connection type list, select Use PORT. 

5. Select OK. 

S

OCKET 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.  

Firewall and AV Software 

Outgoing connections can be affected by the presence of firewall or anti virus software on 

the local computer or network connection.  Either one may be blocking the ports needed to 

make a successful FTP connection to the remote 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 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. 

Technical reasons for 1006x errors 

WSAETIMEDOUT (10060) 

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. 

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). 

247