NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
FTP setup
Whist I am pondering a full NAS upgrade a little issue has come up that is bugging me.
Here's what I am trying to achieve. I have a couple of IP cams on my home network. I have them set up to respo...
The problem with many embedded ftp clients is that they want to upload to the ftp root - this is where the ReadyNas does not allow to upload date, instead the client has first to choose a shared folder ... unless your cameras can be configured to upload to a certain path, there won't be much luck.
Regarding the FTP. account, that’s why I created a fresh one on the NAS, as a clean slate.
I populate that account into either FileZilla or Windows depending how I’m connecting, and it’s all fine. Put the same account info into the cam config, no go. As far as I can see it’s just regular FTP across the board, but I’ll double check in case there were options I overlooked, though I can’t recall any other settings/options right now.
Masquerading could be a factor. FileZilla can work around masquerading issues, but other clients can't. If the cameras are on the home network, then make sure it isn't used on the NAS.
Also, there are two flavors of FTP - passive and active. The dominant setup is passive, but it is possible that the camera needs active.
If you have a link to the camera user guide, perhaps post that.
The problem with many embedded ftp clients is that they want to upload to the ftp root - this is where the ReadyNas does not allow to upload date, instead the client has first to choose a shared folder ... unless your cameras can be configured to upload to a certain path, there won't be much luck.
Boom! FTP path!
There must some difference between how things are handled when dealing with a Windows client with IIS/FTP running vs. how the ReadyNAS provides the service. In the cam FTP path dialogue, the default is "./" which I presume is the root. Now that works just fine with a Win10 client FTP service, and in fact it creates its own subfolders based upon date. All good.
Now what the NAS seems to have done on having the new FTP share created is create a subfolder off the root named as per the share, and the cam config doesn't know about that, so I modded the value to "./NASFTPsharename" and it's working with the account I'd created.
Just need to play with security a bit now, to make sure I only open it up as much as needed.
At the moment I don't know how the RN422 handles FTP but this has moved me a step closer to that upgrade.
Thanks for the pointer! :smileyhappy:Great it helped!
Numb3r6 wrote:
There must some difference between how things are handled when dealing with a Windows client with IIS/FTP running vs. how the ReadyNAS provides the service.:
Yep, that's it. Many generic FTP servers you create a specific folder for the service, either by user, or by user group - so the default path (the ftp root) is a writable and readable folder already. Many NAS (Q, R, S) ftp do list the shared folders in the FTP root, and before uploading a path must be selected. or cd'ed to first.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
