Re: Update Broke NFS Exports
Jameson wrote: Ok, now, I've set up a reverse zone containing just the two entries for the 192.168.1.55 client and my server at 192.168.1.51. Forward look ups work fine. host 192.168.1.55 gives me: Host 55.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN) Well, I fixed this.. I accidentally setup my reverse zone as 192.168.1.0 as apposed to 192.168.1. It looks like this also fixed my NFS woes. I wonder why it worked before if I need this now. Hopefully, if it stops working anywhere else someone will come across this, and learn that they now need reverse DNS working to get NFS working. Which is kind of a shame, as I doubt most home users will even have forward DNS setup. =-Jameson I would expect adding an entry for 192.168.1.51 to your /etc/hosts on the nfs server to also be a solution, in lieu of configuring private dns. I was hoping to find an argument that could be added in /etc/sysconfig/nfs to turn off the inverse lookup requirement, but have only found rpc.mountd's -r option which is the opposite of what you need. -- "A society grows great when old men plant trees whose shade they know they shall never sit in" - Greek Proverb -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update Broke NFS Exports
On Fri, 2009-01-16 at 21:49 -0500, Jameson wrote: > > Ok, now, I've set up a reverse zone containing just the two entries > > for the 192.168.1.55 client and my server at 192.168.1.51. Forward > > look ups work fine. host 192.168.1.55 gives me: Host > > 55.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN) > > Well, I fixed this.. I accidentally setup my reverse zone as > 192.168.1.0 as apposed to 192.168.1. It looks like this also fixed my > NFS woes. I wonder why it worked before if I need this now. > Hopefully, if it stops working anywhere else someone will come across > this, and learn that they now need reverse DNS working to get NFS > working. Which is kind of a shame, as I doubt most home users will > even have forward DNS setup. probably not but I would expect that entries in /etc/hosts would be sufficient. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update Broke NFS Exports
> Ok, now, I've set up a reverse zone containing just the two entries > for the 192.168.1.55 client and my server at 192.168.1.51. Forward > look ups work fine. host 192.168.1.55 gives me: Host > 55.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN) Well, I fixed this.. I accidentally setup my reverse zone as 192.168.1.0 as apposed to 192.168.1. It looks like this also fixed my NFS woes. I wonder why it worked before if I need this now. Hopefully, if it stops working anywhere else someone will come across this, and learn that they now need reverse DNS working to get NFS working. Which is kind of a shame, as I doubt most home users will even have forward DNS setup. =-Jameson -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update Broke NFS Exports
On Fri, Jan 16, 2009 at 8:40 PM, Jameson wrote: >> Is 192.168.1.55 one of the other hosts trying to mount the export? And if >> so, what does 'host 192.168.1.55' command yield at the nfs server? > > Yes, unfortunately it seems to be trying to pull the look up from a > public server, and rejecting it due to it being a private address. I > never bothered with reverse zones, so I don't know why it would need > it now, but not before. Ok, now, I've set up a reverse zone containing just the two entries for the 192.168.1.55 client and my server at 192.168.1.51. Forward look ups work fine. host 192.168.1.55 gives me: Host 55.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN) It looks like this may be my issue, but I have no idea how to fix it. If anyone knows how to make it not bother with the reverse look up, that would be a fine workaround for me, as I said, I don't need reverse DNS for anything else. Thanks, =-Jameson -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update Broke NFS Exports
> Is the rpcbind service is running? Check on both client and server with > /etc/init.d/rpcbind status > if it's not running then start it giving the "start" argument. It is running on both, and I'm actually able to do rpcinfo -p 192.168.1.55 from my server, and get ports listed back, and I can do it in the other direction as well. Thanks, =-Jameson -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update Broke NFS Exports
> Is 192.168.1.55 one of the other hosts trying to mount the export? And if > so, what does 'host 192.168.1.55' command yield at the nfs server? Yes, unfortunately it seems to be trying to pull the look up from a public server, and rejecting it due to it being a private address. I never bothered with reverse zones, so I don't know why it would need it now, but not before. > Updates included bind. Perhaps your private dns is broken. Assuming you do > have a private dns configuration for the private network did you try > 'service named restart'? I'm the only one who uses it for the most part, so I've tried bouncing the whole thing, as well as the clients, but to no avail. I'm thinking about downgrading bind just to verify that this is where the problem is. Thanks, =-Jameson -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update Broke NFS Exports
On Fri, Jan 16, 2009 at 5:26 PM, Jameson wrote: >> Add to the nfs server's /etc/hosts.allow >> mountd:192.168.1.55 >> > > I tried that, but it didn't work. As I said, that file has always > been empty, and it has worked before. > > Thanks, > =-Jameson Is the rpcbind service is running? Check on both client and server with /etc/init.d/rpcbind status if it's not running then start it giving the "start" argument. ~af -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update Broke NFS Exports
> Add to the nfs server's /etc/hosts.allow > mountd:192.168.1.55 > I tried that, but it didn't work. As I said, that file has always been empty, and it has worked before. Thanks, =-Jameson -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update Broke NFS Exports
On Fri, Jan 16, 2009 at 3:52 PM, Jameson wrote: > All of my NFS exports suddenly stopped working last night after > updating my F10 server. The only thing I can think of that has > changed has been the updates. In messages, I'm getting: > mountd Warning: Client IP address '192.168.1.55' not found in host lookup > mountd: connect from 192.168.1.55 to proc (0) in mountd: request from > unauthorized host Add to the nfs server's /etc/hosts.allow mountd:192.168.1.55 the tcpwrappers is preventing the connection. ~af -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update Broke NFS Exports
Jameson wrote: All of my NFS exports suddenly stopped working last night after updating my F10 server. The only thing I can think of that has changed has been the updates. In messages, I'm getting: mountd Warning: Client IP address '192.168.1.55' not found in host lookup mountd: connect from 192.168.1.55 to proc (0) in mountd: request from unauthorized host Is 192.168.1.55 one of the other hosts trying to mount the export? And if so, what does 'host 192.168.1.55' command yield at the nfs server? Updates included bind. Perhaps your private dns is broken. Assuming you do have a private dns configuration for the private network did you try 'service named restart'? -- "A society grows great when old men plant trees whose shade they know they shall never sit in" - Greek Proverb -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Update Broke NFS Exports
All of my NFS exports suddenly stopped working last night after updating my F10 server. The only thing I can think of that has changed has been the updates. In messages, I'm getting: mountd Warning: Client IP address '192.168.1.55' not found in host lookup mountd: connect from 192.168.1.55 to proc (0) in mountd: request from unauthorized host Is there a new layer of security that has been turned on by default, that I need to configure? I've been running without SELinux for pretty much the entire existence of the box. My hosts.allow and hosts.deny have always been empty. I've been doing all of my blocking either through my firewall, or application specific conf files. I'm allowing my entire local network access to the exports in the exports file, and allow all local traffic through the firewall. I'm stumped as to why this would have started now, unless bind was resolving the reverse for my local hosts, but has stopped since the update. Thanks, =-Jameson -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
