![windows filezilla port windows windows filezilla port windows](https://www.tutorials24x7.com/uploads/2020-06-21/files/11-tutorials24x7-install-filezilla-ftp-client-windows-10-passwords-warning.png)
The result should be Windows Firewall with advanced. Lets open up the Firewall panel, press the Windows key on your keyboard and start typing firewall. Now that you have finished setting up the custom port we can move forward to the Windows Server 2012 Firewall.
![windows filezilla port windows windows filezilla port windows](https://help.clouding.io/hc/article_attachments/360008344819/KB-Filezilla-Server-16.png)
Instead you can limit the range of these ports to let's say: 50100-51100. Now this is a wide range and I do not recommend opening all these ports.
![windows filezilla port windows windows filezilla port windows](https://yvettewatson.files.wordpress.com/2013/09/21.png)
By default the FTP client will connect through passive mode, and opens a random port between 1-65535. When port 21 is configurated in the Firewall, and you have setup the users/groups in the FileZilla Server setup you still can encounter the problem above. I had the following problem: Response:Ē27 Entering Passive ModeĮrror: Failed to retrieve directory listing Traditional FTP uses port 21, you should open this on your Firewall (see below) but even after opening up this port some errors can rise to the occasion when using passive ftp. Setting up the FileZilla Server is straightforward, but after configuration the user/groups and directory you can have some trouble setting up the Windows Server 2012 Firewall. If you do not know FileZilla Server or the Filezilla Client I strongly encourage you to try them out at FileZilla comes with a lite and lean GUI, great logging tools, connection (speed)limits and more. I prefer to use FileZilla FTP Server above the traditional IIS FTP module. Setup FileZilla Server Passive Ports on Windows Server 2012