Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

Freenas 8.2.0 NFS on Centos 6.3 Access Denied

Status
Not open for further replies.

krogerssolar

Cadet
Joined
Dec 12, 2012
Messages
4
Hi all new to the form and two freenas i have configured a freenas box i was able to create a nfs share i think i know i have the CIFS share up and going as its working on both my Linux and windows systems I'm trying to connect to the nfs share for testing from my centos servers and i get the info below.

[root@web ~]# mount -v 10.1.2.60:/mnt/backup /media/backups/
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Wed Dec 12 14:02:58 2012
mount.nfs: trying text-based options 'vers=4,addr=10.1.2.60,clientaddr=10.2.2.9'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=10.1.2.60'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.1.2.60 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.1.2.60 prog 100005 vers 3 prot UDP port 796
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 10.1.2.60:/mnt/backup
[root@web ~]#

and same when trying

[root@web ~]# mount -t nfs 10.1.2.60:/mnt/backup /media/backups/
mount.nfs: access denied by server while mounting 10.1.2.60:/mnt/backup
[root@web ~]#

showmount shows

[root@web ~]# showmount -e 10.1.2.60
Export list for 10.1.2.60:
/mnt/backup 10.2.2.0
[root@web ~]#

Im stumped at this point as to what to try firewall is is allowing all ports on cent os server and the network rule in out network firewall for passing info between the two servers and networks.
 

hgoles

Dabbler
Joined
Nov 27, 2012
Messages
10
I've the exact same issue with CentOS 6.3
Code:
mount -o nolock -t nfs xx.xx.xx.xx:/dev/mnt/storage1/test1 /test1
mount.nfs: access denied by server while mounting  xx.xx.xx.xx:/dev/mnt/storage1/test1
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
I'd try mounting from another OS and see if it works. If it doesn't its a permissions issue on FreeNAS. If it does then its a CentOS.

If it's permissions it's hard to help since there's so many ways you can screw it up and there's no simple way to determine where you made the mistake. It's really a "need to know" thing.

If it's CentOS, then obviously we won't be much help here.
 

hgoles

Dabbler
Joined
Nov 27, 2012
Messages
10
I've just create a ZFS dataset and create a simple NFS share on top of it
All of users and groups on NFS share creation form are N/A and I simply add the IP of client to authorised IPs
What other option should I set to be able to use NFS share on other server?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Not a clue.. don't use NFS :(

But having N/A for users and gorups sounds very wrong.
 

hgoles

Dabbler
Joined
Nov 27, 2012
Messages
10
I've followed this guide and still the same issue
Code:
In the following examples, an NFS share on a FreeNAS® system with the IP address of 192.168.2.2 has been configured as follows:
1. A ZFS volume named /mnt/data has its permissions set to the nobody user account and the nobody group.
2. A NFS share has been created with the following attributes:
Path: /mnt/data
Authorized Network: 192.168.2.0/24
MapAll User and MapAll Group are both set to nobody
the All Directories checkbox has been checked

Isn't there any log file in FreeNAS to see why it's rejecting the access of client?
I'm using FreeNAS and it's clients on different range of public IPs, can't this be the cause of issue?
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
I simply add the IP of client to authorised IPs

I'm not sure I would and ANY authorized IP's until you can get it to work without any authorized IP.

Other than that, I'm not sure I can help much either.
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
I've followed this guide and still the same issue
Code:
In the following examples, an NFS share on a FreeNAS® system with the IP address of 192.168.2.2 has been configured as follows:
1. A ZFS volume named /mnt/data has its permissions set to the nobody user account and the nobody group.
2. A NFS share has been created with the following attributes:
Path: /mnt/data
Authorized Network: 192.168.2.0/24
MapAll User and MapAll Group are both set to nobody
the All Directories checkbox has been checked

Isn't there any log file in FreeNAS to see why it's rejecting the access of client?
I'm using FreeNAS and it's clients on different range of public IPs, can't this be the cause of issue?

Sounds like a possible firewall issue.
 

hgoles

Dabbler
Joined
Nov 27, 2012
Messages
10
The issue was with the path, I've used /dev/mnt/storage1/test1 while it was /mnt/storage1/test1
 
Status
Not open for further replies.
Top