

The windows firewall may not be aware of this and block it. In passive mode it works differently which means less work on the client side firewall and more work on the server side firewall but you remain in control over the range of ports so you'll have an easier time forwarding and allowing them in various devices. The above linked document explains it all and it's not specific to FileZilla. It's how the FTP protocol works, so regardless of which application you end up with, you need to set it up the same way.

You don't need a subdomain or even a domain name to run an FTP server in-house, and you don't even need a DNS entry if you want to go to it by IP from a non-user device like a scale. I'm not even sure what you're referring to regarding "have to do anything you didn't tell this guy".Īn SSL cert protects the data in transit, but since it is LAN operations and scale data, I don't see how that enters into it. What would you tell him? Step-by-step instructions for setting up any recommended FTP server on this post seems a bit off topic or at least beyond the topic of which FTP do we recommend that is free.Īs for what the other guy did, well, if he's running it externally it is very possible he did use an existing or register a domain, setup a subdomain in his DNS, and get an SSL cert if he didn't have a wildcard to already cover it. Those aren't built into an FTP server, though, and you'd have to do that regardless of which FTP server software you're setting up for public use. The only exception might be a cloud FTP hosting service if you're willing to use their generic domain.
