Re: RHEL 5.1->5.2 upgrade - part 3

["Robert G. (Doc) Savage" <dsavage@peaknet.net>]

Jason,

It took me a while to get back to this, but I think you are on to
something. I just tried disabling the software firewall on my RHEL5
system (something I RARELY do), and was able to successfully do an NFS
mount from my Fedora laptop.

For some reason the man pages on my Fedora laptop aren't functioning
correctly. 'man 5 nfs' on my RHEL5 system suggests adding "port=0" to
the mount command (or /etc/fstab):

port=n   The numeric value of the port to connect to the NFS server on.
         If the port number is 0 (the default) then query the remote
         host's portnapper for the port number to use. If the remote
         host's NFS daemon is not registered with its portmapper, the
         standard NFS port number 2049 is used instead.

I've tried several combinations of port= and additions to the RHEL5
firewall, but haven't found a combination that works. Is there an
updated NFS wiki somewhere that describes how to link up (new) Fedora
with (old) RHEL5.

--Doc

On Sun, 2008-07-13 at 19:05 -0500, Jason M. Schindler wrote:
> I remember having this problem after a Fedora upgrade before.  I believe
> that it had something to do with certain NFS required services (mountd,
> statd) using random ports instead of static ones.  Try disabling the
> firewall on your RHEL box and see if the client can mount the NFS shares. 
> If so, I believe you have to manually set the desired ports for those
> services and then add the proper exceptions to your firewall.
> 
> Hope this helps.
> 
> -Jason
> 
> 
> > Actually this is a Fedora 8/9 problem, but I'm trying to fix it as part
> > of my 5.1->5.2 upgrade, so...
> >
> > Setting up NFS used to be simple in the old days of Fedora 7 and RHEL4.
> > I'd add the mountables to /etc/exports, run 'exportfs -v' enable and
> > start the portmap and nfs services on the target server. Then I'd
> > edit /etc/fstab on the client, enable and start its portmap service,
> > then 'mount' the desired targets and go.
> >
> > I believe I've done everything required on the RHEL5.2 server. But when
> > I try to do an NFS mount on a client, I get the following error message:
> >
> > $ mount /lion
> > mount.nfs: mount to NFS server 'lion' failed: System Error: no route to
> > host
> > Of course I can ping, ssh to/from, etc. to 'lion' with no trouble at
> > all.
> >
> > The /etc/fstab entry on the client is:
> > lion:/pub   /lion  nfs   rsize=32768,wsize=32768,timeo=14,intr 0 0
> >
> > The server's software firewall is set to allow incoming NFS4.
> >
> > The only real change appears to be the elimination of portmap service in
> > Fedora 8/9. Portmap functionality is now provided by the rpcbind
> > service. Naturally there's no 'man rpcbind'.
> >
> > Where can I find more information?
> >
> > --Doc
> >
> >
> > -
> > To unsubscribe, send email to majordomo@silug.org with
> > "unsubscribe silug-discuss" in the body.
> >
> 
> 
> 
> -
> To unsubscribe, send email to majordomo@silug.org with
> "unsubscribe silug-discuss" in the body.
> 


-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.