Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have two machines, first one running RedHat enterprise linux 5 and second one running RedHat Enterprise Linux 4. I have connected these two machines via LAN. I have been attempting to set up NFS (Network file system), hence the first machine has been made the server and the second machine the client. The IP address of the server is and the IP address of the client machine is

On the server machine I have written the following in /etc/exports file:


When I attempt to mount the server directory from the client machine using the following command

mount -t nfs -o rw /home/ivv/test

I get the following error (on the client machine)

***mount:mount to NFS server '' failed: System error: No route to host.***
share|improve this question
Maybe verify that the firewall and selinux is set accordingly on the server. – ssteidl Nov 3 '09 at 13:32

A little more information would be handy:

  • Can you ping between the two servers?
  • Have you restarted NFS on the server after you added the entries to /etc/exports?
  • What (if anything) do you see in the NFS server's logs when the client tries to mount?
share|improve this answer

Try to find out weather this is a networking problem or something related to nfs. A simple netwoking test is to ping to the other host. Ie: "ping otherhost". (To make thingns easier, add the hosts to the /etc/hosts file of both computers.) To test nfs, you can also try to nfs mount the export on the nfs server itself.

ps: reading silent's answer, if it's the firewall, allow udp traffic as well.

share|improve this answer

Either your network is totally boned (RainyRat's ping suggestion will tell you this), or else the firewall on one (or both) machine(s) is configured not to let NFS traffic through. I don't think this is likely given the error message ("No route to host" isn't a common firewall-related error) but it's possible, and worth checking.

share|improve this answer

And try to add the firewall exception

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.