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.
StephenB Thanks for your quick reply!
My ReadyNas is running RAIDiator 5.3.13 firmware.
I enabled FTP-SSL opening port 22 with user authentication.
Also this time, I'm only able to access file when I'm on the local network.
If I try to access remotely from a different I.P. address the FTP client gives me a connection timeout.
Under Server I put my ReadyNas host name (for example the URL would be something like ftps://william-nas:22).
And after that my user name and password.
So it works, but again, not remotely. Maybe I got something wrong with the FTP connection.
Thanks a lot,
William
william-nas is only known to devices on your local network. You missed a very important step from StephenB 's response:
Both would require setting up DDNS service for the router that the ReadyNAS is connected to. There are a couple of free options for that - Netgear builds in a free one in many of their routers. NoIP (among other companies) also offers a free DDNS service.
Then you will have a public IP address and URL that point to your router that you can access from outside your network. You'd have to use that identification instead of william-nas.
Sandshark That's right, I forgot both actions were required. My bad.
I will set up a DDNS service and I'll let you know how it goes.
Thanks,
William
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
