• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 429
  • Last Modified:

NFS not working!

I am trying to set up an nfs server but the client cannot seem to access the server. nfs server runs RH7.3 (2.4.20-20.7) and client runs RH9 (2.4.20-20.9).

On server, I did the following
1. in /etc/exports, added: <server_dir> <client> (rw)
2. exportfs -a
3. checked iptables, hosts.allow/deny. for requisite permissions.

But on client when I do rpcinfo -p <server>, it doesnt show anything. Neither does showmount

also tried restarting necc daemons, checking log files.. nothing out of ordinary.

I can ping and ssh to the server, but nfs is no go :( please help!! rpcinfo -p on server attached below


   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  32768  status
    100024    1   tcp  32768  status
    100004    2   udp    645  ypserv
    100004    1   udp    645  ypserv
    100004    2   tcp    648  ypserv
    100004    1   tcp    648  ypserv
    100007    2   udp    665  ypbind
    100007    1   udp    665  ypbind
    100007    2   tcp    668  ypbind
    100007    1   tcp    668  ypbind
    100011    1   udp    942  rquotad
    100011    2   udp    942  rquotad
    100011    1   tcp    945  rquotad
    100011    2   tcp    945  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   udp  32776  nlockmgr
    100021    3   udp  32776  nlockmgr
    100021    4   udp  32776  nlockmgr
    100005    1   udp  32777  mountd
    100005    1   tcp  32776  mountd
    100005    2   udp  32777  mountd
    100005    2   tcp  32776  mountd
    100005    3   udp  32777  mountd
    100005    3   tcp  32776  mountd
    391002    2   tcp  33196  sgi_fam

  • 2
  • 2
1 Solution
your exports file may be the culprit, assuming you just want one client to be able to get it:


or for the whole subnet:


remember spaces meen different thing different place.  THere is one space in the line after /home/josh and before 192.168....
Have you started the NFS server process. Check with:
   service nfs status
on the server. You might have to start this service.
Matt39Author Commented:
Thanks all who answered. I fixed the problem. The iptables ruleset was not configured properly. Everything is working fine now.

Fine by me.
Matt39Author Commented:
Btw, I think I should add a little more about how the problem was fixed. The problem occured due to incorrect documentation in the man page of iptables. For inserting a rule, the man page says..

-I, --insert
Insert one or more rules in the selected chain as the given rule number. So, if the rule number is 1, the rule or rules are inserted at the head of the chain. This is also the default if no rule number is specified.

This is incorrect. The default is that the rule is appended to the bottom, not added to the head of the list. Have notified the netfilter maintainers about this.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Build your data science skills into a career

Are you ready to take your data science career to the next step, or break into data science? With Springboard’s Data Science Career Track, you’ll master data science topics, have personalized career guidance, weekly calls with a data science expert, and a job guarantee.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now