LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 01-16-2009, 05:05 PM   #1
dcogley
LQ Newbie
 
Registered: Jan 2009
Posts: 5

Rep: Reputation: 0
NFS Authentication Problem after update


Hello,

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

My exports file looks like this:

/nfs/share1 192.168.1.0/255.255.255.0(rw,no_root_squash,sync)

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?
 
Old 01-17-2009, 01:24 PM   #2
bmarien
LQ Newbie
 
Registered: Jan 2009
Posts: 11

Rep: Reputation: 0
Have you checked the release notes on the security update? there might be something helpfull in there ...

Try mounting on localhost, and ofcource check if all necessary services are running/and just to make sure/ restarted
 
Old 01-17-2009, 01:24 PM   #3
irishbitte
Senior Member
 
Registered: Oct 2007
Location: Brighton, UK
Distribution: Ubuntu Hardy, Ubuntu Jaunty, Eeebuntu, Debian, SME-Server
Posts: 1,213
Blog Entries: 1

Rep: Reputation: 88
If the host 192.168.1.129 uses a static IP, then all you have to do is add the host to your hosts.allow file:

Code:
ALL: 192.168.1.129
 
Old 01-17-2009, 01:27 PM   #4
irishbitte
Senior Member
 
Registered: Oct 2007
Location: Brighton, UK
Distribution: Ubuntu Hardy, Ubuntu Jaunty, Eeebuntu, Debian, SME-Server
Posts: 1,213
Blog Entries: 1

Rep: Reputation: 88
Take a look at this:

http://www.userlocal.com/security/securinginetdetc.php

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.
 
Old 01-19-2009, 01:37 PM   #5
dcogley
LQ Newbie
 
Registered: Jan 2009
Posts: 5

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by bmarien View Post
Have you checked the release notes on the security update? there might be something helpfull in there ...

Try mounting on localhost, and ofcource check if all necessary services are running/and just to make sure/ restarted
I did not recieve any release notes for the latest security update. Where can I find these? I am able to mount the nfs share from the same machine.

Quote:
Originally Posted by irishbitte View Post
If the host 192.168.1.129 uses a static IP, then all you have to do is add the host to your hosts.allow file:

Code:
ALL: 192.168.1.129
I tried this and rebooted, and I am still getting the 'Client IP address not found in host lookup' message.

I have IPtables currently disabled.

Thanks
 
Old 01-19-2009, 03:59 PM   #6
dcogley
LQ Newbie
 
Registered: Jan 2009
Posts: 5

Original Poster
Rep: Reputation: 0
Problem Solved

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.
 
Old 01-19-2009, 07:30 PM   #7
chrism01
LQ Guru
 
Registered: Aug 2004
Location: Sydney
Distribution: Rocky 9.2
Posts: 18,359

Rep: Reputation: 2751Reputation: 2751Reputation: 2751Reputation: 2751Reputation: 2751Reputation: 2751Reputation: 2751Reputation: 2751Reputation: 2751Reputation: 2751Reputation: 2751
Actually, you need to check/update the /etc/nsswitch.conf file. It determines which options are used to authenticate services, and in which order.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Apt Authentication Error at Update gustavolinux Linux - Desktop 2 09-03-2008 07:42 AM
Authentication failure while accessing NFS share chnadrapaul Linux - Networking 3 08-14-2006 06:03 AM
Authentication failure while accessing NFS share chnadrapaul Red Hat 1 08-12-2006 01:37 AM
Suse 9 online update proxy authentication Sammy2ooo Linux - General 5 11-20-2003 11:32 AM
How does user authentication work across NFS? SparceMatrix Linux - Networking 3 03-10-2003 02:45 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 01:39 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration