I am trying to connect to a solaris server using putty from a windows client. SSH connection is not working. The terminal window just gives an error message "Network error:Connection refused". Telnet using putty is working fine with the same server. Can someone please detail what configurations needs to be checked in this case? How to troubleshoot? (There are other servers in the same network which allows SSH connection.)
Here is a series of steps you can use to diagnose the problem:
- Check if sshd is running on the host(ps -ef|grep ssh)
- Ensure that sshd is binding to port 22 using netstat (netstat -al|grep "LISTEN " should work)
- See if you can connect to the real IP address via ssh from the host machine (if not, there is either a local firewall, or sshd is not working as it should
- Try to ping the host from the client machine (if this fails, there is a routing problem)
- Try to telnet to port 22 from the client machine (telnet 192.168.1.1 22) (if this fails, a firewall is blocking you)
- Finally, if all the above succeed, but you cannot ssh using the ssh client - re-install your ssh client.
Check if there isn't a firewall between you and the server.
I know it seems a very obvious check. But have you confirmed that your Solaris server has a sshd running? Once you have telneted to the machine run netstat to see if it is listening on the ssh port (port 22). If it is then you next port of call will be to check /etc/hosts.allow and so forth as MathewC suggested
If you confirm ssh is running on the machine, you may want to check if the client machine you're trying to connect from can see port 22 as open using nmap.
nmap -p22 [solaris-box-ip]
If this is Solaris 10, check if SSHD is running by issuing the
svcs -p ssh command. That'll tell you if SSH is running, and, if not, why (maybe a dependancy failed for some reason, or maybe it was disabled).
You can enable SSH by issuing
svcadm enable ssh
Connection refused means the service is running but you don't have access.
You might need to also run
inetadm -m network/telnet:default tcp_wrappers=TRUE
to add on to the list of checks, use
svcs -xv to check if there are any failed services, and if ssh is one of them. This gives you a breakdown on why the service failed as well.
protected by HopelessN00b Mar 10 '16 at 10:48
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?