On 3/7/21 1:17 AM, Ed Greshko wrote:
On 07/03/2021 13:44, Robert McBroom via users wrote:
~]# mount -t nfs 192.168.1.248:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service. mount.nfs: Protocol not supported
I don't see anyway to specify the user/password. Things I find with search seem to be quite out of date.
Another mode of access is supposedly
nfs://192.168.1.248/nfs/mcstuffy
using this in a mount command gets NFS URL not supported. dolphin and konqueror do not see it either.
It sounds more like /mnt/HD/HD_a2/mcstuffy is more likely a cifs exported file system than nfs. I've never configured nfs to use usernames/passwords. To do so, I think one needs kerberos configured.
Is your username on the Mycloud the same as on your linux system? If so, what happens when you do....
smbclient -L 192.168.1.248
You should be prompted for your password on the Mycloud
~]# smbclient -L 192.168.1.248 Enter WORKGROUP\root's password:
Sharename Type Comment --------- ---- ------- Public Disk WDdata SmartWare Disk WDdata TimeMachineBackup Disk mcstuffy Disk Transmission Disk Anti-Virus Essentials Disk rm3 Disk Share_Aggregation Disk Samba MSDFS Server IPC$ IPC IPC Service (2-Bay NAS) SMB1 disabled -- no workgroup available
~]# showmount -e 192.168.1.248 Export list for 192.168.1.248: /mnt/HD/HD_a2/mcstuffy * /mnt/HD/HD_a2/SmartWare * /mnt/HD/HD_a2/Public *
Apparently both smb and nfs access are provided to the shares. As was suggested in another response adding the user and password of the client system to the NAS allowed access. Also it was suggested that ssh access had been noted elsewhere. The web page for the NAS provides a check box to enable ssh access with a disclaimer about any changes voiding the warranty. To be explored.