FTP access/configurations how-to..

On the PC side I like the FileZilla client.

Here's my setup:

On the Duo, under "standard file protocols"
-check box for FTP is checked
-a non-standard port was chosen - xxxx
-authentication mode is user
-upload resume is enabled
-passive ports are set to xxxx+1 to xxxx+5
-masquerade as is set to the Duo host name.

Note my duo uses the user security model.

for each share on the Duo,
-ftp default access is set to read/write
-all other boxes left alone.

On the router, TCP ports xxxx to xxxx+5 are forwarded to the Duo
ddns is active, so I can use a uri to reach the router.

In FileZilla's site manager
(general tab)
-host is to the ddns uri
-port is set to xxxx
-protocol is set to ftp
-encryption is set to require explicit FTP over TLS
-Logon type is normal
-user password set to my NAS credentials
(transfer settings tab)
-transfer mode is default.

This works for on my home network and over the internet (FileZilla automatically handles the masquerade issue).
Note that it would also connect if encryption were set to off, however, I don't do that.

thanks that info worked like a charm, as i am still new to the concept of NAS I forgot to set FTP read/write in shares, not much differs from what i tested before, did not enable DDNS tho.

one thing that bugs me atm is that, earlier today somehow it worked for a min and then it made a link going to: /homes/<username> but nowhere on my NAS i see this folder, which i assume went into a hidden mode but makes it not possible to delete that folder and content.

also is there a way to resolve the time-out, tried to open a folder that is 11GB in size and it times out.

If you go into the C volume, you should see a home directory and then also see a folder for each username you've configured on the NAS. These shares are not public.

On the timeouts - that would be one reason for ftp resume of course. Though on your local lan you shouldn't see that. Is this over wireless?

actually it is from this PC, and is not wireless, it times out when using browser url using explorer view mode. in filezilla it does not time out but on browser version it does.

ok. I've had trouble in the past with that (before I had a ReadyNAS), so I stick with FTP clients myself.

filezilla up/down from it is 1.4MB/s, when I drag/drop from NAS to desktop it was 7-10MB/s.

I'm having a heckva time trying to gain Remote access. I'd prefer Fizezilla FTP, but could never get it working so then I used ReadyNAS Remote. Now that doesn't work for any of our users. We get logged in and connected, but no shares are displayed. At least 4 systems that used to have access. Two are new converts to WIN7, so maybe it's a WIN7 issue?

Irrespective, on FTP, I've got the NAS configured as described (using PORT 21) and the Port Forwarding tool validates that the PORT is open on my router.

DYNDNS gave me a domain name, which I use as HOST name in FileZilla.

Masquerade is set to the NAS host name (NOT the DYNDNS name).

On FileZilla, I use the DYNDNS name as HOST, my NAS user ID/password and port 21 (I DO NOT SPECIFY the NAS host name anywhere).

When it tries to connect, it does display the DYNDNS name and then indicates the correct IP ADDRESS:21. But, all I ever get is a connection timeout.

BTW, I can use Filezilla just fine to get to the NAS over the LOCAL network. Just can't get it to do it remotely

What am I doing wrong!? (on either ReadyNAS Remote OR FTP). Very frustrating for the users who can get to our file configuration!

For remote FTP, the masquerade address needs to be your dyndns domain name. Make sure your passive port range is forwarded from your router to the NAS as well.

ewok wrote:
For remote FTP, the masquerade address needs to be your dyndns domain name...

Not with FileZilla, it works fine if you set the masquerade address to the readynas host name. (It detects the "misconfiguration" and substitutes the router's IP address).

Quite a convenient feature actually, since it allows you to use FTP both locally and remotely.

Hopefully this is a nice easy question - I'm looking to repeat these instructions, but not sure how to go about the dyndns step and can't see anything obvious about it on the support page on their site.

Is this the service that I need to get to have a domain name for my changing home IP? http://dyn.com/dns/dyndns-free/ Or is it one of the paid products? thx

EDIT: I found this, which seems to explain the steps, except it still doesn't answer that question about whether I need the free or paid dyndns service. Hopefully it will help the next person!
http://www.dyndnscommunity.com/question ... e-net.html