NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
FTP Server Capability Configuratioon
There is a KB article on how to configure the ReadyNAS FTP Server capability. In the article it discusses the Authenticiation Mode -- Either User of Annoynmous. Tyhpically for a User mode (no...
schumaku wrote:
Digital999 wrote:
Was you response that the username/paswsword combination is a function of the accounts configured on the ReadyNAS?
Yes, exactly!
Yes. You set up a user account/password (using the accounts page), and then use that with FTP.
If you are planning to use this over the internet, you should set up the NAS to require FTPS Then you use a client like FileZilla or WinSCP, and set it up to use explicit FTP over TLS. Ordinary FTP isn't secure, because the username and password are sent as clear text (unencrypted).
Personally I use FileZilla - one reason is that you don't need to set up masquerading. So you can also use it to access the NAS both locally and remotely. (One problem with masquerading is that it often ends up not working locally).
schumaku: Yes, it's really FTPES, but the ReadyNAS doesn't call it that.
I must have selected the wrong dropdown list
The device is an OS6 ReadyNASdevice -- a ReadyNAS 314 device.
Was you response that the username/paswsword combination is a function of the accounts configured on the ReadyNAS?
Digital999 wrote:The device is an OS6 ReadyNASdevice -- a ReadyNAS 314 device.
No problem!
Digital999 wrote:Was you response that the username/paswsword combination is a function of the accounts configured on the ReadyNAS?
Yes, exactly!
schumaku wrote:
Digital999 wrote:
Was you response that the username/paswsword combination is a function of the accounts configured on the ReadyNAS?
Yes, exactly!
Yes. You set up a user account/password (using the accounts page), and then use that with FTP.
If you are planning to use this over the internet, you should set up the NAS to require FTPS Then you use a client like FileZilla or WinSCP, and set it up to use explicit FTP over TLS. Ordinary FTP isn't secure, because the username and password are sent as clear text (unencrypted).
Personally I use FileZilla - one reason is that you don't need to set up masquerading. So you can also use it to access the NAS both locally and remotely. (One problem with masquerading is that it often ends up not working locally).
schumaku: Yes, it's really FTPES, but the ReadyNAS doesn't call it that.
Thanks for taking the time to respopnd -- much appreciated.
Thanks also for the hints on setting up an FTP access that will be useful.
The ReadyNAS documentation was a little subtle on the username/password for the FTP setup. Probably could sue an explicit update.
Digital999 wrote:
The ReadyNAS documentation was a little subtle on the username/password for the FTP setup. Probably could use an explicit update.
Another thing that is missing - the default passive port range is very large. If you are forwarding ports in your router, you should narrow it.
Normally I suggest 4 passive ports per simultaneous user. Also the best practice is to use passive ports in the private/dynamic port range - which is 49152-65535.
I also suggest using a non-standard port for the control connection (and setting that up in the FTP client). So if you had 10 simultaneous users, you could for example use port 50000 for the FTP control connection and 50001-50040 as passive ports.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
