F8, portmap, 111, and NFS failure

[Amadeus W.M.]

On Sat, 05 Jan 2008 12:39:16 -0700, don fisher wrote:

> I recently installed a new F8 system, similar to what I had done
> previously. The firewall is preventing the export of file systems from
> this system. I have NFS trusted, but the problem appears to be with port
> 111.
> 
> If I attempt to mount the F8 system files (with firewall enabled) on
> system "B" I receive:
> 
> mount -v /dfpc74
> mount: Unable to connect to 192.168.7.4:111, errno 113 (No route to
> host) mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 47097
> mount: Unable to connect to 192.168.7.4:47097, errno 113 (No route to
> host) Exit 32
> 
> With the firewall disabled the mount is successful.
> 
> mount -v /dfpc74
> mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 2049 mount:
> trying 192.168.7.4 prog 100005 vers 3 prot udp port 32771
> 
> 
> What am I missing in my setup. I work from the command line, so please
> reply in a way that is not GUI dependent.
> 
> Thanks
> don

You're missing a message I posted on Jan 1st. Look for "NFS vs the 
firewall". Essentially you must force the rpc services to start on 
predefined ports by specifying them in /etc/sysconfig/nfs, then open 
those ports (udp and tcp) in the firewall besides the nfs port (2049) and 
the portmapper (111).