Problem getting NAS box NFS/CIFS to work with Jessie

Discussion:

(too old to reply)

Fred

2016-10-03 15:40:01 UTC

Hello,

I am trying to get a D-Link DNS-321 NAS box to do NFS/CIFS on a private
network with a PC running Jessie.

FTP to the -321 works ok. In the -321 admin web page I have the NFS
server enabled. The SMB server is configured to allow r/w access to anyone.

When I try to mount the -321 to access it:

***@ragnok:/home/fred# mount.nfs 192.168.0.32:Volume_1 /mnt/dns321 -v
mount.nfs: timeout set for Sun Oct 2 12:53:54 2016
mount.nfs: trying text-based options
'vers=4,addr=192.168.0.32,clientaddr=192.168.0.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.0.32'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.0.32 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.0.32 prog 100005 vers 3 prot UDP port 32770
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 192.168.0.32:Volume_1

***@ragnok:/home/fred# mount.cifs 192.168.0.32/Volume_1 /mnt/dns321
--verbose
mount.cifs: bad UNC (192.168.0.32/Volume_1)

***@ragnok:/home/fred# mount.cifs 192.168.0.32:Volume_1 /mnt/dns321 -v
mount.cifs: bad UNC (192.168.0.32:Volume_1)

What does UNC mean in the above response and where do I go from here?
Best regards,
Fred

Reco

2016-10-03 17:30:02 UTC

Permalink

Hi.

On Mon, 03 Oct 2016 08:05:59 -0700

So, in plain English, your NAS does not support NFSv4 (but it's
somewhat expected given it's a D-Link). Therefore your client falls back
to NFSv3 …

Post by Fred
mount.nfs: trying text-based options 'addr=192.168.0.32'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.0.32 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.0.32 prog 100005 vers 3 prot UDP port 32770
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 192.168.0.32:Volume_1

… and fails on both UDP and TCP due to server's access permissions most
probably. Further diagnostics for this should be done on servers' side.
Or the server simply has this share under the different name. Try
'showmount -e 192.168.0.32'.

Post by Fred
--verbose
mount.cifs: bad UNC (192.168.0.32/Volume_1)
mount.cifs: bad UNC (192.168.0.32:Volume_1)
What does UNC mean in the above response and where do I go from here?

UNC stands for 'Uniform Naming Convention' aka 'share name'.
What mount.cifs is trying to tell you is that both
'192.168.0.32/Volume_1' and '192.168.0.32:Volume_1' are malformed.
Correct one may be '//192.168.0.32/Volume_1', or if you really
need to do it M$ way '\\\\192.168.0.32\\Volume_1'

Reco

Joe

2016-10-03 17:50:02 UTC

Permalink

On Mon, 03 Oct 2016 08:05:59 -0700

Post by Fred
Hello,
I am trying to get a D-Link DNS-321 NAS box to do NFS/CIFS on a
private network with a PC running Jessie.
FTP to the -321 works ok. In the -321 admin web page I have the NFS
server enabled. The SMB server is configured to allow r/w access to anyone.
mount.nfs: timeout set for Sun Oct 2 12:53:54 2016
mount.nfs: trying text-based options
'vers=4,addr=192.168.0.32,clientaddr=192.168.0.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.0.32'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.0.32 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.0.32 prog 100005 vers 3 prot UDP port 32770
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting
192.168.0.32:Volume_1
--verbose
mount.cifs: bad UNC (192.168.0.32/Volume_1)
-v mount.cifs: bad UNC (192.168.0.32:Volume_1)
What does UNC mean in the above response and where do I go from here?
Best regards,
Fred

UNC is the network path, and I don't believe it can contain ':'. It's
not obvious where that is coming from, but try with two leading '/'s.

My (Wheezy and Sid) /etc/fstab entries look like:

//192.168.1.100/Share /mnt/buffalo/share cifs user,guest,...

--
Joe

Fred

2016-10-03 20:40:02 UTC

Permalink

Post by Reco
On Mon, 03 Oct 2016 08:05:59 -0700

UNC is the network path, and I don't believe it can contain ':'. It's
not obvious where that is coming from, but try with two leading '/'s.
//192.168.1.100/Share /mnt/buffalo/share cifs user,guest,...

It does appear the path needs to be //192.168.0.32/Volume_1.

***@ragnok:/home/fred# mount.cifs //192.168.0.32/Volume_1 /mnt/dns321
Password for root@//192.168.0.32/Volume_1:
mount error(13): Permission denied

It doesn't accept the -321 admin password. Maybe the root password for
the embedded Linux OS which I don't have.

I tried running /sbin/mount.cifs as a regular user:

***@ragnok:~$ /sbin/mount.cifs //192.168.0.32/Volume_1 /mnt/dns321
mount.cifs: permission denied: no match for /mnt/dns321 found in /etc/fstab

Directory /mnt/dns321 does exist and is in fstab. I will try working
with the fstab entry.

***@ragnok:/home/fred# showmount -e 192.168.0.32
Export list for 192.168.0.32:
/mnt/HD_a2 192.168.0.15,192.168.0.3,192.168.0.2

The directory /mnt/HD_a2 doesn't exist.
Best regards,
Fred

Fred

2016-10-04 02:50:02 UTC

Permalink

Post by Fred

Post by Reco
On Mon, 03 Oct 2016 08:05:59 -0700

It does appear the path needs to be //192.168.0.32/Volume_1.
mount error(13): Permission denied
It doesn't accept the -321 admin password. Maybe the root password
for the embedded Linux OS which I don't have.
mount.cifs: permission denied: no match for /mnt/dns321 found in /etc/fstab
Directory /mnt/dns321 does exist and is in fstab. I will try working
with the fstab entry.
/mnt/HD_a2 192.168.0.15,192.168.0.3,192.168.0.2
The directory /mnt/HD_a2 doesn't exist.
Best regards,
Fred

The package cifs-utils must be installed.

The /etc/fstab entry is:
//192.168.0.32/Volume_1 /mnt/dns321 cifs rw,user 0 0

Thanks for the help!
Best regards,
Fred

Andrew F Comly 康大成

2016-10-04 00:30:01 UTC

Permalink

Debian mail list administrator,
Please unsuscribe me from your mailing list, I have already attempted to unsuscribe via debian.org account, but you all still keep sending me mail.

Sincerely,
Andrew F Comly åº·å€§æ

-------- Original Message --------
Subject: Problem getting NAS box NFS/CIFS to work with Jessie
Local Time: October 3, 2016 3:05 PM
UTC Time: October 3, 2016 3:05 PM
From: ***@blakemfg.com
To: debian-***@lists.debian.org

Hello,

I am trying to get a D-Link DNS-321 NAS box to do NFS/CIFS on a private
network with a PC running Jessie.

FTP to the -321 works ok. In the -321 admin web page I have the NFS
server enabled. The SMB server is configured to allow r/w access to anyone.

When I try to mount the -321 to access it:

***@ragnok:/home/fred# mount.nfs 192.168.0.32:Volume_1 /mnt/dns321 -v
mount.nfs: timeout set for Sun Oct 2 12:53:54 2016
mount.nfs: trying text-based options
'vers=4,addr=192.168.0.32,clientaddr=192.168.0.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.0.32'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.0.32 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.0.32 prog 100005 vers 3 prot UDP port 32770
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 192.168.0.32:Volume_1

***@ragnok:/home/fred# mount.cifs 192.168.0.32/Volume_1 /mnt/dns321
--verbose
mount.cifs: bad UNC (192.168.0.32/Volume_1)

***@ragnok:/home/fred# mount.cifs 192.168.0.32:Volume_1 /mnt/dns321 -v
mount.cifs: bad UNC (192.168.0.32:Volume_1)

What does UNC mean in the above response and where do I go from here?
Best regards,
Fred

Dan Purgert

2016-10-04 14:00:02 UTC

Permalink

Post by Fred
[...]
[...]
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 192.168.0.32:Volume_1
[...]
mount.cifs: bad UNC (192.168.0.32:Volume_1)
What does UNC mean in the above response and where do I go from here?
Best regards,
Fred

I don't systemd, so I can't comment on whether or not it is throwing a
spanner into the works.

The first error looks like your /etc/exports is using a different path
thatn you think it is, or /etc/hosts.allow is broken on the NAS.

Given your command, exports should look something this:

- Volume_1 192.168.1.0/24(rw,no_subtree_check)

However, in my experience, /etc/exports will use the full path
(commonly, this'll be something like "/srv/Volume_1"). You will likely
have to check the file to verify what it really is.

Your hosts.allow should be something like
- "ALL: 192.168.1.0/255.255.255.0" (possibly /24, depending on how your
system behaves).

The UNC path is "Universal Naming Convention", and essentially means
"path". Given the error, it reinforces my thinking that you forgot to
provide the full path of the share.

--
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281

Fred

2016-10-04 19:10:02 UTC

Permalink

Hi Dan,

Post by Dan Purgert

I don't systemd, so I can't comment on whether or not it is throwing a
spanner into the works.

I don't think systemd had anything to do with the problem. It was, of
course, my fault!

Post by Dan Purgert
The first error looks like your /etc/exports is using a different path
thatn you think it is, or /etc/hosts.allow is broken on the NAS.
- Volume_1 192.168.1.0/24(rw,no_subtree_check)
However, in my experience, /etc/exports will use the full path
(commonly, this'll be something like "/srv/Volume_1"). You will likely
have to check the file to verify what it really is.
Your hosts.allow should be something like
- "ALL: 192.168.1.0/255.255.255.0" (possibly /24, depending on how your
system behaves).
The UNC path is "Universal Naming Convention", and essentially means
"path". Given the error, it reinforces my thinking that you forgot to
provide the full path of the share.

I don't have an /etc/exports and the NAS box embedded Linux OS doesn't
allow users access to system level stuff. Volume_1 is the root of the
user storage area. My main problem was that the path to the NAS box
needed to be: //192.168.0.32/Volume_1 instead of using a colon as
mount.nfs wants. Also a correct entry in /etc/fstab was needed so a
regular user could mount it.
Thanks for the help!
Best regards,
Fred