Hi List! I have a problem with ssh. I reinstalled Suse 8.0 and I have a problem with ssh'ing some computers (strangely some other work), which I did not have before. I always reveive a "ssh_exchange_identification: Connection closed by remote host", when ssh'ing certain machines. Detailed information:
ssh -v fuzzy.mcs.csuhayward.edu OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f debug1: Reading configuration data /usr/local/etc/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: needpriv 0 debug1: Connecting to fuzzy.mcs.csuhayward.edu [134.154.14.232] port 22. debug1: Connection established. debug1: identity file /home/gandalf/.ssh/identity type -1 debug1: identity file /home/gandalf/.ssh/id_rsa type -1 debug1: identity file /home/gandalf/.ssh/id_dsa type -1 ssh_exchange_identification: Connection closed by remote host debug1: Calling cleanup 0x80642f0(0x0)
I thought that the problem might be in /etc/hosts.allow/deny but they look like: /etc/hosts.allow: ALL: ALL /etc/hosts.deny: (no entries) As some ssh connections work. I thought, I might have the wrong version and so I uninstalled the Suse rpms and compiled/installed the newest OpenSSL and OpenSSH versions (3.5), the problem remains the same. An ftp does not work either:
ftp -v fuzzy.mcs.csuhayward.edu Connected to fuzzy.mcs.csuhayward.edu. 421 Service not available, remote server has closed connection.
This makes me think it might be a problem with the hosts-files but I can't figure it out. Does anyone know how to help me? Thanks a lot, Philipp Jenke -- ********************* * www.p-jenke.de *********************
Hi All Thanks for all the answers.
You didn't backup your old ssh configuration? No, I did not, my bad.
i think the answer is in the logfiles of your server, so please check them and show us.
Could you tell me, which logfiles I have to look for? I also tried the win-ssh implementation "putty" - the same problem, so I think you are right that it is less likely a problem with my computer, but with the server. Philipp -- ********************* * www.p-jenke.de *********************
On Wed, Mar 05, 2003 at 10:20:25AM +0100, Philipp Jenke wrote:
i think the answer is in the logfiles of your server, so please check them and show us.
Could you tell me, which logfiles I have to look for?
on suse this would be /var/log/messages as usual, and probably /var/log/warn for unsuccessful ssh atempts. if public key authentication fails, it is likely a permission problem on the $HOME and/or $HOME/.ssh/ od $HOME/.ssh/* directories/files. sshd is picky about ownership/write permissions there. and it is right ;) hth, Lars
I have a problem with ssh. I reinstalled Suse 8.0 and I have a problem with ssh'ing some computers (strangely some other work), which I did not have before.
I always reveive a "ssh_exchange_identification: Connection closed by remote host", when ssh'ing certain machines.
You didn't backup your old ssh configuration? Then at least the host keys and probably the configuration settings have changed. It could be that other hosts refuse connections since your host id is changed and they think someone is doing a man-in-the-middle attack. Perhaps? Differences in default authentication methods and those required by various hosts could be a reason too - I guess... timo
Hi Philipp, Philipp Jenke schrieb:
Hi List!
I have a problem with ssh. I reinstalled Suse 8.0 and I have a problem with ssh'ing some computers (strangely some other work), which I did not have before.
If you get a connect for 'telnet hostxxx 25' but no sshd banner it might be a routing problem. Did you forget to set some routes in route.conf. May be the update has overriden route.conf - look for route.con.rpmsave ...
An ftp does not work either:
ftp -v fuzzy.mcs.csuhayward.edu
Connected to fuzzy.mcs.csuhayward.edu. 421 Service not available, remote server has closed connection.
It looks like a routing problem ... Andreas Tirok --
participants (5)
-
Andreas Tirok -
Lars Ellenberg -
Philipp Jenke -
Sven 'Darkman' Michels -
timo