SCP protocol on ReadyNAS 3138

The ReadyNAS Web UI designations are very different from the implementation and the effective file system and mount structure on the Linux system. As I said before,  ssh, scp or ftps on a ReadyNAS are not pointing to a virtual root, much more it's all referring the effective root file system. To bring the data into a shared folder (as configured for share access) use /data/[sharedfoldername]/ or for the user home folder use /home/[username] as the destination folder. 

For the share named Configurations, it's mounted under /data/Configurations - that's the path you need to use on the switch scp client for referring to that share storage destination.

Afraid, you have to become familiar with what is under the ReadyNAS hood for these purposes - some peek and poke using ssh (and the ReadyNAS root or a user account with permitted shell access) can help. The same applies to other NAS vendor implementations. For example, on the QNAP we have symlinks available on the file system root, here you could simply refer to /Configurations - what is undoubted more handy and user friendly.

Also useful could be some OpenSSH clients installed, Windows 10 does allow the installation of OpenSSH  https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse - you need just the OpenSSH client. This allows to do some testing in an easier way than using any embedded scp on a switch.

---

Thonglin wrote:

When I create a new share it automatic create under /VOLUME/....

I using a user: vbackup to send the cisco config file to NAS.

 

---

Your path should be /VOLUME/Configurations/ - you apparently are using FlexRaid on the NAS, with VOLUME as the volume name.

I also suggest testing your vbackup account (logging into the NAS with ssh using it's credentials).

Your posted commands seem to be using cisco as the account and not vbackup though.

---

Thonglin wrote:

scp://cisco:password@192.168.1.1/VOLUME/Configurations/SW-Test.txt

 

---