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 accidental
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(NX
> 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 rev
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
> 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 d
> 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
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
> 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/listinf
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 foun
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 19
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 pro
11 matches
Mail list logo
