SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
nfs setup on slack 9.1 - no route to host sorted!!
My small problem. having set up a nice server running slack 9.1 nfs, I originally had 2 pcs connecting in to it and it works fine, with read write access etc. So I want to add another box, and it stubbornly refuses to allow the new machine to connect. the other two are fine. the new machine is all there, it can access the internet through my gateway/router, I can log in to it from another pc, it is possible that I am missing a service on it, but i think that it is at the server that the problem is. The error on message on boot up of the new machine is:
root@slacky:~# /sbin/mount -a -t nfs
mount: RPC: Remote system error - No route to host
if I do show mount:
root@slacky:~# showmount -e 192.168.0.10
Export list for 192.168.0.10:
where 192.168.0.50 is the machine I am trying to get working
me rpc info says
root@slacky:~# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
I was looked at the rpcinfo for the server, and after the portmapper, it has rquotad, could I be missing this?
I have added all three machines to the host.allow but this did not make any difference.
root@serviette:~# cat /etc/exports
# See exports(5) for a description.
# This file contains a list of all directories exported to other computers.
# It is used by rpc.nfsd and rpc.mountd.
the hosts allow looks like:
root@serviette:~# cat /etc/hosts.allow
portmap: 192.168.0.20, 192.168.0.30, 192.168.0.50
# End of hosts.allow.
I am fairly new to all this, so I may have omitted to do something obvious..
I am glad it was a can't see the wood for the trees human error problem with a nice simple soluttion... (yes it is working now). I am slightly jaded, but also better educated in nfs, after having spent hours unsucsessfuly trying to get fedora core 1 to be an nfs server more than once without restarting everything, and failing. slack is so painless in comparison....