filezilla ftp server setup on windows 2008 r2 firewall

Overall, I'd recommend against using FTP if at all possible for the complexity of the above as well as the fact that everything is sent in clear text. In Server 2012, you can install FTP server role under the IIS server role. In this mode, your server needs to allow incoming connections on whatever ports it will allocate for passive data transfer. The client requests an IP and Port to use for data transmission by specifying the PASV command. 'Passive mode' FTP addresses some of these concerns by having only client-initiated connections. Most clients will choose a random high number port, then become very upset to find out that their Linksys router is performing Stateful Packet Inspection and denying the data connection. The client needs to allow incoming connections on whatever port it's requested the connection back on.

You need to allow outbound traffic on any port from this system to wherever the client is (generally in a decently secure environment this is awful).After this connection is established, the client can provide the server with an IP address and port number to connect back to the client on. With 'active mode' FTP, the FTP client initiates a connection to the server on TCP port 21, therefor you need to allow incoming traffic on TCP/21. The issue here is that FTP is a flawed protocol in today's world of opening specific ports for specific purposes.

Filezilla ftp server setup on windows 2008 r2 firewall