SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
i just finished compiling a slack 10 box to 2.6.0... right after it came up on the network, i couldn't login remotely using SSH. i can SSH out of the box to another machine but when i try to connect using SSH to that machine it gives me this message:
ssh: connecto to host 192.168.1.103 port 22: Connection refused.
what can i do to fix this as i need to login to this box remotely because it doesn't have a monitor or a mouse or a keboard.
Did you generate a key-pair? ( On both computers )
Is the sshd daemon running?
Is port 22 open ( firewall settings )
Given the '192.168.' address, I'm assuming that you are trying to
access it from a machine on the local network.
You could add the public keys to the authorize_keys files on both computers.
This way, you wouldn't have to enter a pass-phrase. I believe you need generate rsa keys
for this to work.
One thing that could happen is if the wrong permissions are on the private key.
The server will refuse connections in that case.
Another possibility that I think could happen is if the IP address was used by a different computer before
you installed this one. However, I think that would more likely be the case if you changed things at the
client computer. But in any case, you could try deleting any information about the client at the server, and
information about the server on the client computer, in the known_hosts file. In effect, starting fresh on both ends.
I don't remember where the connection failures are logged, but it may contain the information on why the connection was refused.
There are several types of authentication, so you need to read through the man pages for 'ssh' and 'sshd'.
But if you need to get this connection working fast,
A) Make sure the sshd daemon starts.
B) Check the firewall. Does it allow local network ssh connections (port 22).
C) Generate new keys with ssh-keygen and use the RSA type key.
D) Add the contents of the ~/.ssh/id_rsa.pub file to the other computers ~/.ssh/authorized_keys
I hope this helps. There are things in site wide configuration configuration files in /etc/ssh/ that could cause a connection to be refused.
You would need to study them against the man pages to find out.