Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am having some trouble accessing my NFS share that was previously working. I ran the Red Hat security update today that supposedly updated the NFS server on my machine. I am running Red Hat Fedora 9 (2.6.27.9-73). I am mounting this share as a root file system for an embedded device.
The error I am getting according to /var/log/messages is:
Jan 16 06:46:20 localhost mountd[2679]: Warning: Client IP address '192.168.1.129' not found in host lookup
Jan 16 06:46:20 localhost mountd[3661]: connect from 192.168.1.129 to proc (0) in mountd: request from unauthorized host
I tried adding mountd: ALL to my /etc/hosts.allow file which got rid of the authentication error but the host then fails with:
Root-NFS: Unable to get nfsd port number from server, using default
The operation eventually times out.
Is there something else I am missing? Is there a place can I get more detailed information on NFS authentication? Is there anyway to go go back to the previous version before the security update was applied?
So far as I understand it, once you add the host 192.168.1.129 to your hosts.allow file with the line:
Code:
ALL: 192.168.1.129
you're sorted. Looking at what you said about the nfs port moving to default, perhaps you have a firewall issue which came about as a result of the security update!
I daresay, often a complete reboot helps, looking at what the previous poster said about daemons / services running. A complete reboot will often catch such things.
Last edited by irishbitte; 01-17-2009 at 01:35 PM.
Apparently the client IP address MUST exist in the /etc/hosts file in order for it to work with the hosts.allow file. The hosts.allow man page mentions nothing about this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.