NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Unable to see Data via windows ftp access
Hi, got a Problem im struggeling with for a Long time: I can acces my data with Filezilla via FTp and it works well. But if i create a FTP Folder in The Windows Explorer i can open it but do not ...
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.
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
