NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Can't get FTP access to work on my shares
Hi all, I can't get FTP access to work on the shares on my ReadyNAS. I am able to connect to the server running on the NAS (my client tells me so), but it fails in the authentication process. Ev...
You are not using FTP, since that doesn't use TLS - you are using either FTPS or SFTP.
In FileZilla, set the protocol to "FTP - File Transfer Protocol" and set Encryption to "Require explicit FTP over TLS".
On the NAS make sure "Enable FTPS" is checked. You can also set "Force FTPS".
There might also be an issue with the specifics of the password - either the length or perhaps a special character. If that's a possibility, then try testing with a simpler password, and see if that makes a difference.
But are you saying that I should be able to login to the Ftp server using my administrator account credentials? Which settings should I make for that to work?
If FTP access is enabled for shares (or the admin home folder), then you just use "admin" and the NAS admin password. No other settings are required.
This assumes that passive ports are properly configured in the NAS and the router. If the FTP client needs masquearading that also needs to be set up properly.
What FTP client are you using?
I'm using Filezilla on Windows10, and 'andFTP' from my Android phone.
It says "login incorrect, could not connect to server." This is strange, I can succesfully login to the NAS's admin panel with the same credentials.
This happens if I try to connect on my laptop that's on the same LAN as the NAS, and also if I use my phone on cellular data.
As for port forwarding, I've set them (port 21 and the range of passive ports) in my router, and used the default passive ports that the NAS uses. Fom what I read, I don't need to configure masquerading with Filezilla.
I'm positive that I have FTP enabled in system -> settings, and also in the share settings.
Any ideas?
annekrijn wrote:
used the default passive ports that the NAS uses.
That's too broad a range. Shrink it down (I take the expected simultaneous connections and multiply by four). Use ports in the dynamic range (49152–65535)
However, that doesn't explain the symptoms on the local lan. You're using the local IP address on the LAN? Or the DDNS name/router internet IP?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
