[PROBLEM] Can't connect to NAS

[julessilver]

@julessilver

Are you comfortable using SSH to work from the command line of your moOde player? (moOde's builtin Web SSH Terminal works great.) Then, let's bypass moOde's NAS configuration panel.

From the command line, can you successfully ping the hostname SynNAS? Does the ping response include the IP address you expect (apparently 192.168.1.73)? 

Example: here's what I get pinging my server OMV-HC1 (note u/l-case doesn't matter in the hostname):

Code:

pi@moode:~ $ ping omv-hc1 -c 1
PING omv-hc1.fios-router.home (192.168.1.12) 56(84) bytes of data.
64 bytes from omv-hc1.fios-router.home (192.168.1.12): icmp_seq=1 ttl=64 time=3.50 ms

--- omv-hc1.fios-router.home ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 3.508/3.508/3.508/0.000 ms

From the command line you can test-mount your username/password-protected SMB share (note that u/l-case doesn't matter in hostname/share but it very much does matter in username and password):

Code:

mkdir /tmp/test
sudo mount -t cifs //<hostname or ip>/<sharename> /tmp/test -o username=xxx,password=yyy

# examples assuming the hostname is SynNAS, the IP address is 192.168.1.73,
# the username is jules, and the password is yyy
# sudo mount -t cifs //SynNAS/Music /tmp/test -o username=jules,password=yyy
# or
# sudo mount -t cifs //192.168.1.73/Music -o username=jules,password=yyy

NOTE ADDED IN EDIT: the mount command is a single line; reading my completed post in my browser it is folded at "-o" into two lines)

(If you leave off the password option, you'll be prompted for it; if you leave off the username option, interesting things happen if the share is protected).

If you can successfully mount it, then un-mount it with (note the odd spelling of the command)

Code:

sudo umount /tmp/test

If the username and/or password is wrong in the mount command, you should see---wait for it---"mount error (13), permission denied". This is what I see repeatedly in your log.

As for NFS, I don't use it but you can test in a similar way:

Code:

sudo mount -t nfs <hostname or ip>:/<sharename> /tmp/test <nfs-options>

Note that there's no nfs option for a username/password. you'll have to dig into NFS documentation to sort out how to deal with the raft of options (both on the server end and the client end).

Hope this helps.

Regards,
Kent

Hi Kent.

Went through your excellent instructions and decided it was the Synology NAS that was at fault. So I made a new admin user and password and re attached the NAS storage using the new credentials.

All works well. now.

Thanks for all your help. 

Your attention to detail is impeccable.

Best regards...jules