Filezilla which port

FileZilla comes with a lite and lean GUI, great logging tools, connection speed limits and more. 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. By default the FTP client will connect through passive mode , and opens a random port between Now this is a wide range and I do not recommend opening all these ports.

Instead you can limit the range of these ports to let's say: Now that you have finished setting up the custom port we can move forward to the Windows Server Firewall. Lets open up the Firewall panel, press the Windows key on your keyboard and start typing firewall. The result should be Windows Firewall with advanced In active mode , the client establishes a connection to the command channel but the server is responsible for establishing the data channel. Typically, TCP ports 20 and 21 are used.

In passive mode , the client establishes both channels. However, it then requests the server on the command channel to start listening on a port at the servers discretion rather than trying to establish a connection back to the client. This option might be called NAT forwarding or pinhole configuration on some devices.

When you connect to an FTP server, you are actually making two connections. First, the control connection is established, over which FTP commands and their replies are transferred. Then, in order to transfer a file or a directory listing, the client sends a particular command over the control connection to establish the data connection.

The data connection can be established in two different ways, using active mode or passive mode. FileZilla Pro then issues a command to transfer a file or to get a directory listing, and establishes a secondary connection to the address returned by the server. Once FileZilla Pro issues a command to transfer a file or listing, the server will connect to the provided address. In both cases, the required file or listing gets transferred over the data connection.

In passive mode, the connection is outgoing on the client side and incoming on the server side. In active mode this is reversed. Note that the only difference is how the connection gets established.

Once established, the connection can be used both for uploads or downloads. In passive mode, the involved routers and firewalls on the server side need to be configured to accept and forward incoming connections. On the client side, however, only outgoing connections need to be allowed which will be the case most of the times.

Analogously, in active mode, the router and firewall on the client side need to be configured to accept and forward incoming connections. Only outgoing connections have to be allowed on the server side. Therefore, passive mode is recommended in most cases. This may be a standalone router device perhaps a wireless router , or be built into a DSL or cable modem. Think about a server behind a NAT router. So if a server is behind a NAT router, it needs to know the external IP address of the router in passive mode.

The client then establishes a connection to the NAT router, which in turn routes the connection to the server.