Unable to see Data via windows ftp access

Did you try turning off your windows firewall/security? Is the ethernet connection categorized the same as wifi (should be private, work, or home).

the firewall makes no difference if i turn it off.
I still cant see any folders

I'm not sure I have all the information here. I am thinking
(a) FileZilla always works
(b) FTP folders work on a WiFi connection
(c) FTP folders don't open on an LAN connection

What I don't know is if the WiFi and LAN connections are on the same network, or if one is over the internet.
FTP folders not opening correctly seems likely to be an issue with the data connection (made over the passive ports), not the control connection.

yes filezilla alwas works
ftp Folders never work
only Folders with access over the lokal Network work

Thats, that helps.

Unless you have a VPN like readynas remote installed and configured, network folders using windows file sharing will only work on the local network (they should work wirelessly and with ethernet). So that is workng as designed.

I have tried this on my RN102 using admin credentials using ftp:\\nasname:controlport as the ftp path in windows, and it works on the local lan, but it does have some setup challenges.

First of all, if you are using home folders turned on and "allow home folder access over FTP" checked, then the ftp shortcut will open the home folder for the specified user. There is no way to navigate up to the main shares. If you use ftp:\\nasname:controlport\sharename then it fails (and tries to open \home\useraccount\sharename, which didn't exist). So if you want to navigate shares you need to uncheck "allow home folder access over FTP" and reboot the NAS. I believe this is a bug in 6.1.8 - at least it is a serious limitation with windows network folders. It works ok in Filezilla, as it does allow you to navigate to the main shares.

Secondly, if you want to access the FTP folder over the internet then you need to have masquerading set to your external ddns name (and only connect with FTP using that ddns name). When I set that up (entering the ddns name in the masquerade field), the RN102 FTP server did not use the correct external IP address. I went in with SSH, and when I pinged the ddns name the correct external IP address was found. This appears to be another bug in 6.1.8. The work-around is to leave masquerading off, and use filezilla for internet access. If you set up filezilla to use ftps, that is more secure anyway.

great simply turning off the ome folders solved the problem.

Thanks!