Can’t connect to a local FTP – “Connection closed by remote host.”

This thread might help : Virtualmin Backup to FTP Server | passive ftp connection problem

Q: When I schedule a backup with Virtualmin (3.79 GPL-1) to backup the files to a (Windows 2008 SP2) FTP server, the backup fails. This is because Virtualmin uses a passive FTP connection, which won't work because this FTP server is behind a firewall and only ports 20-21 are forwarded to the FTP Server. A connection is established (on port 55xxx i see in the backup logs) and times out after that because of the used port. When I use a FTP client on my notebook, on the same network, I notice the same. Only non-passive connections work, with passive FTP connections it times out on the directory listing.

Opening/forwarding ports from 49000-65535 is not an option in this situation. Is it possible to setup Virtualmin to don't use passive FTP, but only ports 20-21? When creating the backup schedule filling in the IP address like: xxx.xxx.xxx.xxx:21 is not possible, the ':21' is removed after the schedule is saved.

A: you'd probably be better off to install ssh on your WS2008 box.

The explanation as to when it works or doesn't may be as simple as whether the FTP connection is made in active or passive FTP or instead through SSH.

Apart from this, you could try Fix for Filezilla Failing to Retrieve Directory Listing.

Questions:

1. Have you tried Core FTP Lite, downloaded at Core FTP LE 2.2 : free version ?
2. Have you tried to disable all firewalls and antivirus products on your computer?

A colleague suggested investigating SSL so I deleted the FTP site and started again building a new one. The new ftp site worked. Staring at the config screens for the new FTP site in the IIS Manager I have a suspicion that the binding on the old site was incorrectly specifying 127.0.0.1 as the IP Address instead of All Unassigned (i.e. *)