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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
if you dont have rlogin (and the remote host wouldnt most likely allow access with those anyways) you could allways install them? Atleast in Slackware it comes with the tcpip package.
If thats not an option, then your last few hopes are:
1. telnet. Its most likely off or blocked, but worth a try
2. root ftp / nfs - This is a sneaky trick, if you can get access to the partitions somehow (ftp or nfs or similar filetransfer protocols) and sneak a script (shellscript that starts the sshd) into the hourly cron directory, sshd will start on the next cron hourly.. Well, asuming the remote host has crond running ofcourse..
I cant think of anymore computer related answers, but calling someone at the machine is prolly the easiest way.. And when you do get access, put the sshd into rc.local to start it automagickly.. save ye alot of hassle.. (:
Having another remote connection protocol, like telnet or rsh, kinda defeats the purpose of using ssh in the first place. It would be easier, and safer, to get ssh to start on boot than to get one remote connection protocol running just so you can use that to start another remote connection protocol like ssh.
What I would do is find what distribution is running on the remote system and then find out what method is used to make that distro start ssh automatically.
If I understand it right, the remote system gets rebooted and sshd isn't starting on boot. If that's the case then you need to turn on the startup script for sshd. You could set up a cron job to start the service, but you only have to do that if it's getting shut off some other way besides a reboot, such as being manually disabled or crashing. If all you need to do is make sure sshd is starting on boot, then it should be a simple command like chkconfig sshd 3 5 (that may not be the exact syntax, check the man page for your distribution.)
indeed the first priority would be starting in on boot. I just asumed the situation was that you have no physical access to the machine. In that case, the cron method is nice IF you have access to the partitions some way eventhough you dont have ssh. I had a situation where my server threw a total tantrum, disabling every local tty and killing sshd. I still had the root partition nfs mounted on a different machine, so I could sneak in a cron task to /etc/cron.hourly/sshd.sh with the script as:
The "hourly" crons are run every hour, so I just had to wait 30 mins for that to come up, and voila, sshd was back online. The directory structure is Slackware specific, but other distros have similar systems. One cannot sneak in a normal crontab entry as they are stored in a temorary file that is created when you execute crontab -e. Thus, it is imo impossible to remotely without a shell, make a normal crontab entry. Thus, you have no need to know what the local time there is, only when the next hourly crontab will be run.
But, thats just a quickfix. Enabling the init script for it is the permanent way to go. If your distribution uses the BSD style init:
chmod +x /etc/rc.d/rc.sshd
If youre on a SysV init style distro, I cannot advise you, but most distros are SysV, so someone will surely be able to help you with that.
Well, that became quite a long post for a simple matter, hmh, well, back to my morning tea.. d: