NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RND 2000 v2 remote access
Hello there! So it's 2021 and I have this ReadyNas Duo v2. After struggling a lot I managed to properly install it and access to it on my Macbook running OS Catalina. I even entered the dash...
Sandshark wrote:
If you have opened port 22 and a range of passive ports to the outside world, then you should be be able to directly address the NAS at your static IP from outside: ftps://your.ip.goes.here:22
The NAS uses explicit FTP over TLS, and by default it would be listening on port 21 (not port 22).
As Sandshark says, it is a bit better to use a non-standard port (configuring that in the NAS). As far as passive ports go, I suggest 4 per simulaneous connection. If you only expect to use your PC (and are the only remote user), then you'd only need 4 passive ports.
Non-standard ports are best allocated from the private/dynamic port range - which is 49152-65535. So you could (for example) configure the NAS to use 54321 for the control port, and 54322-54325 as the passive ports. If your FTP client requires masquerading, you'd also need to configure the NAS to use your router's static IP address as the masquerade. Or (as I've already suggested), use FileZilla - which doesn't require masquerading.
Then you'd reserve an IP address in your router for the NAS (so it always has the same IP address). And forward TCP ports 54321-54325 to your NAS IP address. Unfortunately I'm not seeing your router's manual when I search for it, so I can't help with that.
If you do use filezilla, then you'd create a site that specifies your router's static IP address, and which is set to use port 54321. Also, configure the connection to "require explicit FTP over TCP"
Sandshark wrote:
A VPN would be a better plan.
Totally agree.
You will also need to configure and forward passive ports for data transfer.
Some FTP clients will require masquerading to be configured. If you use that, then you'll only be able to use FTP when you are remote. Filezilla is one client that doesn't need masquerading.
I forgot to mention that if your office has a static IP assigned by your internet provider (commercial accounts often do) with or without a URL also assigned, then you don't need the DDNS service, just use that static IP.
Sandshark wrote:
I forgot to mention that if your office has a static IP assigned by your internet provider (commercial accounts often do) with or without a URL also assigned, then you don't need the DDNS service, just use that static IP.
Just want to add that is only relevant if William_rnp has control over the office router (and can therefore leave the NAS in the office).
Thanks for your continuous help!
Yes, I have control and access to my office router. I can login into the router interface to do port mapping as well.
I'm pretty sure it's a static IP address.
And yes, I leave the NAS in the office.
Do you guys have a guide for port mapping in this case? I tried yesterday but I felt kind of lost.
I don't know if I have to write down the NAS IP address or the router IP address. I have very little experience in this.
The router is also Netgear, GS series.
Thanks a lot,
William
William_rnp wrote:
The router is also Netgear, GS series.
What specific router model?
The "GS" products I am aware of are switches, not routers. Though some of those switches do have routing functions, I don't think they support NAT or port forwarding.
William_rnp wrote:
I'm pretty sure it's a static IP address.
If you don't deploy DDNS, then you want to be certain, not "pretty sure". Your provider will be able to tell you.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
