Filezilla Server “Failed to bind the listen socket on port 21 to the following IPs”

An older server that’s just ticked away in the background for years on end with Filezilla Server installed just stopped working for some reason. Of course nobody really used it, but everybody wanted to use it when it stopped working.

In the logs I got Failed to bind the listen socket on port 21 to the following IPs.

It just started working after I had done nothing for a while, while I was googling for a solution. But I had tried a number of things:

  • Uninstalled IIS (even though it was not using any FTP ports as confirmed by netstat -b -n > C:\output.txt)
  • Uninstalled Filezilla server and reinstalled Filezilla Server
  • Set the Filezilla service (under services) to an automatic (delayed) start. I had noticed with some other server applications tried to start before the network was ready after upgrading the server to SSDs.
  • Deleted and re-added all the Filezilla server firewall settings, both in normal (under Control Panel) and through the Advanced Security version (under Administrative Tools). Remember to browse… and choose the actual ‘FileZilla Server.exe’ and not the server interface.

Easy trust relationship fix

“The trust relationship between this workstation and the primary domain failed”

Shit happens and so does this error.

Besides the usual complex fixes and leaving/rejoining the domain which can break a user profile (even though most things can be fixed by copying contents).

I found by simply changing the domain from mydomain to mydomain.local(or vice versa) works without breaking the user profile and ‘rejoins’ the domain. Although apparently using the .local suffix is no longer recommended by Microsoft although it still comes added by default.