All,

I am stuck and need help troubleshooting my problem.

First of all, I disabled SELinux and stopped the firewalld.service on the server and client to eliminate their interference and make it easier for me to troubleshoot the problem.

On the server (LinuxSrv, 192.168.0.8), I made the following changes:

/etc/exports:
/home/data 192.168.0.78(rw,sync,no_root_squash)

/etc/hosts.allow:
portmap: 192.168.0.78
lockd: 192.168.0.78
rquotad: 192.168.0.78
mountd: 192.168.0.78
statd: 192.168.0.78

/etc/hosts.deny:
portmap:ALL
lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL

/etc/hosts:
192.168.0.78 LinuxClt
192.168.0.8 LinuxSrv

If I run exportfs -a -v, I get:
exporting 192.168.0.78:/home/data

On the server (LinuxClt, 192.168.0.78), I made the following changes:

/etc/nfsmount.conf (because my LinuxSrv is old and it has NFS 3):
Nsfvers=3

I ran the following command:
/usr/bin/mount -t nfs -o vers=3 LinuxSrv:/home/data /mnt/data

and got: mount.nfs: No route to host

What am I missing?


I appreciate any help.... Thanks.

Which distro and version is this?

Can the client connect to the servers in other ways, e.g. ping, ssh or ncat?

"no route to host" usually means that the connection request gets lost somewhere between client and server, or that the server doesn't respond (i.e. blocks it). Are you sure the firewall on the server is off? You can check with iptables-save.

berndbausch,

Never mind! I thought I had turned off the firewall on the Server, but it was still on, and it was blocking the 2049 NFS ports.

Thanks

After years of painful and embarrassing errors like this, I keep telling myself: Always double-, triple-, quadruple-check. And then I forget it and run into the same errors again. Such is life.