• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1250
  • Last Modified:

Can't connect through SSH

I am new to Linux.  I just installed redhat 7.2 server, but I can't connected to this server through ssh.  I have checked openssh-2.9p2-7 has been installed on the server, and sshd is running.  What should I do to make it work?  Thanks!
0
Vincenthkl
Asked:
Vincenthkl
4 Solutions
 
slaxsCommented:
Hi Vincenthkl,

To connect to an OpenSSH server from a client machine, you must have the openssh-clients and openssh packages installed on the client machine.

Im guessing you installed the openssh-server package?


Slaxs



0
 
slaxsCommented:
You must install OpenSSH server (openssh-server) the client (openssh-clients) packages, as well as the general OpenSSH package (openssh) for either of them to work. Hope this helps.
0
 
robsmartCommented:
might be that your firewall is blocking port 22 ?? check your firewall settings.
0
Managing Security & Risk at the Speed of Business

Gartner Research VP, Neil McDonald & AlgoSec CTO, Prof. Avishai Wool, discuss the business-driven approach to automated security policy management, its benefits and how to align security policy management with business processes to address today's security challenges.

 
joele23Commented:
If you are just having problems connecting from a remote machine try using ssh2.
Ive notice a lot of times if I cant ssh in and I try ssh2 it works fine.
0
 
ferg-oCommented:
What user account are you using to connect? If you want to use root it is turned off by default in /etc/ssh/sshd_config - you will need to change the line:

PermitRootLogin no
to
PermitRootLogin yes

Some people don't like to allow root to login remotely due to brute force considerations so another way around it is to create another user using the useradd command and then connect via SSH with that and su to get root access...

Also you can limit access to ssh using /etc/hosts.allow and /etc/hosts.deny - I suggest reading up on those files if you are new to unix.

Good luck!
0
 
jlindqCommented:
To trouble-shoot try "telnet [host IP] 22" to connect to port 22 using telnet. If the SSH service is running and not filtered anywhere along the netowrk path you should get a SSH banner (e.g. "SSH-1.99-OpenSSH_3.7.1p2"). (Pressing Return will generate a protocol error and take you back to the prompt.)
If this works, the daemon is up and running and you can contact it. You then need a SSH client (OpenSSH or any other SSH client should do.)

If it doesn't work, I'd suggest trying it locally on the machine, both "telnet localhost 22" and "telnet [Host IP] 22" to see if you can connect locally. If you can't, there is some network filtering (firewalling) in place between the client and server.

You can also start sshd with the -d debug flag. It will then not spawn into daemon mode but run one single process withotu forks anbd output debug messages on the server that you can watch.

0
 
ferg-oCommented:
Another one bites the dust.

People who post questions, receive answers or request for more info to help the answer, and do not close them out should be penalised methinks?
0

Featured Post

The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now