ssh: connect to host <ipaddress> port 22: Connection refused

K-radical · 2010-07-31 13:19:37

I'm experiencing something very weird and I honestly don't know what to make of it. So I've got two machines; 'server' and 'workstation'. Server is running sshd configured (to the best of my knowledge anyways...) properly. Every time I reboot the server itself or restart /etc/rc.d/sshd, I am unable to ssh to it from workstation.

Workstation reports the error in the title of this thread.

This happens every single time, so all I have to do to fix it is ping workstation from server. After that it can ssh to it no problem. Why is this? How can I resolve this so the initial ping is not needed?

Thanks,

ewaller · 2010-07-31 15:44:30

Two questions:
1. In the failed condition, can you ping the server from the workstation?
2. What is the architecture of the network ? ( Wireless?, Router? Cross over cable?)

ralvez · 2010-07-31 16:15:42

I'm assuming that the server part is OK, based on your explanation of the problem;however, you should also add in the server in /etc/hosts.allow the following:
(this assumes that you want to give access to your client machine with an address of 192.0.168.1.23)
sshd:192.0.168.1.23

Notice that this grants access to the machine with the specific address.
You could make the server open to anyone by using:
sshd:ALL

but that is not advisable.

Hope this helps.

Ricardo

ewaller · 2010-07-31 17:05:04

I agree with almost everything ralvez said, and all of that should be necessary. The fact that you can, eventually, establish a ssd session tells me that may already be in place.

My concern is whether the network knows how to discover the route from the workstation to the server without first getting a clue from the server side my initiating a transaction first.

ralvez · 2010-07-31 17:09:37

ewaller wrote:

I agree with almost everything ralvez said, and all of that should be necessary. The fact that you can, eventually, establish a ssd session tells me that may already be in place.
My concern is whether the network knows how to discover the route from the workstation to the server without first getting a clue from the server side my initiating a transaction first.

I think you have made a very good point here ... and it made me think
I wounder if K-radical has setup his /etc/hosts in his workstation.

R.

Last edited by ralvez (2010-07-31 17:09:58)

.:B:. · 2010-07-31 21:53:04

You can always use the -v switch for verbosity when trying to ssh to your server. 'Connection refused' can mean a lot of things, from sshd not running on that port, to not being active on the server at all, or to refusing a connection because it only accepts keys instead of passwords, ...

It's a bit like saying 'hey, my computer doesn't work!'

Arch Linux

#1 2010-07-31 13:19:37

ssh: connect to host <ipaddress> port 22: Connection refused

#2 2010-07-31 15:44:30

Re: ssh: connect to host <ipaddress> port 22: Connection refused

#3 2010-07-31 16:15:42

Re: ssh: connect to host <ipaddress> port 22: Connection refused

#4 2010-07-31 17:05:04

Re: ssh: connect to host <ipaddress> port 22: Connection refused

#5 2010-07-31 17:09:37

Re: ssh: connect to host <ipaddress> port 22: Connection refused

#6 2010-07-31 21:53:04

Re: ssh: connect to host <ipaddress> port 22: Connection refused

Board footer