how do i set NAS drive to be open to FTP to outside internet?

All those settings look right...but if your router isn't UPNP compatible(Universal Plug and Play) then you need to open port 21 manually on its firewall

Also you may need to do a static nat translation on the router to map your public IP to the private IP of the NAS...

What model router have you?

Router "Adtran NetVanta 3120"

in the router public firewall i forwarded from external IP:Port 21 to the Drive IP:Prot 21, is that ok, because when i am trying to connect from outside with FileZila to the drive its failed

also how do i have to configure if i want that also computer on the network IP 192.168.1.102
will be able to FTP to driver? to set in the router the firewall Private zone? do i have to open also port 22?

Thanks
Gvilbis

Ok so sounds like you've done the 'port forwarding', which is NAT...
Have you opened port 21 on the firewall settings on the router?
No need for port 22, although sometimes you need port 20 for FTP - so open that(both on the firewall and through the 'port forwarding' section

As for private access that doesn't need any rules on your router, IP 192.168.1.102 should have direct access to the NAS internally? Can you not as is connect with an internal pc to the FTP on the NAS?

see print screen for setting port 20 and 21 in adtran but when i am trying to connect from outside with port 21 its not letting me

its says something is wrong with the protocol
"FileZilla Server version 0.9.33 beta
Copyright 2001-2009 by Tim Kosse (tim.kosse@filezilla-project.org)
Connecting to server...
Connected, waiting for authentication
Protocol error: Unknown protocol identifier (0x50 0x50 0x48). Most likely connected to the wrong port.
Connection to server closed.
Trying to reconnect in 5 seconds
"

is there other way to test? also user and pass for NAS is the same pass to be use in filezilla?

or maybe because no files is on share mode?
adtran-port-forward-ftp.JPG

here also hows look the share folders setting (print screen)
share-folder-setting.JPG

Ok bit confused by this listing...

its says something is wrong with the protocol
"FileZilla Server version 0.9.33 beta
Copyright 2001-2009 by Tim Kosse (tim.kosse@filezilla-project.org)
Connecting to server...
Connected, waiting for authentication
Protocol error: Unknown protocol identifier (0x50 0x50 0x48). Most likely connected to the wrong port.

Where do you get that output from?
Reason I ask is that's the Filezilla server software, this is an output from the NAS itself?

On your internal LAN can you connect to the FTP service on the NAS? What software are you using to connect to it? Filezilla?

the output above is in filezilla sever which i run it from outside to connect to NAS

from the network i can log to NAS managment page by typing the internal IP and then user and pass and change setting

the share folder setting picture its from NAS managment page

i am connecting to NAS managment configuration by typing internal ip of it

ok, but now from filezilla client i anm receving the following error:

tatus:      Waiting to retry...
Status:      Connecting to 199.27.203.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER Intinno
Response:      530 Non-anonymous sessions must use encryption.
Error:      Could not connect to server

ok i disable the ssl/tls connection and it success partialy

here is the connection message in filezilla client:

Status:      Connecting to 199.27.203.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER Intimo
Response:      530 Non-anonymous sessions must use encryption.
Error:      Could not connect to server
Status:      Waiting to retry...
Status:      Connecting to 199.27.203.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER Intimo
Response:      530 Non-anonymous sessions must use encryption.
Error:      Could not connect to server
Status:      Connecting to 199.27.203.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER intimo
Response:      530 Non-anonymous sessions must use encryption.
Error:      Could not connect to server
Status:      Waiting to retry...
Status:      Connecting to 199.27.203.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER intimo
Response:      530 Non-anonymous sessions must use encryption.
Error:      Could not connect to server
Status:      Connecting to 199.27.203.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER intimo
Response:      530 Non-anonymous sessions must use encryption.
Error:      Could not connect to server
Status:      Waiting to retry...
Status:      Connecting to 199.27.203.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER intimo
Response:      530 Non-anonymous sessions must use encryption.
Error:      Could not connect to server
Status:      Connecting to 199.27.203.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER intimott
Response:      530 Non-anonymous sessions must use encryption.
Error:      Could not connect to server
Status:      Waiting to retry...
Status:      Connecting to 199.27.203.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER intimott
Response:      530 Non-anonymous sessions must use encryption.
Error:      Could not connect to server
Status:      Connecting to 199.27.203.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER Intimo
Response:      331 Please specify the password.
Command:      PASS *********
Response:      230 Login successful.
Command:      SYST
Response:      215 UNIX Type: L8
Command:      FEAT
Response:      211-Features:
Response:       EPRT
Response:       EPSV
Response:       MDTM
Response:       PASV
Response:       UTF8
Response:       REST STREAM
Response:       SIZE
Response:       TVFS
Response:      211 End
Command:      OPTS UTF8 ON
Response:      200 UTF8 option is On.
Status:      Connected
Status:      Retrieving directory listing...
Command:      PWD
Response:      257 "/"
Command:      TYPE I
Response:      200 Switching to Binary mode.
Command:      PASV
Response:      500 OOPS: child died
Command:      PORT 10,0,0,4,10,107
Error:      Could not write to socket: ECONNRESET - Connection reset by peer
Error:      Disconnected from server
Error:      Failed to retrieve directory listing
Status:      Connecting to 199.27.204.74:21...
Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER Intinoo
Response:      331 Please specify the password.
Command:      PASS *********
Response:      230 Login successful.
Command:      OPTS UTF8 ON
Response:      200 UTF8 option is On.
Status:      Connected
Status:      Retrieving directory listing...
Command:      PWD
Response:      257 "/"
Command:      TYPE I
Response:      200 Switching to Binary mode.
Command:      PASV
Response:      500 OOPS: child died
Command:      PORT 10,0,0,4,10,114
Error:      Could not write to socket: ECONNRESET - Connection reset by peer
Error:      Disconnected from server
Error:      Failed to retrieve directory listing

here is the message i am receving:

Status:      Connection established, waiting for welcome message...
Response:      220 vsFTPd 2.0.7+ (ext.1) ready...
Command:      USER Intimo
Response:      331 Please specify the password.
Command:      PASS *********
Response:      230 Login successful.
Command:      OPTS UTF8 ON
Response:      200 UTF8 option is On.
Status:      Connected
Status:      Retrieving directory listing...
Command:      PWD
Response:      257 "/"
Command:      TYPE I
Response:      200 Switching to Binary mode.
Command:      PASV
Response:      500 OOPS: child died
Command:      PORT 10,0,0,4,10,135
Error:      Could not write to socket: ECONNRESET - Connection reset by peer
Error:      Disconnected from server
Error:      Failed to retrieve directory listing

Its failing on passive mode, can you switch Filezilla to Active mode?

http://wiki.filezilla-project.org/Network_Configuration

Try active mode and test...

try to change to active mode unsaccesffuly

please see print screen of my setting

Thanks
passive-mode.JPG

Based on those settings you need to open ports 50000 - 50100 on the firewall as well to make this work - have you opened those ports?

i open but still running on Pasive mode, do i have to set something on the NAS drive?

Possibly...here is a posting related to the same drive you are using...
http://community.wdc.com/t5/WD-ShareSpace/Filezilla-aborts-on-my-Shared-Space/td-p/341859

Possibly the issue is Filezilla, can you use regular windows explorer to access the ftp site? Or even command line FTP?

I.e. using your Internet Explorer browser can you go to - ftp://<yourip>
Or even from a windows machine externally from command line can you

ftp <yourip>
You should get a prompt for user/pass - once connected run command
dir
This should show the contents of the FTP site

Also just to be sure this isn't related to firewall/router are you able to access the NAS INTERNALLY on the same network as the NAS? I mean on the inside network where the NAS is located - can you use Filezilla to connect? If you can't then this isn't related to a firewall issue, its a setting on the NAS(and as I mentioned previously possibly Filezilla doesn't like this model of NAS)