NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Using RN202 behind WNDR 4500v2
Hi,
as described above i am using a WNDR 4500v2 router. Until now i had a 2TB storage conntected to one of the USB ports directly. After having troubles with it and noticing that the router can only handle up to roughly 25000 files, I bought the RN202 , which works fine to me in my home network.
Can anyone describe, how i need to set up me devices, in order to use FTP system instead of ReadyCloud?
I created a folder on RN202 called ONLINE, set the FTP mark and made it readable for everybody but writing access has only a specific group.
So I am not sure at the moment. I guess I need to set some portforwarding in the Router, but i don't have any experience with that. Can anyone help?
Thank you very much in advance!
bastibugla wrote:
Hi StephenB,
thanks for the quick answer!
Can you explain a bit more detailled how I can setup portforwarding in router? I guess I already set it up, but unfortunately it doesn't work at the moment. That's what i set up in router:
Internal IP address is of course that one of NAS.
# Service Name External Start Port External End Port Internal Start Port Internal End Port Internal IP address 1 FTP passive ports 50000 50004 50000 50004 192.168.1.7 2 FTP 20 21 20 21 192.168.1.7 On the other hand, what does "Masquerade" mean in NAS set up? Do I have to enter that folder into my ftp address like: ftp://bastibugla.mynetgear.com/readyNAS ? I guess I need to sign up to those folder with that one, which i defined in NAS, not that admin login, with what i get into my router, correct?
Thanks for your support!!
It looks to me like you set up port forwarding correctly (though you didn't need to forward port 20, that is used for active FTP which won't work through firewalls). You do need to configure that same passive port range in the NAS. You do need to disable the FTP service in your router though (otherwise it will be listening on port 21, which could interfere with the connection).
The way FTP passive mode works, the FTP server (e.g., the NAS) sends the passive port information to the client on port 21. That passive port information includes the IP address (e.g., 192.168.1.7:50000 in your case). But the 192.168.1.7 part won't reach you over the internet, instead the server needs to send the public IP address of your router (which is what bastibugla.mynetgear.com would resolve to). Masquerading tells the NAS to use a different IP address, and not the 192.168.1.7.
Some clients (for instance FileZilla) don't need the masquerade. They automatically detect that the 192.168.1.7 is not routable, and do their own masquerade (taking the public IP address they used to reach your router instead). None of my clients need it, so I leave it disabled. If you do need it, you'd set it to bastibugla.mynetgear.com
On ftp://bastibugla.mynetgear.com/readyNAS, you don't normally include the sharename. ftp://bastibugla.mynetgear.com is enough to reach the NAS (the connection uses port 21, which you have forwarded). The client will give you a user/password challenge, and then show you all the folders that are available. It might show some folders that you aren't allowed to access with that log on, but shouldn't let you navigate into them. But you can include the folder if you wish (like HTTP it is case-sensitive).
3 Replies
(a) in system->settings services, set up FTP authentication as "user". Turn masquerading on, and enable FTPS.
(b) Configure port 21 as control port, 50001-50004 as passive port range. (other ports can be substituted of course).
(c) forward ports 21 and 50000-50004 to the NAS in the router
(d) get a ddns name - imagine bastibugla.mynetgear.comThen access the NAS as ftp://bastibugla.mynetgear.com
If you pick a different control port (say 50000) then you'd use ftp://bastibugla.mynetgear.com:50000 One reason to use a different port is that it allows you to use both your router and the NAS as FTP servers.
Some FTP clients also work with masquerading off (but not all).
FTPS has better security (the connection is encrypted) but not all FTP clients support it. If all your clients do, then you might also set "Force FTPS".
Hi StephenB,
thanks for the quick answer!
Can you explain a bit more detailled how I can setup portforwarding in router? I guess I already set it up, but unfortunately it doesn't work at the moment. That's what i set up in router:
Internal IP address is of course that one of NAS.
# Service Name External Start Port External End Port Internal Start Port Internal End Port Internal IP address 1 FTP passive ports 50000 50004 50000 50004 192.168.1.7 2 FTP 20 21 20 21 192.168.1.7 On the other hand, what does "Masquerade" mean in NAS set up? Do I have to enter that folder into my ftp address like: ftp://bastibugla.mynetgear.com/readyNAS ? I guess I need to sign up to those folder with that one, which i defined in NAS, not that admin login, with what i get into my router, correct?
Thanks for your support!!
bastibugla wrote:
Hi StephenB,
thanks for the quick answer!
Can you explain a bit more detailled how I can setup portforwarding in router? I guess I already set it up, but unfortunately it doesn't work at the moment. That's what i set up in router:
Internal IP address is of course that one of NAS.
# Service Name External Start Port External End Port Internal Start Port Internal End Port Internal IP address 1 FTP passive ports 50000 50004 50000 50004 192.168.1.7 2 FTP 20 21 20 21 192.168.1.7 On the other hand, what does "Masquerade" mean in NAS set up? Do I have to enter that folder into my ftp address like: ftp://bastibugla.mynetgear.com/readyNAS ? I guess I need to sign up to those folder with that one, which i defined in NAS, not that admin login, with what i get into my router, correct?
Thanks for your support!!
It looks to me like you set up port forwarding correctly (though you didn't need to forward port 20, that is used for active FTP which won't work through firewalls). You do need to configure that same passive port range in the NAS. You do need to disable the FTP service in your router though (otherwise it will be listening on port 21, which could interfere with the connection).
The way FTP passive mode works, the FTP server (e.g., the NAS) sends the passive port information to the client on port 21. That passive port information includes the IP address (e.g., 192.168.1.7:50000 in your case). But the 192.168.1.7 part won't reach you over the internet, instead the server needs to send the public IP address of your router (which is what bastibugla.mynetgear.com would resolve to). Masquerading tells the NAS to use a different IP address, and not the 192.168.1.7.
Some clients (for instance FileZilla) don't need the masquerade. They automatically detect that the 192.168.1.7 is not routable, and do their own masquerade (taking the public IP address they used to reach your router instead). None of my clients need it, so I leave it disabled. If you do need it, you'd set it to bastibugla.mynetgear.com
On ftp://bastibugla.mynetgear.com/readyNAS, you don't normally include the sharename. ftp://bastibugla.mynetgear.com is enough to reach the NAS (the connection uses port 21, which you have forwarded). The client will give you a user/password challenge, and then show you all the folders that are available. It might show some folders that you aren't allowed to access with that log on, but shouldn't let you navigate into them. But you can include the folder if you wish (like HTTP it is case-sensitive).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
