FTP server using passive ports

Hey

Thanks for all the answers.

I just tried removing the passive ports on my firewall and tried connecting through my external address from home (RDP from work) and that didn't work. So I guess my router isn't NAT'ing the request right or the FTP server can't understand the NAT'ing being done.

StephenB wrote:
EDIT: since https is allowed, another approach is to manage the home router remotely through https, and change the forwarding rule for port 21 when he wants to access the other ReadyNAS. That is cumbersome, but would work.

This is what I most likely will have to do in the cases where I need to access the other FTP. I can't manage my router directly from work, since the managing ports on the router itself starts at 1024 >.< I have a workaround though with ReadyWOL addon on my Duo and RDP passthrough the router on a lower portnumber than standard :)

Thanks for the very clarifying answer to active and passive mode. I think its safe to say that the corporate firewall in combination with my firewall is borking that connection up into oblivion. I've masqueraded both servers as my external DNS address as well as set my FTP connection to active, since it sets itself as passive as default. It works like a charm.

From the outside the speed of the Duo and Ultra are about the same, so I'll figure out which dataset I need access to :P

As I stated a few posts up, I guess it's a trade-off on which FTP that I want to be available at any given time.

I'll say this will be the answer, given that I've tried everything I could think of, as well as everything suggested here about port-forwarding and routing/NAT'ing.


Thank you again for the help :)
Slasky