Updated To Version 3.10.0 Now Receiving Errors

[botg]

You can select insecure plain FTP in the Site Manager.

[boco]

Global default? No.

[petecomwest]

Hi everybody,
I joined up when I read 'nodirectorylisting' wishing to backdate Filezilla. That's exactly what I have done. Fortunately, I always keep old versions in my downloads folder, and was able to reinstall 3.9
No matter what I did (ports, firewalls, encryption etc) it simply would not connect. I have now set the program to never check for updates.

If everyone were to use that approach, we'd still be living in caves. Move forward, convince your server administrator or server hosting provider to fix their server.

I just called, ones again, to my Internet connection provider, and as usual, there was some one who can speak he's own South-East Asian language only, even their second official language is English .. o'boy..

Of course it was just Call Center support, where person who answered didn't knew what is FTP?!! I tried to speak slowly, and in the end he understood that much that he sent some email message to their so called 'technicians', who may get and read the message, and if he read, he should be able to fix the problem, as it FOR SURE IS on their end.

btw. English is not my mother language and I have never studied it but still, those call centers are terrible more then me

This situation game to me 3 weeks ago, and not only FileZilla but every FTP program I've tried now:

Status: Resolving address of xxxxxxxx.net
Status: Connecting to xxxxxxxx...
Status: Connection established, waiting for welcome message...
Error: Could not connect to server

3 weeks is a long time for person like me who work 16/24/360 online and upload daily large amount of files.

[petecomwest]

You can select insecure plain FTP in the Site Manager.

That doesn't change anything with my connection. No help.

[boco]

That would mean you have a different problem. Provided you used that very Site Manager entry to connect. Last Server and QuickConnect don't work.

[stuffdone]

Suddenly cannot access remote directory listing even though connected. found that WinSCP works fine and will import my FileZilla settings. This was easier than spending hours trying to find out why FileZilla suddenly stopped being nice.

[sport]

I'm running FileZilla Server and had to same MLSD error when a friend tried to log in using FileZilla Client. Opened Windows Firewall, Inbound Rules, double-clicked on Filezilla Server, Protocols and Ports: Protocol type, TCP; Local port: All ports; Remote port: All ports. Apply.

Access through ftptest.net and my friend accessed my FileZilla server.

Hope this helps.