Filezilla File Server


FileZilla will install a service that runs whenever Windows boots up, so if you would rather only run the FTP server manually, select the appropriate option from the drop down menu on the third screen: Apart from that setting, everything else can be left at the defaults for the purpose of this tutorial. FileZilla supports multiple protocols. FileZilla is a cross-platform implementation of the FTP, SFTP, and FTPS protocols. In addition to the unprotected plaintext file transfers it also supports the SFTP and FTPS secure file transfer protocols. For secure file transfers the server-side naturally needs to also support the selected secure protocol. Search for files. If you need to find a particular file on the local machine or remote server: Connect to the server in FileZilla Pro. In the main menu, click on Server Search remote files. Alternatively, press the F3 key. The File search window will be displayed. Choose the search time from the Search type radio buttons.

FileZilla FTP server is a very popular open-source solution. We can use it either as a desktop side solution or as a full server side solution. The desktop side solution is useful for a small installations. However, when we need a larger amount of the traffic or to server more users, the server side solution is only reasonable choice.

In addition, the entire process of data exchange via FTP protocol does not require any server-side visualization. The whole process of graphic representation of available data is carried out on the client side. Therefore, we do not need the GUI on the server side.

Transfer files securely over FTP - Built using Filezilla® Secure FTP Server Solution on Windows Server 2016 Secure FTP Server is a full featured FTP server with support for secure SSL/TLS connections, IP security, anti-FXP options, per-user FTP client speed limits, user groups and MODE-Z compression.

Now we have the solution – the FileZilla FTP server running on the Windows Server Core.

The benefit of such solution is that we will need less resources on the server side. In addition, today, when most of the servers are virtualized, we can have higher density of the VMs per a virtualization host.

We shouldn’t overlook the security aspect of such solution. The Windows Server Core has less exposed services. In addition, there are fewer targets that can be exploited and attacked.

Installing the FileZilla FTP server

The Windows Server Core has a very limited graphical shell with the command prompt. It’s primary intended to be administered remotely. The good news is that you can run some graphical installations inside this limited environment. Therefore, we can install these applications in the same way you would install them on the full Windows Server.

I installed the Windows Server 2008 R2 SP1 Core as the VM in the Oracle VirtualBox. I would recommend you to install integration services for the virtual environment. Although I used the Windows Server 2008 R2 SP1 Standard Core in this demonstration, you can also use a Windows Server 2012 R2 Core or Windows 2016 Core. You should the latest version of the FileZilla Server.

In the Core server we can transfer software either over the CD/DVD disk or using command line tools. I opted for the first method in this demonstration. Therefore, I made an ISO image with an installation of the FileZilla Server.

I run the installation package from the CD (the E: drive in my case) and… voila! We can install the FTP server as usual. You can check my previous post for additional details about the installation process.

When installation process prompt for the startup parameters, you need to choose them in the same way as when installing in the full GUI environment. We will install the software, register a service and service will start automatically.

You should keep in mind that you cannot access from a remote location without the FileZilla server administrator password. Moreover, no password after the installation.

I advise you to install the administration console on the local server. Of course, you can’t run automatically the administration console on the Core server version. Don’t worry, you can manually run it at any time. It’s inside the FileZilla folder. The default path is C:Program Files (x86)FileZilla Server.

You can check if the FileZilla server is running with the netstat command. Just type

in the command prompt. You will see all running network services on the machine. When the FTP service is running, it should be bound to the port 21 TCP.

Our next step will be configuration of the FileZilla server. We should run the admin console from the server. Don’t be confused if the IP address is ::1. This is a loopback address in the IPv6 protocol. All Windows computers, starting from Windows 7 and 2008 Server, will use the IPv6 over the IPv4 as the preferred protocol for an internal network communication.

When we’re inside the FTP console we can configure the server. After that, we will be ready to connect to the server from the remote network location.

If the FileZilla server is not accessible from the network

The Windows Server 2008 Core had the Windows Firewall turned on. This is same firewall as in the full server version. However, we cannot so easily change the rules in this version.


We can either enable the remote server administration protocol (WinRM) or to use command line. I will demonstrate the second approach.

We want to allow the FileZilla Server executable through the firewall. We need to use the netsh command. This command is very powerful. We can control the firewall settings through it.

Our command will be:

In short, we need to allow the whole incoming traffic to any network port our application wants to open. We should also specify the firewall profile. The default is a domain profile.

The Windows Server Core platform has a great potential, which is often neglected. We can use it to build the magnificent network solutions.

Stay tuned.

Documentation » Using WinSCP » Guides » Scripting/Automation »

The FileZilla client does not support any kind of automation.

Though you can use WinSCP to easily script your FileZilla sites.

Use the Import Sites command to import your FileZilla site to WinSCP.

Once the site is imported, use the Generate Session URL/Code command to generate a script or a .NET assembly code (C#, VB.NET or PowerShell) for the site.

Filezilla Server Configuration

Alternatively, you can directly refer to the FileZilla site from the WinSCP script, if you want to maintain a possibility to manage the site settings from FileZilla.

Use the -filezilla switch of the open command:

This is not recommended though as you rely on a configuration stored in your Windows account profile. For this reason the script is not portable.

Once you have a connection established, you can follow a generic guide to automating file transfers with WinSCP.

Or you can even have WinSCP generate a full file transfer script or code for you.


Filezilla Server File Name Invalid

  • Troubleshooting;
  • Scripting documentation;
  • Example scripts;
  • Guide to advanced scripting;
  • WinSCP .NET assembly;
  • Example .NET assembly code;
  • Schedule file transfers or synchronization.