Hi. I use a socalled Clarkconnect server based oh RH9.0. I very often have used the ssh command the a local machine running SuSE 8.2. If I enter ssh 192.168.1.xxx, I receive this: "ssh: connect to 192.168.1.xxx port 22: No route to host." What does this indicate, and what possible services are maybe not running ?. It came suddenly and so far I'll say, that I haven't touched anything, that could have done it. Advices are more than welcome. -- Med venlig hilsen - Best regards. Erik Jakobsen - eja@urbakken.dk. Licensed radioamateur with the callsign OZ4KK. SuSE Linux 8.2 Proff. Registered as user #319488 with the Linux Counter, http://counter.li.org.
On Tuesday, September 23, 2003, at 01:11 AM, Erik Jakobsen wrote:
Hi.
I use a socalled Clarkconnect server based oh RH9.0. I very often have used the ssh command the a local machine running SuSE 8.2.
If I enter ssh 192.168.1.xxx, I receive this:
"ssh: connect to 192.168.1.xxx port 22: No route to host."
What does this indicate, and what possible services are maybe not running ?.
Possibly.
It came suddenly and so far I'll say, that I haven't touched anything, that could have done it.
Advices are more than welcome.
Did you go to the web interface and enable ssh? Go to a browser and enter https://192.xxx.xxx.xxx:81/ and it will take you to the web interface. You'll have to go to the admin login and turn on all the services you would like to run. Just looking for background info. will
Did you go to the web interface and enable ssh? Go to a browser and enter https://192.xxx.xxx.xxx:81/ and it will take you to the web interface. You'll have to go to the admin login and turn on all the services you would like to run.
Hello will. Yes it has been set the ssh port 22, and have worked fine since long time. But a friend claimed, that he could not enter the normal local computer, and received the same information as I did.
Just looking for background info.
After that, I think the culprit shall be found on the local computer. Do you think so too or ?. -- Med venlig hilsen - Best regards. Erik Jakobsen - eja@urbakken.dk. Licensed radioamateur with the callsign OZ4KK. SuSE Linux 8.2 Proff. Registered as user #319488 with the Linux Counter, http://counter.li.org.
On Tuesday 23 September 2003 01:11, Erik Jakobsen wrote:
Hi.
I use a socalled Clarkconnect server based oh RH9.0. I very often have used the ssh command the a local machine running SuSE 8.2.
If I enter ssh 192.168.1.xxx, I receive this:
"ssh: connect to 192.168.1.xxx port 22: No route to host."
What does this indicate, and what possible services are maybe not running ?.
It came suddenly and so far I'll say, that I haven't touched anything, that could have done it.
Advices are more than welcome.
If this system was working normally before and has just stopped for some reason then I would suspect that either your routing daemen has died or you have a bad network connection in your cable routing somewhere. I had a similar thing happen with my system at work last week and it turned out to be a bad RJ45 cable connection at an HP switch in the network. You might try pinging the remote server from the workstation to see if you can reach it that way. If not, try the following... As root user, you might try running the "route" command to be sure your route is still up and also the "ifconfig" command to be sure your NIC is still configured properly. And, you might try executing "/etc/init.d/network restart" to restart the services on your local machine. If something has died this should restart your daemons and reinitialilze your NICs. Regards, Jack A.
participants (3)
-
Erik Jakobsen -
Jack Alderson -
will