Share your knowledge at the LQ Wiki.
Go Back > Forums > Linux Forums > Linux - Networking
User Name
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.


  Search this Thread
Old 09-07-2006, 11:07 PM   #1
Registered: Jan 2005
Location: Montreal, QC, CANADA
Distribution: Red Hat Fedora
Posts: 135

Rep: Reputation: 15
NFS: System Error: No route to host (retrying)

I am configuring NFS for my LAN as following:
The server( has nfs, nfslock, portmap running. The /etc/exports file is:

#this has only one line
On the client(, nfs,netfs,nfslock and portmap are running
The /etc/fstab on the client is:

#the local mount directives is cut           /home    nfs    bg,soft,nfsvers=2  0  0
Trying to mount NFS volume on client give the following error in /var/log/messages:

localhost mount[3323]: mount to NFS server '' failed: System Error: No route to host (retrying).
On the client, issuing
give correct result, dropping rate =0%
On the server,
also give droping rate =0%
Does anyone have any idea what may goes wrong?

PS:The document i used to config NFS is
which also mentions that the client must be able to use host to look up server name and the reverse but does not say how to implement it. Does it actually cause this error?
Hope anyone can give a hint
Old 09-08-2006, 01:57 AM   #2
Registered: Oct 2005
Location: germany
Distribution: debian
Posts: 255
Blog Entries: 5

Rep: Reputation: 30
Have you run
exportfs -ra
on the server to actually to insert the share into the table of exported file systems?
Well, actually this is just a wild guess.
No route to host errors is what I get when I try the wrong IP adress.
Since you can ping, maybe it's a firewall issue?
Are your rpc.nfsd and rpc.mountd started?
Have you tried mounting the share somewhere in /mnt (where it should be)?
What happens when you type
mount -t nfs /mnt
Old 09-08-2006, 08:11 AM   #3
Registered: Jan 2005
Location: Montreal, QC, CANADA
Distribution: Red Hat Fedora
Posts: 135

Original Poster
Rep: Reputation: 15
Hi, thank you for your reply.
I did use

exportfs -ra

serviceconfig shows:

rpc.mountd (pid 1995) is running...
nfsd (pid 1992 1991 1988 1987 1986 1985 1984 1983) is running...
rpc.rquotad (pid 1970) is running...

Try mouting NFS volume manually as you advise yield the same error.
Any other suggestion? Since both user and client use portmap, i guess there's nothing to do with the firewall since we never know what port will be assigned to NFS after the handshaking.
Old 09-08-2006, 11:45 AM   #4
Senior Member
Registered: Jan 2006
Posts: 4,363

Rep: Reputation: 172Reputation: 172

There is a way to force the port to always be the same (that what I had to do). You will also need to check your /etc/hosts.allow file. I think everything you need should be in this link.



Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Help: NFS error (No route to host) systemhackerz Linux - Networking 33 09-13-2012 12:54 PM
No route to host error... alwaysrookie Programming 2 11-04-2005 12:33 PM
rpc remote system error: no route to host scrubbo Linux - Networking 0 09-14-2004 01:48 PM
Error: No route to host! CRB314 Linux - Newbie 1 03-22-2004 03:37 AM
nfs setup on slack 9.1 - no route to host daceo Slackware 2 02-19-2004 05:04 PM > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 08:53 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration