[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem getting NAS box NFS/CIFS to work with Jessie



	Hi.

On Mon, 03 Oct 2016 08:05:59 -0700
Fred <fred@blakemfg.com> wrote:

> 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:
> 
> root@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

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 …

> 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'.


> root@ragnok:/home/fred# mount.cifs 192.168.0.32/Volume_1 /mnt/dns321 
> --verbose
> mount.cifs: bad UNC (192.168.0.32/Volume_1)
> 
> root@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?

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


Reply to: