What's the best way to create a personal FTP server for sharing files via direct links? I've experimented with different programs, but have found that while I'm able to download files from the server at home, those who try to access the link encounter errors. It's frustrating - I've already spent five hours on this.

Interestingly, I seem to have three leftover servers available on IPs that start with 170, and these work just fine. However, the server with my own IP (starting with 212) doesn't seem to function as intended. Specifically, when I try to access it using this format: ftp://172.18.6.116, the download works as expected. But when I share the link with others, it simply doesn't work.

Creating your own FTP server is a fairly straightforward process. It starts with obtaining a permanent IP address for your computer. After that, simply download and install Serv-U program to get started. With this program, it's easy to grant specific users unique permissions - such as read-only access or the ability to download only certain files. You can even specify that users share files back to your computer, if desired.

Alternatively, if you have a Windows server installed on your computer, you can utilize the built-in FTP server functionality. There are benefits to using an FTP server instead of Microsoft Sharing: it's generally more secure and you don't need to create users on your PC to grant permission to the server. Plus, with an FTP server, you can manage logins separately and set download speed limits for various users. If you're looking to create an FTP server, consider using the FileZilla Server program for optimal performance.

When two or three computers are connected to the same router, they operate in a default workgroup called "WORKGROUP." You can check this by visiting the Control Panel, then System. Once there, you can permit specific viewing access among computers. In doing so, all folders that have view/modify permissions appear instantaneously on the local network, allowing for faster downloads and uploads than with a web-based FTP server.

Of course, when attempting to connect via external internet to a computer, a static IP address is necessary to maintain connectivity. Unfortunately, some Internet providers still offer dynamic addresses and even claim their local network as a city-wide internet service. This leads to confusion and frustration on behalf of customers who may mistakenly consider this service free.

You can get these links on the DropBox website. In general, I did this at home - install FileZilla Server, it's not difficult to configure it, then if you work through a router, configure Port Forwarding, if not, just give your friends (acquaintances) your IP.

I've encountered an issue with my FTP server. I'm able to connect without issue via FTP client on the local machine, but when using my mobile phone or another PC, the folders that I created on the local machine are not displayed - even though I was able to create a new folder from my mobile phone, which I still cannot see. On the local machine, however, I can view the folder as expected.
 I have correctly assigned permissions, so I'm not sure what the issue could be.

From a technical perspective, the issue may lie in the network configuration or firewall settings of your home network. It's important to ensure that your router is forwarding incoming connections on the FTP port (usually port 21) to the correct internal IP address of the server. Additionally, check if your firewall is allowing inbound and outbound traffic on the FTP port.

Regarding the difference in performance between the servers with IPs starting with 170 and 212, it's worth considering the network infrastructure and potential restrictions imposed by your internet service provider. Servers with public IPs that begin with 170 might not face the same limitations as those with IPs starting with 212. This could explain why the former work as intended while the latter encounters issues when accessed externally.

In order to troubleshoot the problem, I recommend reviewing the logs of your FTP server for any error messages or indications of failed connection attempts. You may also want to consider using dynamic DNS services to map a domain name to your home IP address, which can make sharing links more user-friendly and help bypass some potential issues with direct IP access.

While it's disheartening to have spent five hours on this without a clear resolution, I encourage you to persevere and continue exploring different approaches. It's often through persistence and methodical troubleshooting that elusive technical issues can be resolved. If necessary, seeking assistance from online communities or forums dedicated to networking and server administration might provide valuable insights and solutions.
Setting up a personal FTP server for file sharing can be a complex endeavor, but with the right approach and determination, you can overcome the challenges and achieve reliable accessibility for your shared files.