Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
No route to host means that your local host is unable to talk to the address 192.168.1.136 for some reason.
First diagnose your local network, "ifconfig -a"
If you do not have an attachment to a 192.168.1.xxx network, then that's problem #1.
If you have an address on that network, or a viable class B or C address, then try a ping. Try first pinging the router, "ping 192.168.1.1", if that doesn't work. Ping your own IP address, which is the address shown by the ifconfig command. Note if your address is something like 169.<something>.<something>.<something> then that's a DHCP failed address assignment and it's not a real address. A real address is typically 192.x.y.z, or 10.x.y.z, but there are others. The "self" address is 127.0.0.1 which means "loopback", you can ping that address to verify that your IP stack is running at all.
If you have a local IP problem, then you need to resolve that before you can talk to that remote system. If your system is fine from an IP and network connection status, then perhaps you cannot reach the remote system. Ping that system's IP address, and also try ping -R to show the route.
No route to host means that your local host is unable to talk to the address 192.168.1.136 for some reason.
First diagnose your local network, "ifconfig -a"
If you do not have an attachment to a 192.168.1.xxx network, then that's problem #1.
If you have an address on that network, or a viable class B or C address, then try a ping. Try first pinging the router, "ping 192.168.1.1", if that doesn't work. Ping your own IP address, which is the address shown by the ifconfig command. Note if your address is something like 169.<something>.<something>.<something> then that's a DHCP failed address assignment and it's not a real address. A real address is typically 192.x.y.z, or 10.x.y.z, but there are others. The "self" address is 127.0.0.1 which means "loopback", you can ping that address to verify that your IP stack is running at all.
If you have a local IP problem, then you need to resolve that before you can talk to that remote system. If your system is fine from an IP and network connection status, then perhaps you cannot reach the remote system. Ping that system's IP address, and also try ping -R to show the route.
Hi, i have checked ifconfig , my internet connection is fine.
my server and my desktop are on the same network
in fact, i am able to ssh 192.168.1.136 . but unable to showmount
any helps pls?
service nfs status
exportfs -v
rpcinfo -p
showmount -e localhost
desktop
Code:
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
server
Code:
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 111 -j ACCEPT
COMMIT
#-A RH-Firewall-1-INPUT -m state --state NEW -m tcp --dport 111 -j ACCEPT
#-A RH-Firewall-1-INPUT -m state --state NEW -m tcp --dport 2049 -j ACCEPT
Quote:
service nfs status
Code:
rpc.svcgssd is stopped
rpc.mountd (pid 3670) is running...
nfsd (pid 3735 3734 3733 3732 3731 3730 3729 3728) is running...
rpc.rquotad (pid 3666) is running...
Re iptables; its a first match system, so on the INPUT chain, the REJECT rule must come last
Code:
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 111 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
you'll need
Code:
service iptables restart
after changing that file.
Technically its not really a service, but its treated like one...
hi chrism01
i have move the input above of reject already
and i have restart the table
but still unable to showmount -e
but now i am able to rpcinfo -p 192.168.1.136
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.