![](https://seccdn.libravatar.org/avatar/c0d08030ac6d4a16f93b99a62426bf1b.jpg?s=120&d=mm&r=g)
I can't use nfs in my internal LAN. I use the SuSE kernel 2.2.16, configured for (normal, not kernel) nfs. While the files /etc/exports and /etc/hosts.allow are configured according to the man pages, and rpc.mountd and rpc.nfsd are started at boot time, nevertheless the mountd server refuses the access to the directory listed in /etc/exports. In the past, with older versions of the system, I had no problems running nfs so I suppose it may be a matter of new security features, not mentioned in the man pages. The rpcinfo -p command gives: program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 545580417 1 udp 703 bwnfsd 545580417 1 tcp 705 bwnfsd 100005 1 udp 740 mountd 100005 2 udp 740 mountd 100005 1 tcp 743 mountd 100005 2 tcp 743 mountd 100003 2 udp 2049 nfs 100003 2 tcp 2049 nfs Please help !
![](https://seccdn.libravatar.org/avatar/2e846a486bb47d24595d540de089fe0d.jpg?s=120&d=mm&r=g)
amircea@libertysurf.fr wrote:
I can't use nfs in my internal LAN. I use the SuSE kernel 2.2.16, configured for (normal, not kernel) nfs. While the files /etc/exports and /etc/hosts.allow are configured according to the man pages, and rpc.mountd and rpc.nfsd are started at boot time, nevertheless the mountd server refuses the access to the directory listed in /etc/exports. In the past, with older versions of the system, I had no problems running nfs so I suppose it may be a matter of new security features, not mentioned in the man pages.
What error message do you get? Since you've used NFS before, you're probably aware that you need to watch the uid/gid mappings when mounting over NFS. Check the permissions on the directory you're trying to access as well. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
participants (2)
-
amircea@libertysurf.fr
-
Chris Reeves