Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Help: NFS error (No route to host)
Please help me I am new to this forum and i really need help.
I have set a NFS server and exported the /var/ftp/pub directory to all clients on the network 192.168.0.0/255.255.255.0 and have run the the following commands:
exportfs -a -v
service nfs start
chkconfig nfs on
service portmap restart
chkconfig portmap on
they all where successfuly done, but still when I try to mount this directory
/var/ftp/pub i get the an error message similar to this nfs "192.168.0.254" server down
also I made the same shared directory on a client PC and when I try to mount it from the server i get this error message:
mount: RPC: Remote System Error - No Route to Host
Please Help Me
Last edited by systemhackerz; 07-09-2005 at 05:04 PM.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Well Dont be sad my friend the solution was very easy just disable your iptables
$service iptables stop
If you want this service to keep runing with the NFS just add it as a rule to the iptables allow list
This is ABSOLUTELY NOT good advice. Don't just go turning off iptables unless you know what you're doing. And even if you do know what you're doing it's not a good idea.
The correct answer to this post is to say, it's probably your firewall setup, add nfs tcp/udp to your firewall configuration to allow your client access to the server. If you don't know what that means, dig around a bit, and replace the redhat iptables service with something like shorewall.
The Answer to this as in what the previous person stated is correct. DO NOT just disable IPtables...
the issue is that the NFS needs a tcp/udp port through the firewall on the host from the client. Once the (for testing purposes only) firewall was disabled I was able to mount the NFS share. Next step is to learn which port is needed opening to permit MFS mounting from the client to the host
I'm having the same problem upgrading from RH-9 (Shrike). I have no problem mounting from my old "Shrike" box, but can't connect to the "Werewolf" box unless iptables is disabled.
Looking at the nfs man page, it says
(for option port=n)
The numeric value of the port to connect to the NFS server on. If the port number is 0 (the default) then query the remote host’s portmapper for the port number to use. If the remote host’s NFS daemon is not registered with its portmapper, the standard NFS port number 2049 is used instead.
It would seem, then, that the server would have to have a portmapper running in order to tell the client what port to come in on. Shrike has a portmap service but Fedora does not. Something else must provide this service, but what is it?
By the way, I added 2049/tcp and 2049/udp with system-config-securitylevel to no avail.