Hi all,
Which ports do I need to have open on an NFS client's firewall to allow it to connect to a remote NFS servers?
When I disable iptables (using ConfigServerFirewall), it connects fine, but as soon as I enable it, NFS gives me this error: root@saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to send.
I have added ports 111 & 2049 in both the TCP & UDP ingres & exgress ranges, but that doesn't seem to help. portmap & nfs is running as well. But as I say, as soon as I disable the firewall, it mounts fine.
Google search results reveal a lot of different ports, like 4000:4004, 83xxxx (something, I forgot) but it still doesn't help.
root@saturn:[~]$ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 48996 nlockmgr 100021 3 udp 48996 nlockmgr 100021 4 udp 48996 nlockmgr 100021 1 tcp 47195 nlockmgr 100021 3 tcp 47195 nlockmgr 100021 4 tcp 47195 nlockmgr 100011 1 udp 4004 rquotad 100011 2 udp 4004 rquotad 100011 1 tcp 4004 rquotad 100011 2 tcp 4004 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 4003 mountd 100005 1 tcp 4003 mountd 100005 2 udp 4003 mountd 100005 2 tcp 4003 mountd 100005 3 udp 4003 mountd 100005 3 tcp 4003 mountd
Hi
You need 2 ports open 2049/udp 2049/tcp but you should read this little howto http://www.cyberciti.biz/faq/centos-fedora-rhel-iptables-open-nfs-server-por...
Per On Thu, 2010-02-18 at 13:00 +0200, Rudi Ahlers wrote:
Hi all,
Which ports do I need to have open on an NFS client's firewall to allow it to connect to a remote NFS servers?
When I disable iptables (using ConfigServerFirewall), it connects fine, but as soon as I enable it, NFS gives me this error: root@saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to send.
I have added ports 111 & 2049 in both the TCP & UDP ingres & exgress ranges, but that doesn't seem to help. portmap & nfs is running as well. But as I say, as soon as I disable the firewall, it mounts fine.
Google search results reveal a lot of different ports, like 4000:4004, 83xxxx (something, I forgot) but it still doesn't help.
root@saturn:[~]$ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 48996 nlockmgr 100021 3 udp 48996 nlockmgr 100021 4 udp 48996 nlockmgr 100021 1 tcp 47195 nlockmgr 100021 3 tcp 47195 nlockmgr 100021 4 tcp 47195 nlockmgr 100011 1 udp 4004 rquotad 100011 2 udp 4004 rquotad 100011 1 tcp 4004 rquotad 100011 2 tcp 4004 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 4003 mountd 100005 1 tcp 4003 mountd 100005 2 udp 4003 mountd 100005 2 tcp 4003 mountd 100005 3 udp 4003 mountd 100005 3 tcp 4003 mountd
-- Kind Regards Rudi Ahlers SoftDux
Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, Feb 18, 2010 at 1:08 PM, Per Qvindesland per@norhex.com wrote:
Hi
You need 2 ports open 2049/udp 2049/tcp but you should read this little howto
http://www.cyberciti.biz/faq/centos-fedora-rhel-iptables-open-nfs-server-por...
Per
uhm....
I have added ports 111 & 2049 in both the TCP & UDP ingres & exgress ranges, but that doesn't seem to help. portmap & nfs is running as well. But as I say, as soon as I disable the firewall, it mounts fine.
On Thursday 18 February 2010 11:00:53 Rudi Ahlers wrote:
Hi all,
Which ports do I need to have open on an NFS client's firewall to allow it to connect to a remote NFS servers?
When I disable iptables (using ConfigServerFirewall), it connects fine, but as soon as I enable it, NFS gives me this error: root@saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to send.
I have added ports 111 & 2049 in both the TCP & UDP ingres & exgress ranges, but that doesn't seem to help. portmap & nfs is running as well. But as I say, as soon as I disable the firewall, it mounts fine.
Google search results reveal a lot of different ports, like 4000:4004, 83xxxx (something, I forgot) but it still doesn't help.
root@saturn:[~]$ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 48996 nlockmgr 100021 3 udp 48996 nlockmgr 100021 4 udp 48996 nlockmgr 100021 1 tcp 47195 nlockmgr 100021 3 tcp 47195 nlockmgr 100021 4 tcp 47195 nlockmgr 100011 1 udp 4004 rquotad 100011 2 udp 4004 rquotad 100011 1 tcp 4004 rquotad 100011 2 tcp 4004 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 4003 mountd 100005 1 tcp 4003 mountd 100005 2 udp 4003 mountd 100005 2 tcp 4003 mountd 100005 3 udp 4003 mountd 100005 3 tcp 4003 mountd
Hi,
NFS by default uses random high numbered ports. See "48996 nlockmgr" above. You need to tie them down to allow them through your firewall
Create the following file /etc/sysconfig/nfs
#/etc/sysconfig/nfs # Created 05.07.05 by Tony Molloy
# Number of NFS threads to run RPCNFSDCOUNT=48
# ports for statd daemon STATD_PORT=4000 STATD_OUTGOING_PORT=4004
# ports for lockd daemon LOCKD_TCPPORT=4001 LOCKD_UDPPORT=4001
# ports for mountd daemon #MOUNTD_NFS_V2=no #MOUNTD_NFS_V3=no MOUNTD_PORT=4002
# ports for rquota daemon #RQUOTAD=no RQUOTAD_PORT=4003
Then open ports 4000:4004 in you firewall as well as port 111 the portmapper and port 2049 for NFS
Hope this helps,
Tony
On Thu, Feb 18, 2010 at 1:11 PM, Tony Molloy tony.molloy@ul.ie wrote:
On Thursday 18 February 2010 11:00:53 Rudi Ahlers wrote:
Hi all,
Which ports do I need to have open on an NFS client's firewall to allow
it
to connect to a remote NFS servers?
When I disable iptables (using ConfigServerFirewall), it connects fine,
but
as soon as I enable it, NFS gives me this error: root@saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to send.
I have added ports 111 & 2049 in both the TCP & UDP ingres & exgress ranges, but that doesn't seem to help. portmap & nfs is running as well. But as I say, as soon as I disable the firewall, it mounts fine.
Google search results reveal a lot of different ports, like 4000:4004, 83xxxx (something, I forgot) but it still doesn't help.
root@saturn:[~]$ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 48996 nlockmgr 100021 3 udp 48996 nlockmgr 100021 4 udp 48996 nlockmgr 100021 1 tcp 47195 nlockmgr 100021 3 tcp 47195 nlockmgr 100021 4 tcp 47195 nlockmgr 100011 1 udp 4004 rquotad 100011 2 udp 4004 rquotad 100011 1 tcp 4004 rquotad 100011 2 tcp 4004 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 4003 mountd 100005 1 tcp 4003 mountd 100005 2 udp 4003 mountd 100005 2 tcp 4003 mountd 100005 3 udp 4003 mountd 100005 3 tcp 4003 mountd
Hi,
NFS by default uses random high numbered ports. See "48996 nlockmgr" above. You need to tie them down to allow them through your firewall
Create the following file /etc/sysconfig/nfs
#/etc/sysconfig/nfs # Created 05.07.05 by Tony Molloy
# Number of NFS threads to run RPCNFSDCOUNT=48
# ports for statd daemon STATD_PORT=4000 STATD_OUTGOING_PORT=4004
# ports for lockd daemon LOCKD_TCPPORT=4001 LOCKD_UDPPORT=4001
# ports for mountd daemon #MOUNTD_NFS_V2=no #MOUNTD_NFS_V3=no MOUNTD_PORT=4002
# ports for rquota daemon #RQUOTAD=no RQUOTAD_PORT=4003
Then open ports 4000:4004 in you firewall as well as port 111 the portmapper and port 2049 for NFS
Hope this helps,
Tony
--
Chief Technical Officer. Tel: +353 061-202778 Dept. of Comp. Sci. University of Limerick.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi Tony,
Where do I do this? On the NFS server, or the NSF client?
4 other NFS clients have connected to this server successfully, and I used the same settings (i.e. opened port 111 & 4096) on the client's firewall
On Thursday 18 February 2010 11:23:43 Rudi Ahlers wrote:
On Thu, Feb 18, 2010 at 1:11 PM, Tony Molloy tony.molloy@ul.ie wrote:
On Thursday 18 February 2010 11:00:53 Rudi Ahlers wrote:
Hi all,
Which ports do I need to have open on an NFS client's firewall to allow
it
to connect to a remote NFS servers?
When I disable iptables (using ConfigServerFirewall), it connects fine,
but
as soon as I enable it, NFS gives me this error: root@saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to send.
I have added ports 111 & 2049 in both the TCP & UDP ingres & exgress ranges, but that doesn't seem to help. portmap & nfs is running as well. But as I say, as soon as I disable the firewall, it mounts fine.
Google search results reveal a lot of different ports, like 4000:4004, 83xxxx (something, I forgot) but it still doesn't help.
root@saturn:[~]$ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 48996 nlockmgr 100021 3 udp 48996 nlockmgr 100021 4 udp 48996 nlockmgr 100021 1 tcp 47195 nlockmgr 100021 3 tcp 47195 nlockmgr 100021 4 tcp 47195 nlockmgr 100011 1 udp 4004 rquotad 100011 2 udp 4004 rquotad 100011 1 tcp 4004 rquotad 100011 2 tcp 4004 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 4003 mountd 100005 1 tcp 4003 mountd 100005 2 udp 4003 mountd 100005 2 tcp 4003 mountd 100005 3 udp 4003 mountd 100005 3 tcp 4003 mountd
Hi,
NFS by default uses random high numbered ports. See "48996 nlockmgr" above. You need to tie them down to allow them through your firewall
Create the following file /etc/sysconfig/nfs
#/etc/sysconfig/nfs # Created 05.07.05 by Tony Molloy
# Number of NFS threads to run RPCNFSDCOUNT=48
# ports for statd daemon STATD_PORT=4000 STATD_OUTGOING_PORT=4004
# ports for lockd daemon LOCKD_TCPPORT=4001 LOCKD_UDPPORT=4001
# ports for mountd daemon #MOUNTD_NFS_V2=no #MOUNTD_NFS_V3=no MOUNTD_PORT=4002
# ports for rquota daemon #RQUOTAD=no RQUOTAD_PORT=4003
Then open ports 4000:4004 in you firewall as well as port 111 the portmapper and port 2049 for NFS
Hope this helps,
Tony
--
Chief Technical Officer. Tel: +353 061-202778 Dept. of Comp. Sci. University of Limerick.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi Tony,
Where do I do this? On the NFS server, or the NSF client?
Put the file on the NFS server and open the ports on the NFS server. Then restart NFS services
# service nfs start # service nfslock start
To make these permanent
# chkconfig --level 35 nfs on # chkconfig --level 35 nfslock on
Check with rpcinfo that NFS is using the specified ports.
Tony
4 other NFS clients have connected to this server successfully, and I used the same settings (i.e. opened port 111 & 4096) on the client's firewall
On Thu, Feb 18, 2010 at 1:11 PM, Tony Molloy tony.molloy@ul.ie wrote:
On Thursday 18 February 2010 11:00:53 Rudi Ahlers wrote:
Hi all,
Which ports do I need to have open on an NFS client's firewall to allow
it
to connect to a remote NFS servers?
When I disable iptables (using ConfigServerFirewall), it connects fine,
but
as soon as I enable it, NFS gives me this error: root@saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to send.
I have added ports 111 & 2049 in both the TCP & UDP ingres & exgress ranges, but that doesn't seem to help. portmap & nfs is running as well. But as I say, as soon as I disable the firewall, it mounts fine.
Google search results reveal a lot of different ports, like 4000:4004, 83xxxx (something, I forgot) but it still doesn't help.
root@saturn:[~]$ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 48996 nlockmgr 100021 3 udp 48996 nlockmgr 100021 4 udp 48996 nlockmgr 100021 1 tcp 47195 nlockmgr 100021 3 tcp 47195 nlockmgr 100021 4 tcp 47195 nlockmgr 100011 1 udp 4004 rquotad 100011 2 udp 4004 rquotad 100011 1 tcp 4004 rquotad 100011 2 tcp 4004 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 4003 mountd 100005 1 tcp 4003 mountd 100005 2 udp 4003 mountd 100005 2 tcp 4003 mountd 100005 3 udp 4003 mountd 100005 3 tcp 4003 mountd
Hi,
NFS by default uses random high numbered ports. See "48996 nlockmgr" above. You need to tie them down to allow them through your firewall
Create the following file /etc/sysconfig/nfs
#/etc/sysconfig/nfs # Created 05.07.05 by Tony Molloy
# Number of NFS threads to run RPCNFSDCOUNT=48
# ports for statd daemon STATD_PORT=4000 STATD_OUTGOING_PORT=4004
# ports for lockd daemon LOCKD_TCPPORT=4001 LOCKD_UDPPORT=4001
# ports for mountd daemon #MOUNTD_NFS_V2=no #MOUNTD_NFS_V3=no MOUNTD_PORT=4002
# ports for rquota daemon #RQUOTAD=no RQUOTAD_PORT=4003
Then open ports 4000:4004 in you firewall as well as port 111 the portmapper and port 2049 for NFS
Hope this helps,
Tony
--
Chief Technical Officer. Tel: +353 061-202778 Dept. of Comp. Sci. University of Limerick.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Thanx, this solved the problem :)
On Thu, Feb 18, 2010 at 3:00 AM, Rudi Ahlers Rudi@softdux.com wrote:
Hi all, Which ports do I need to have open on an NFS client's firewall to allow it to connect to a remote NFS servers? When I disable iptables (using ConfigServerFirewall), it connects fine, but as soon as I enable it, NFS gives me this error: root@saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to send. I have added ports 111 & 2049 in both the TCP & UDP ingres & exgress ranges, but that doesn't seem to help. portmap & nfs is running as well. But as I say, as soon as I disable the firewall, it mounts fine. Google search results reveal a lot of different ports, like 4000:4004, 83xxxx (something, I forgot) but it still doesn't help.
root@saturn:[~]$ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 48996 nlockmgr 100021 3 udp 48996 nlockmgr 100021 4 udp 48996 nlockmgr 100021 1 tcp 47195 nlockmgr 100021 3 tcp 47195 nlockmgr 100021 4 tcp 47195 nlockmgr 100011 1 udp 4004 rquotad 100011 2 udp 4004 rquotad 100011 1 tcp 4004 rquotad 100011 2 tcp 4004 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 4003 mountd 100005 1 tcp 4003 mountd 100005 2 udp 4003 mountd 100005 2 tcp 4003 mountd 100005 3 udp 4003 mountd 100005 3 tcp 4003 mountd
--
I would strongly recommend using NFS4 if at all possible.
See Chapter 18 for NFS in general and 18.8 for security issues
http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-nfs-security.htm...
On Thu, Feb 18, 2010 at 10:22 PM, Agile Aspect agile.aspect@gmail.comwrote:
I would strongly recommend using NFS4 if at all possible.
See Chapter 18 for NFS in general and 18.8 for security issues
http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-nfs-security.htm...
-- Enjoy global warming while it lasts. _______________________________________________
Hi,
How do I install NFS4, exactly? The server runs CentOS 5.4 with all the latest kernel & software updates. From what I can gather on google, NFS is NFS, is NFS?
On Fri, 2010-02-19 at 16:42 +0200, Rudi Ahlers wrote:
On Thu, Feb 18, 2010 at 10:22 PM, Agile Aspect agile.aspect@gmail.com wrote:
I would strongly recommend using NFS4 if at all possible. See Chapter 18 for NFS in general and 18.8 for security issues http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-nfs-security.html -- Enjoy global warming while it lasts. _______________________________________________Hi,
How do I install NFS4, exactly? The server runs CentOS 5.4 with all the latest kernel & software updates. From what I can gather on google, NFS is NFS, is NFS?
-- Kind Regards Rudi Ahlers SoftDux
Try man nfs?
Regards, B.J.
CentOS 5.4, Linux 2.6.18-164.11.1.el5 athlon 09:56:46 up 3 days, 21:57, 1 user, load average: 0.17, 0.13, 0.10
NFSv4 support is already compiled into the CentOS kernel so no extra installation is necessary. To force NFSv4 on the server set the following options in /etc/sysconfig/nfs:
a) MOUNTD_NFS_V2="no" b) MOUNTD_NFS_V3="no" c) RPCNFSDARGS="-N 2 -N 3"
Dan
On Fri, Feb 19, 2010 at 6:40 PM, Dan Burkland dburklan@nmdp.org wrote:
NFSv4 support is already compiled into the CentOS kernel so no extra installation is necessary. To force NFSv4 on the server set the following options in /etc/sysconfig/nfs:
a) MOUNTD_NFS_V2=”no”
b) MOUNTD_NFS_V3=”no”
c) RPCNFSDARGS=”-N 2 –N 3”
Dan
Thanx Dan,
I have done that, but it seems that either these settings don't work on CentOS5.4, or I'm doing something wrong.
root@mars:[~]$ mount.nfs4 master1.mydomain.co.za:/ /bck mount.nfs4: Protocol not supported
I did some google search on this, and apparently I need to change some settings in /etc/init.d/nfs on like 97, but my /etc/init.d/nfs looks different from those in the search results. So, I guess the search results are related to older versions?
Here's a snippet from a google search:
edit your "/etc/init.d/nfs" file as follows:
Comment out line 97 and add the following line (which removes the -N 4.1)
echo -n $"Starting NFS daemon: " # For now, turn off the nfs41 support # daemon rpc.nfsd -N 4.1 $RPCNFSDARGS $RPCNFSDCOUNT daemon rpc.nfsd $RPCNFSDARGS $RPCNFSDCOUNT
Then, restart your NFS server (service nfs restart)
It should then work (mine does)
This one site ( http://www.citi.umich.edu/projects/nfsv4/linux/using-nfsv4.html) though had a walkthrough, but I still don't get it to work.
Any suggestions?
On 2/19/2010 1:38 PM, Rudi Ahlers wrote:
I have done that, but it seems that either these settings don't work on CentOS5.4, or I'm doing something wrong.
Is the remote machine also CentOS 5? NFS v4 is a relatively recent addition to Linux, so if your remote box is older, it might only be capable of NFS 3. I have to do that with our old CentOS 3 boxes here.
On Sat, Feb 20, 2010 at 1:31 AM, Warren Young warren@etr-usa.com wrote:
On 2/19/2010 1:38 PM, Rudi Ahlers wrote:
I have done that, but it seems that either these settings don't work on CentOS5.4, or I'm doing something wrong.
Is the remote machine also CentOS 5? NFS v4 is a relatively recent addition to Linux, so if your remote box is older, it might only be capable of NFS 3. I have to do that with our old CentOS 3 boxes here. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yup, it's CentOS 5.4 :)
root@mars:[www]$ uname -a Linux mars 2.6.18-164.11.1.el5xen #1 SMP Wed Jan 20 08:06:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux root@mars:[www]$ cat /etc/redhat-release CentOS release 5.4 (Final)
On Feb 19, 2010, at 6:41 PM, Rudi Ahlers rudiahlers@gmail.com wrote:
On Sat, Feb 20, 2010 at 1:31 AM, Warren Young warren@etr-usa.com wrote: On 2/19/2010 1:38 PM, Rudi Ahlers wrote:
I have done that, but it seems that either these settings don't
work on
CentOS5.4, or I'm doing something wrong.
Is the remote machine also CentOS 5? NFS v4 is a relatively recent addition to Linux, so if your remote box is older, it might only be capable of NFS 3. I have to do that with our old CentOS 3 boxes here. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yup, it's CentOS 5.4 :)
root@mars:[www]$ uname -a Linux mars 2.6.18-164.11.1.el5xen #1 SMP Wed Jan 20 08:06:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux root@mars:[www]$ cat /etc/redhat-release CentOS release 5.4 (Final)
Are both machines in the same NFSv4 domain? You need to define the domain in the sysconfig/nfs file.
-Ross
I have done that, but it seems that either these settings don't work on CentOS5.4, or I'm doing something wrong.
Is the remote machine also CentOS 5? NFS v4 is a relatively recent addition to Linux, so if your remote box is older, it might only be capable of NFS 3. I have to do that with our old CentOS 3 boxes here.
Yup, it's CentOS 5.4 :)
Are both machines in the same NFSv4 domain? You need to define the domain in the sysconfig/nfs file.
+1; the idmapdomains have to be the same and the users accessing the nfs share have to be "known" on the server either in its /etc/passwd or through nis-nisplus-ldap.
Also, an nfsv4 mount invocation is different from a previous nfs version's mount invocation.
If you are exporting /path/to/shareddir from nfsserver, you have to mount nfsserver:/ /path/to/mountpoint on your client
You may have to export with fsid=0 or fsid=root but it may be assumed if there isn't a directory exported at a higher level, but I have not tested it is assumed without.
-
Agile Aspect -
B.J. McClure -
Dan Burkland -
Per Qvindesland -
Ross Walker -
Rudi Ahlers -
Rudi Ahlers -
Tom H -
Tony Molloy -
Warren Young