filezilla could not connect to server windows 10

Hope that helps!!! I've spent a few hours of my life debugging this - time that I can't get back. These ports only are opened when a client connects and terminate when disconnected. The good news is there's nothing listening on these ports on the server side - so it's mostly harmless from a security standpoint. I'm not one to open ports like this, but there's not much choice if this is the way you are going. Once the additional ports were opened (49152-65535), Filezilla client worked like a charm. I am using IIS 7.5 FTP server with TLS certificate for security. It should never be used on the internet for anything important. Do not use plain text FTP as it's all in the clear (including password). Nothing worked - in looking at the debug logs on the asa, the filezilla client was not negotiating the limited port range - it would try to open the data connection outside of the range, which the ASA restricted.Īlso note that FTP inspection will NOT work when using encrypted channels so the firewall was not able to 'fixup' the FTP protocol as it can do when using plain text.

When using the FTP over TLS / implicit or explicit options in the Filezilla client, it would not honor the port negotiation from the server that was limited to specific ports. Originally, I had configured the server side to use a limited port range and opened those on the ASA and made sure the windows firewall was open as well. I ran into this on my Cisco ASA recently.I had to open ports 49152-65535 to the host serving up FTP behind the firewall, in addition to port 21.

I'm not sure this installation would use the same ports? What else could be the problem? We are migrating servers - the 50001 - 50005 is one of the things that helped get FTPS working on the old server. I have ports 1 through 50005 open on the firewall. Response: 425 Can't open data connection.Įrror: Failed to retrieve directory listing Response: 150 Opening data channel for directory list. Response: 331 Password required for MYUSER Response: 234 Using authentication type TLS Response: 220-written by Tim Kosse 220 Please visit Response: 220-FileZilla Server version 0.9.39 beta Status: Connection established, waiting for welcome message. When I connect from the client FileZilla, I am able to authenticate but cannot get a directory listing: Status: Connecting to MY_SERVER_IP:21. I've set up a self signed certificate in FileZilla server and enabled FTP over SSL/TPS.

Filezilla could not connect to server windows 10