NAS cannot be mounted

[peerwal]

Hello everybody.

After upgrading to Yakkety, I am no longer able to mount my NAS drive.

both

sudo mount -t cifs -o credentials=/home/peter/.smbcredentials,uid=1000,gid=1000 //192.168.178.1/fritz.nas/ /media/Fritzbox

and the fstab statement

//192.168.178.1/fritz.nas /media/Fritzdaten cifs credentials=/home/peter/.smbcredentials,uid=1000,gid=1000    0    0

produce the same error message: ...'no such device or address'.


Both of them used to work fine in Xenial and still work fine in Ubuntu Mate 16.04.

Does anybody knw, whether anything has changed with cifs? cifs-utils have been installed and I can access fritz-nas as Samba share.


Thanks for any suggestions.

[oshunluvr]

First, check the share:
smbclient -L 192.168.178.1 -Upeter
This assumes the IP and username from your above entry. If you get a list of your shares, the problem is elsewhere. This should confirm you're seeing the server and share.

In the past, adding this option helped:
sec=ntlm

[peerwal]

I get the list of shares, but the additional option does not change anything.

[peerwal]

Found a funny solution: I changed the IP address to 192.168.178.254 and the mount works. If I enter this address into the browser, it is automatically redirected to 192.168.178.1 and the FRITZ!Box login page opens. On my Mate notebook the mount still works using 192.168.178.1 directly. I got no idea, why it only works with the redirection on my Kubuntu PC.

Does anybody have an explanation?

[oshunluvr]

From what I read briefly on the internet, the .254 address is always available on the Fritz!box as a backup if you forget your settings or want to reset to factory defaults.

I suspect something else is blocking your access to 192.168.178.1. I'd be curious to see the output of:

nmap -sP 192.168.178.1/24

[peerwal]

The output is

[FONT=monospace]Starting Nmap 7.12 ( https://nmap.org ) at 2016-11-04 15:22 CET
Nmap scan report for fritz.box (192.168.178.1)
Host is up (0.0010s latency).
Nmap scan report for T61.fritz.box (192.168.178.21)
Host is up (0.050s latency).
Nmap scan report for android-e95735b40ffae461.fritz.box (192.168.178.22)
Host is up (0.055s latency).
Nmap scan report for Gitti-PC.fritz.box (192.168.178.25)
Host is up (0.00097s latency).
Nmap scan report for T3500.fritz.box (192.168.178.26)
Host is up (0.000093s latency).
Nmap scan report for TL-WA854RE.fritz.box (192.168.178.33)
Host is up (0.047s latency).
Nmap scan report for fritz.nas (192.168.178.254)
Host is up (0.00030s latency).
Nmap done: 256 IP addresses (7 hosts up) scanned in 3.69 seconds
[/FONT]

[oshunluvr]

Well, clearly the primary IP is available. Unless something changed your IP tables, I can't imagine why you can't access it from .1

Try mounting the share manually again then looking at /var/log/syslog and see if anything is there relating to the mount failure.

[sithlord48]

try removing the // before the ip address

[oshunluvr]

try removing the // before the ip address

Good catch... <forehead smack> Always look at the simple things first. I use a hostname for my server so I looked right past that.

This:
//192.168.178.1/fritz.nas /media/Fritzdaten cifs credentials=/home/peter/.smbcredentials,uid=1000,gid=1000 0 0

Should be:
192.168.178.1:/fritz.nas /media/Fritzdaten cifs credentials=/home/peter/.smbcredentials,uid=1000,gid=1000 0 0

[peerwal]

Sorry guys, this doesn't work either, as mount.cifs only accepts 2 slashes in front of the IP address. Otherwise it claims 'bad UNC', no matter, whether I drop the slashes in the fstab line or in the manual mount command.

[GreyGeek]

Start with "///"