no route to host

PenguinHead · 12-30-2004, 11:30 PM

OK... I'm stumped. I can ping my host 192.168.2.150. My host can ping me. However, when I open a SSH session to host (or any session for that matter which are TCP), I get the miserable, "no route to host" from my workstation.

This is a fresh install. The network seems fine from a ping perspective. Any advice? Anyone seen this before? Is it me, or have I lost some basic network troubleshooting fundamentals?

Blah,
Chris

neo77777 · 12-30-2004, 11:45 PM

This is rare to see no route to host, I'd expect timeouts instead. But in any case, edit /etc/hosts and windows host file to include ip's of your workstatations, it is most probably DNS problem, when you try to ssh to a host that cannot resolve the name of the source and/or its own name it will timeout.
Hope it helps.

NetAX · 12-30-2004, 11:46 PM

A firewall can easily block incoming connections. Check your firewall and check to see if the SSH daemon is started.

louis_m_c · 01-01-2005, 09:01 AM

smells like firewall issue. be sure port 22 (or other verify your config, use webmin for that it's great) is open to intranet.

also with webmin you can setup easily SSHd.

Then be sure you have a security service (anything that can generate keys public and private of different types (hdmac-5, RSH, KSH, etc.) i'm not used to that, I can't help much) to keep your ssh session secured.

on my windows clients I've been successful using Putty for X11 takeover of my server

I belive the best how-to for you would be one about VPN as SSH is often talked about in it.

I hope this help a bit

happy new year

againstms · 01-07-2005, 04:57 AM

Okay I have the exact same problem, it seems that it has to be on the machien that I am trying to ssh into because I can ssh into another bo on my network, what do I need to configure on the box I can nto get into, I can however ssh from that box to my box????

browny_amiga · 01-20-2005, 10:45 AM

Try to see if port 22 is open seen from the machine where you cannot login. Use nmap for that. It is not only a portscanner, but also a great security audit tool and connectivity checker:

nmap name-of-the-machine-where-I-cannot-log-in

Nmap is also available for windows and it will show you if port 22 is open.

cheers

Markus

againstms · 01-21-2005, 05:47 AM

Ok, port 22 is open on both achine sbut I still get the same error and can not ssh int the box, but I can ssh into other boxesfine from both systems, just the one machine doesn't seem to allow these sessions...
If I do a nmap localhost I do get the message that port 22 is open for ssh!

louis_m_c · 01-21-2005, 07:21 AM

Make sure SSHd is listening on 192.168.2.150 in your /etc/ssh/sshd_config

if it still aint it send your sshd_config here

spikeroo · 02-02-2005, 12:45 PM

disable /etc/init.d/iptables

oddo · 02-02-2005, 03:03 PM

I suggest these steps to see where the trouble is:

1. netstat -tlnp - to see if sshd is listening and on what interface
2. telnet 192.168.x.x 22 ( the host with the ssh server) to see if you can reach ssh daemon
If not - check firewall
iptables -F
iptables -t filter -I INPUT -m tcp -p tcp --dport 22 -j ACCEPT
( you run this from your sshd server)
If telnet succeded go to step 3.

3. If the machine where you are trying has more than one eth try to see if this one is working
ssh -I 192.168.x.y 192.168.x.x ( if ssh client makes the request from another interface by default, and routes are incorectly configured you will get that message that you complain about)