I need to send larger files between work and home. To do that I thought of hosting a simple FTP server within my home network and add a virtual server in the DIR-825 to open a public port (e.g.3021) and route it to the private port 21 on my home machine.
This is all fine. From my work machine I can now connect to port 21 on my home machine using the public port 3021 on the DIR-825.
The problem with FTP is that the initial socket on port 21 is ONLY used for sending commands.
All data (e.g. files and directory listings) are sent on a different port.
Since my work computer is also behine a firewall I need to connect in passive mode and that means the FTP server on my home machine will randomize a port to use for the data traffic.
The FTP server will reroute the local IP to the public IP but the randomized port is not open on the DIR-825 and thus I cannot connect to the data socket from my work machine.
Windows has internal functions to handle such problems for the default FTP port 21 (if you are using Windows Firewall). If a socket is opened on that port, all other ports will be allowed from that particular IP address. There is also a hidden registry key if you want to use a different port than the default 21.
Now, how do I solve this issue with the randomized data traffic port and DIR-825?
Author
Topic: Virtual servers and FTP...how? (Read 2772 times)