[HTML9] Top Menu

 

Search

FileZilla Connection Error

First we look to the FTP common url format and check for the correct one.

FTP URL    ftp://<user>:<password>@<host>:<port>/<url-path>

There is two different mode of connection depending on server configuration
(a)    Anonymous : UserName and Password is not required.
Example :  ftp://saypoint.net/dir
ftp://ftp.saypoint.net/dir   (used in cloud networking)
(b)    Normal : UserName and Password is required and it can be mentioned in URL itself.
Example : ftp://<user>:<password>@<host>:<port>/<url-path>
ftp://user:password@saypoint.net:21/dir     unencrypted (Plain FTP)
ftpes://user:password@saypoint.net/dir    encryption in Explicit Mode.


Error:    "EAI_NODATA - No address associated with nodename"
If you see error like below:
Status:    Resolving address of ftp.saypoint.net/dir
Status:    Connection attempt failed with "EAI_NODATA - No address associated with nodename".
Error:    Could not connect to server
Status:    Waiting to retry...
Status:    Resolving address of ftp.saypoint.net/dir
Status:    Connection attempt failed with "EAI_NODATA - No address associated with nodename".
Error:    Could not connect to server

Above error shows that ftp server could not be connected. It may be due to problem with its IP address resolution. One best solution is direct testing FTP server connection through ping command on command prompt. If IP resolution or ping response is not present then most probable problem is with DNS setting. Check for its A or CName Record properly pointing to server IP. One of the easy way is to point domain ftp to domain ip in A-Record. Example:
Point :  ftp.domain.com    to    xxx.xxx.xxx.xxx. 


Error:  421 Sorry, cleartext sessions are not accepted on this server.
If you see error like below:
Response:   220 You will be disconnected after 15 minutes of inactivity.
Command:  USER spdo
Response:   421 Sorry, cleartext sessions are not accepted on this server.
Error:    Could not connect to server
This error means your server not excepting Plain FTP. The solution is opting explicit FTP over TLS. Means using  ftpes://  in URL instead  ftp:// . Either write in XML or follow an easy step shown as show:

1 comments :

Anonymous said...

Great sir . Thank you very much for sharing this...

Post a Comment

Your remarks here!