Search Our Database

Troubleshooting the “EAI_NONAME – Neither nodename nor servname provided, or not known” FTP Error

Last updated on |
by

Introduction

The “EAI_NONAME – Neither nodename nor servname provided, or not known” error typically occurs when using an FTP client like FileZilla to connect to a server. This error indicates that the FTP client is unable to resolve the hostname or address of the server. The issue may arise from incorrect hostnames, DNS resolution problems, or network misconfigurations.

Status: Resolving address of ftp.yourdomain.com
Status: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of ftp.appsdesign.asia
Status: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
Error: Could not connect to server
Status: Disconnected from server

This guide explains the causes of this error and provides step-by-step instructions to resolve it. By the end of this article, you will have a clear understanding of how to identify and fix the root cause of this error.

 

Prerequisites

  • Access to your FTP credentials, including the hostname, username, password, and port number.
  • An active internet connection to test the connection.
  • Administrative access to your DNS or hosting configuration, if necessary.

 

Common Causes

  • Incorrect Hostname: The hostname entered may be invalid or improperly formatted.
  • DNS Resolution Issues: The DNS server cannot resolve the hostname to an IP address.
  • Firewall or Network Restrictions: A firewall or network configuration might be blocking the FTP connection.
  • FTP Server Downtime: The server may be unavailable due to maintenance or other issues.
  • Missing Port Number: The port number field is left empty or incorrect.

 

Step-by-step Guide

Step 1: Verify the Hostname

  1. Double-check the FTP Hostname: Ensure that the hostname you are entering is correct. Examples: ftp.yourdomain.com or 192.168.1.1.
  2. Ping the Hostname: 
    ping ftp.yourdomain.com

 

Step 2: Check DNS Resolution

  1. Verify the DNS Settings: 
    nslookup ftp.yourdomain.com
  2. Clear DNS Cache: On your local machine:
    • Windows: Run ipconfig /flushdns.
    • Mac/Linux: Run sudo dscacheutil -flushcache.

 

Step 3: Test with the Server’s IP Address

Replace the hostname in the FTP client with the server’s IP address to test if DNS resolution is the issue.

 

Step 4: Specify the Port Number

Ensure the correct port is specified in the FTP client. Typically, FTP uses port 21, and SFTP uses port 22.

 

Step 5: Disable Firewall and Test the Connection

  1. Temporarily disable firewalls or antivirus software.
  2. Add rules to allow traffic on port 21 or 22.

 

Step 6: Contact our Support team

If the problem persists, contact Support team at support@ipserverone.com with details of the issue and any error messages.

 

Conclusion

The “EAI_NONAME – Neither nodename nor servname provided, or not known” error occurs due to hostname resolution issues or incorrect configuration in the FTP client. By verifying the hostname, testing DNS resolution, specifying the correct port, and checking your network configuration, this issue can be resolved effectively.

Should you have any inquiries about the guidelines, please feel free to open a ticket through your portal account or contact us at support@ipserverone.com. We’ll be happy to assist you further.

Related Article