Does anyone actually have NFS4 working on an FC6 machine? I've been trying for hours to mount using nfs4.
When i using `mount` I get: mount: pinging: prog 100003 vers 4 prot tcp port 2049 mount.nfs4: Operation not permitted
When I use `mount.nfs4` I get: mount.nfs4: Operation not permitted
In addition to that, if I use any of the parameters for mount.nfs4 documented in its usage text, i get the usage text printed out again.
Please advise. My next option is to use samba if this doesn't pan out.
On Thu, 2006-12-14 at 22:22 -0600, Arthur Pemberton wrote:
In addition to that, if I use any of the parameters for mount.nfs4 documented in its usage text, i get the usage text printed out again.
Please advise. My next option is to use samba if this doesn't pan out.
A few things to check:
1. selinux 2. firewall 3. exports incorrectly configured
Regards,
Ranbir
On 12/14/06, Arthur Pemberton pemboa@gmail.com wrote:
Does anyone actually have NFS4 working on an FC6 machine? I've been trying for hours to mount using nfs4.
Greetings Arthur,
I used the instructions from here to set up NFS v4: http://www.brennan.id.au/19-Network_File_System.html#nfs4
I used it for a few days before switching back to NFS v3.
HtH
Hi.
I have the same problem. SeLinux is off, firewall on client is off.
# mount -vvv -t nfs4 192.168.200.1:/ /media/160gb/ -o async,auto,exec,_netdev,nodev,rw,retry=5,rsize=32768,wsize=32768,proto=tcp,hard,intr mount: pinging: prog 100003 vers 4 prot tcp port 2049 mount.nfs4: Operation not permitted
With -t nfs everything is ok.
On Thu, 2006-12-28 at 00:06 +0300, Kevac Marko wrote:
Hi.
I have the same problem. SeLinux is off, firewall on client is off.
# mount -vvv -t nfs4 192.168.200.1:/ /media/160gb/ -o async,auto,exec,_netdev,nodev,rw,retry=5,rsize=32768,wsize=32768,proto=tcp,hard,intr mount: pinging: prog 100003 vers 4 prot tcp port 2049 mount.nfs4: Operation not permitted
With -t nfs everything is ok.
Yes, I have it working: mount . . .nest:/ on /home/home1 type nfs4 (rw,addr=192.168.158.1) . .
Does /var/log/messages contain any information? And how about the logfile on the server? I recall having the same issue, but don't recall the reasaon. The logfiles however should give more details