With port triggering, it now works over LAN, but not remote. I’m getting frustrated.
Apart from the fact that port triggering does usually not work well for FTP, connecting and transferring files in LAN does not involve the router at all. In other words, port forwarding in the router is done for external access only. What’s important is opening the ports in the firewall(s).
General configuration:
For Passive mode, the listening port and data port range (recommended 100 ports or more) need to be opened in the server machine’s firewall. Ports must be statically forwarded in the server network’s router. FileZilla Server must know its external IP address(es).
However. the log you posted shows Active mode being used (PORT). For Active mode, the listening port still needs to be forwarded and opened on the server side. But, contrary to the recommended Passive mode, the data ports need to be defined, opened and forwarded on the client side. And it needs to be done by every client connecting. Active mode is very firewall unfriendly.
Hard solution: Configure FileZilla Client and the client network for forwarding and opening the data ports correctly.
Probably much easier solution: Simply reconfigure FileZilla Client so it uses Passive mode. Your server-side configuration of data ports only applies to Passive mode (PASV or EPSV).