NFS problem

[Gerhard Magnus]

On Mon, 2008-03-24 at 10:38 -0600, Aaron Konstam wrote:
> On Sun, 2008-03-23 at 17:43 -0700, Gerhard Magnus wrote:
> > I'm trying to set up an NFS file server on one of the boxes on my LAN
> > and have gotten stuck. On the server, I used system-config-nfs to create
> > the following /etc/exports file:
> > 
> > /home/magnusg/music  192.168.1.11(rw,sync) 192.168.1.12(rw,sync)
> > 192.168.1.13(rw,sync)
> > 
> > to allow the other three boxes r/w access to the
> > directory /home/magnusg/music on the server (192.168.1.14).
> > 
> > Also on the server, I used system-config-services to start nfs and
> > nfslock on run levels 3 and 5. Then I checked NFS4 on the firewall
> > configuration widget system-config-firewall to open tcp and udp ports
> > 2049. Then I rebooted the server.
> > 
> > On one of the clients I then did (as root):
> > 
> > mkdir /mnt/PuteF
> > mount 192.168.1.14:/home/magnusg/music /mnt/PuteF
> > 
> > and got the error message:
> > mount: mount to NFS server '192.168.1.14' failed: System Error: No route
> > to host
> > 
> > I'm guessing I need to open more ports, but which ones and where? The
> > four boxes are connected to a Linksys router.
> > 
> No route to host sounds more like a connection problem. You can ssh between the machines?
> --
ssh works fine. I've been googling this problem and found that other
people have had it and it may be a serious bug. Could it be that NFS
doesn't work in fedora and that everybody uses samba anyway?