Hi, Have you tried removing the existing hostkey's from your know_host file on the client ?
Maybe your client is to strict, it sees a different key than expected and kicks you out. So delete exeisting know keys for 23.42.23.42 on your client en try to reconnect. look in ~/.ssh.known_host or ~/.ssh.known_host2 - Wouter [On 28 Jun, 2002, Andreas Syksa wrote in "YASP (Yet Another SS ..."] > Hello List, > > I got a nasty problem after I've updated my OpenSSH to > Version 3.3: > > Right after the update everything worked fine for me. > I could connect to the server - tested everything - fine. > At home, with my laptop in my bed I connected last time > and was suddenly kicked out. > > I was not able to reconnect an thought: time to sleep now. > The day after I realized: I've got a problem: > > ################################################### > [EMAIL PROTECTED]:~> ssh -v -v 23.42.23.42 -l moeppel > OpenSSH_3.0.2p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Applying options for * > debug1: Seeding random number generator > debug1: Rhosts Authentication disabled, originating port will not be trusted. > debug1: restore_uid > debug1: ssh_connect: getuid 500 geteuid 0 anon 1 > debug1: Connecting to 23.42.23.42 [23.42.23.42] port 22. > debug1: temporarily_use_uid: 500/100 (e=0) > debug1: restore_uid > debug1: temporarily_use_uid: 500/100 (e=0) > debug1: restore_uid > debug1: Connection established. > debug1: read PEM private key done: type DSA > debug1: read PEM private key done: type RSA > debug1: identity file /home/slupp/.ssh/identity type -1 > debug1: identity file /home/slupp/.ssh/id_rsa type -1 > debug1: identity file /home/slupp/.ssh/id_dsa type -1 > debug1: Remote protocol version 2.0, remote software version OpenSSH_3.3 > Debian 1:3.3p1-0.0potato2 > debug1: match: OpenSSH_3.3 Debian 1:3.3p1-0.0potato2 pat ^OpenSSH > Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_3.0.2p1 > debug1: SSH2_MSG_KEXINIT sent > Connection closed by 23.42.23.42 > debug1: Calling cleanup 0x80640b0(0x0) > ################################################### > > I've tried it with "ssh -1" as well as with "ssh -o" > but without any success. > As my machine is located at an ISP I've no chance > to get to the console. A bit scary is, that it worked > fine for several logins from Windows / Putty and > Linux with ssh-clients below 3.3 (as seen above). > > The system has all patches / new versions of software > available installed (Apache, Bind, mod_ssl, Proftpd...) > Any idea what might have happend? > > thanks a lot, > Andreas > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Wouter van Gils -=- [EMAIL PROTECTED] http://the-construct.cx/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]