I download FileZilla Server from http://filezilla-project.org/ and I wanted to install it on my Windows Server 2008. I did a basic install, created a user and set a directory for the user. When I tried to access it via the FileZilla client I noticed I could not connect to the FileZilla server. Troubleshooting led to the Windows firewall being the root cause.

In this article I will show you how to configure Windows Firewall to allow FileZilla Server. You can apply this same method for other network services you want to use with Windows Firewall because we are going to set the firewall rules by the application and not by the port.

FileZilla Client error:

Open "Windows Firewall" from Administrative Tools and select "New Rule"

Select "Program", and then press "Next"

Press "Browse"

Browse to C:\Program Files\FileZilla Server\ and select "FileZilla server.exe". Then press "Open". You can apply this method for almost any program that is having issues connecting through Windows Firewall. The key to configuring Windows Firewall is selecting the right EXE to allow. Sometimes the only way to find the right EXE is trial and error. If I would have selected “FileZilla Server Interface.exe” instead of “FileZilla server.exe” it probably would not have allowed the connection.

Verify that the correct EXE is in the path location and press "Next" to continue

Select "Allow the connection", and then press "Next" to continue

Select Domain, Private and Public then press "Next". For most situations you will need to have all of these checked.

Enter a name for the Firewall Rule, in this case we are going name it "FilaZilla FTP Server" so we can easily find it later if we need to change anything

Make sure the rule is set to "Enabled". We can now try to connect again using the client

After the configuration I was able to connect to the FileZilla FTP Server. In the event you cannot connect to the server check the following:

Check the Servers active/passive configuration settings

Check the Clients active/passive configuration settings

Check to see if a router or another firewall is preventing connection both on the client and server side

Keeping these particular logon details is especially recommended. Perhaps you must secure your router a lot better with ip 192.168.l.254. Just in case, if you have neglected these things, it is advisable to reset your router once again.