EAI_NONAME - Neither nodenam

[boco]

First try if you can reach the same hostname in another client (or even your browser).

[markzip]

Getting "EAI_NONAME - Neither nodename nor servname provided, or not known" on all of the servers I admin via FZ
Just started getting this this evening.
FZ worked OK last week.
Can use another FTP program OK to all of these servers
Can see the websites OK
Not a DNS propogation issue that I can think of, the servers have had the same DNS for years now.

Thoughts?

[allmyhoney]

I do have the exact same problem - I am using the latest version and connect connect to any server at all through it. Basically I get this error message:

Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
Error: Could not connect to server

It is not my settings as another ftp program works fine and i have tried over 16 accounts now and nothing. This only stopped working last week?

Any solutions to this?

[boco]

If your entered hostnames are indeed correct, something is blocking FileZilla so it cannot request DNS resolution of these hostnames. As it gets no valid IP address it cannot connect to the server.

[allmyhoney]

I think filezilla is not even connecting to the net - for example i cannot even look for updates and upgrades of it - just errors and says cannot find. Maybe my anit virus software is blocking it or something? I tried uninstalling and reinstalling and no good either!

[boco]

Many anti-virus programs include a firewall. The free ones usually don't. If you cannot even check for updates FileZilla is blocked completely.

[skiman2012]

I had this problem on my website, which I had newly created.

It turned out that I had created my domain through Plesk, but had not gone to my Web Hosting Settings, and then clicked on Access to System and selected Login Allowed. That did the trick.

[Jaggpro]

I was having problems trying to setup my Site manager in Fz to work with Yahoo Servers.
Fortunately my problem was that I was not entering my Domain Name with a .com on the end. ie: ftp.example.com

I also had to put correct it in my User Login... Yahoo-ID@example.com

Hope this helps a few others....

Jaggpro

[abhaysingh]

I have also facing same problem, when i use server IP in place of hostname it work. user server IP solve this problem.

Abhay Singh

[flyhigh]

Error Message: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".

I have used Filezilla for many years with no problems then a few weeks ago this error message appeared. No changes were made that should have affected the ability of my computer to connect. The only changes were Filezilla upgrades. I have worked to resolve the connection problem for many weeks. I called my service provide three times and the problem isn't there. No mis-spellings, I have entered the information over and over. I changed the servers password several times; still no connection. I called my local wifi provider three times and there was no problem there. We changed the wifi modem and router. That didn't sold the problem. I both pinged and tracked the host name several times. Those tests show the paths are clear right up to the website server. Filezilla would not connect.

I had to find another FTP program so I can upload my website files to the website server. The new program works very well, although it isn't as convenient to use as Filezilla, but it uploads my files to the server. If anyone has a knowledgeable suggestion please tell me how to solve this problem using Filezilla. If I cannot resolve this error I cannot use Filezilla as my FTP program.

[techthen]

Have you tried using IP address instead of domain name?

[abrogard]

flyhi.. did you ever find a solution?

what ftp client did you finish up using?

I got the same problem today. If it is DNS then it's a funny one. Surely my FTP client (filezilla) is using the same nameservers as my browser (firefox)? Well firefox finds the domain with no trouble at all.

Makes it look like Filezilla is using some funny nameservers of its own.

But wait: I tried to use the win10 built-in microsoft ftp. And it can't find the domain either !

Makes it look like something the FTP protocol itself does.