connection refused with upgraded sshd

tfg

Hi,

I just upgraded openssh to version 3.8.1_p1-r1 with emerge.

I used to be able to log in from another computer at the LAN, but that doesn't work anymore since the upgrade.

When I login from localhost it just works fine. When I log in in from another computer (with PuTTY) I get the message:
"Network Error: Connection refused"

No firewall is installed on the computer, and sshd is running.

I suppose it has something to do with this upgraded version, since it worked well before.

Does anyone know what could be the problem ?

Thank you very much in advance for any suggestions.
-tfg

veezi · Apprentice Joined: 10 Nov 2003 Posts: 226

Check sshd config file '/etc/ssh/sshd_config' for anything out of order. The only thing that crosses my mind is the 'ListenAddress' option. You might have '127.0.0.1' in there which prevents you from connecting from outside the machine.

Another thing to check is your PuTTY. Check that it works with other ssh hosts. Try to clear the known hosts file, although it doesn't sound like it's the problem.

Good Luck,

tecknojunky · Posted: Tue Jul 06, 2004 5:06 am Post subject:

... also, check if it's not a ssh protocol version clash. My ssh server uses v2 only and some clients default to v1, so it will fail.
_________________
(7 of 9) Installing star-trek/species-8.4.7.2::talax.

tfg · Posted: Tue Jul 06, 2004 4:16 pm Post subject:

In '/etc/ssh/sshd_config' the 'ListenAddress' option is not set, so by default it should listen to all addresses according to the man page.

I used PuTTY to log in before without any problem. At that time I was also using v2. Even switching sshd to v1 didn't help, I still got connection refused. And there is even nothing in the logs about refusing a connection on the sshd machine.

The only thing I did was upgrading openssh to the newest version with 'emerge -p world'. After that I did 'etc-update', but I don't remeber anything about an update op sshd_config.
Before upgrading everything working well.

-tfg

tfg · Posted: Tue Jul 06, 2004 5:08 pm Post subject:

Problem solved!

It happened to be multiple different problems which resulted in the same error message. The problems were the connection settings in the other machine at the LAN, and a problem in the firewall of the LAN (computer had been reset with old firewall settings) when connection from outside the LAN.

-tfg