LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   mount.nfs: mount to NFS server 'rpcbind' failed (http://www.linuxquestions.org/questions/slackware-14/mount-nfs-mount-to-nfs-server-rpcbind-failed-677237/)

w1k0 10-17-2008 09:49 PM

mount.nfs: mount to NFS server 'rpcbind' failed
 
It isn't a question but an answer. I had a problem and I resolved it after some researches. I publish the report about it in hope it will be useful for the other users.

I use three machines: home1, home2, and home3. System configuration on all those machines is virtually the same. First and second machines I used for several years with different versions of Slackware -- third machine is new one and I just try to configure Slackware on it.

When I tried to use NFS I stated the following...

I could ping from any machine to any machine but I had some problems with NFS.

On home1 I could mount home2 directories but I couldn't mount home3 directories.

On home2 I could mount home1 directories but I couldn't mount home3 directories.

On home3 I could mount home1 directories but I couldn't mount home2 directories.

In three cases in which I couldn't mount directory mount command displayed the same message:

mount.nfs: mount to NFS server 'rpcbind' failed: RPC Error: Program not registered
mount.nfs: internal error

I started my researches...

Each successful mount and unmount was reported in /var/log/messages on the client side by something like:

mountd[2689]: authenticated mount request from 192.168.1.x:796 for / (/)
mountd[2689]: authenticated unmount request from 192.168.1.x:641 for / (/)

When I failed to mount home2 directories on home3 machine /var/log/syslog on the server side reported:

kernel: nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
portmap[2894]: connect from 192.168.1.3 to getport(mountd): request from unauthorized host
portmap[2895]: connect from 192.168.1.3 to getport(nfs): request from unauthorized host
portmap[2895]: connect from 192.168.1.3 to getport(nfs): request from unauthorized host

When I failed to mount home3 directories on home1 and on home2 none machine reported nothing.

In such situation I decided to check everything from scratch...

After a dozen or so minutes I stated the reasons of that problems were relatively simple.

On home3 rc.nfsd hadn't permission to be executed for some reason.

# chmod u+x /etc/rc.d/rc.nfsd

# /etc/rc.d/rc.nfsd start

...and I can mount home3 directories.

On home2 server home3 client wasn't registered in hosts.allow.

# echo "ALL: ALL@192.168.1.3 : ALLOW" >> /etc/hosts.allow

# cat /etc/hosts.deny

ALL: ALL@ALL

# cat /etc/hosts.allow

ALL: ALL@127.0.0.1 : ALLOW
ALL: ALL@192.168.1.1 : ALLOW
ALL: ALL@192.168.1.2 : ALLOW
ALL: ALL@192.168.1.3 : ALLOW

...and I can mount home2 directories using home3 machine.

It's all.

Have a nice day...

Bruce Hill 10-18-2008 12:40 AM

Good on yah!

f14f21 11-09-2008 11:40 AM

that's nice of you to give us solution
thank u

olego 02-11-2010 06:44 AM

Thank You for correct solution! I encountered this problem today and I wonder why I should care about /etc/hosts.allow if I already set allowed hosts in the /etc/exports ?

w1k0 03-30-2010 03:45 PM

Using /etc/hosts.deny and /etc/hosts.allow you configure your tcpwrappers. For more information see here. Using /etc/exports you configure your Network File System. For more information see here.

I'm glad I helped you to solve your problem.

I’m sorry for a long delay in the answer but usually I don’t monitor my old threads.


All times are GMT -5. The time now is 03:31 AM.