Filezilla Server

 Filezilla Server notes

Why am I fooling around with FTP? I've never bothered before.

This is still a bit slippery because and I doubt I will improve because too many good alternatives exist for my needs.

Most of the defaults seem good.

I set myself as a user and do use a password whenever asked.

During setup choose start service manually and manually start by current user. Two different steps.

You can always change the Filezilla service to manual in Windows Services.

Change port 21 to some other 5 figure port. This is probably unnecessary when using on a local network and not open to the outside.

In the allow/disallow IP section disallow * meaning all

Then allow the specific IPs or range of IPs 192.168.1.1/24 (It has to be in CIDR format which I do not pretend to understand) Use a calculator like this.

Configure passive port range and Windows firewall. Filezilla will warn of being behind NAT. 

I'm not sure the connection worked because of firewall or passive port settings because I did both.

Port

1. Open up the FileZilla GUI on your server.
2. Click on the top menu Edit → Settings.
3. From the tree menu click on Passive mode settings.
4. Now make sure the checkbox Use custom port range is checked and enter 50100 in the first box a and 51100 in the second.
5. Click OK

Firewall

firewall.cpl

1. From the tree, select Inbound Rules.
2. In the right panel, click New Rule.
3. A windows pops up, select Port and click next.
4. Make sure TCP is selected, and enter 50100-51100 in the Specific local ports field.
5. Hit Next and make sure the Allow connection option is selected. Then hit Next again.
6. Select the zones where this rule need to be applied (in my case I have selected all the zones).
7. Click Next and give this rule a recognizable name: Passive FTP Ports - FileZilla.
8. Click on Finish, and your done.

Filezilla Client worked but WinSCP connected but would not retrieve the directory.

WinSCP works well with SSH

Included in the Windows start menu are Filezilla shortcuts for starting and stopping the server. This is why I do not set up to start the server when Windows starts.

On reason would be Linux to Windows sharing. Another reason to use this would be if Windows networking is being difficult or if you do not want to Windows share a folder but you want or need access to a folder on the network for a specific PC.

But for simple file transfer over a local network Nitroshare is hard to beat for speed and handling large files.  Lanshare is sometimes workable. And I need to remember SendAnywhere 

Reference:

https://johandorper.com/log/filezilla-server-passive-ports