Wow, here we all are thinking deeply about all the things that could be wrong, but no-one simply suggested to check if sshd was listening, almost like not checking if the power is plugged in when your PC is not working.... :-) Anyways good to see you got it working. -- Thanks Paul Dean. QOTD "Life is not WHAT you make it, it's WHO you have in it..." QOTD: ========================================= You have a strong desire for a home and your family interests come first. ========================================= On Fri, 19 Sep 2008 01:33:56 +0530 "J.Bakshi" <bakshi12@xxxxxxxxx> wrote: >On Thursday 18 Sep 2008 6:35:15 am Bruno Cesar Ribas wrote: >> On Thu, Sep 18, 2008 at 06:09:26AM +0530, J.Bakshi wrote: >> > On Thursday 18 Sep 2008 12:25:17 am Omar Salvador Alcalá Ruiz wrote: >> > > Hi >> > > >> > > You should check if the host exist in the hosts.allow file (commonly >> > > under /etc). If not add it. It should work after that. >> > >> > Just done it but no success :-( hosts.deny is also empty so it can't be >> > the culprit. Openssh is running without any problem with out touching >> > hosts.allow debian may have some different setting to enable sshd but I >> > hv no idea. >> >> let us see the '-vvv' passed to ssh! > >Thanks to everyone who suggest me to fix the Problem. >I have fixed it in a diffeernt way . I have added one line in the sshd_conf >file > >ListenAddress < local IP of the lan card > > >And now I can connect with ssh. > >Thanks to all of you. > > >> I have a bunch of machines running debian[1]. And i get this error only >> when some problem to the rootfs ocurred, such as fs corruption or HD fail >> and / were umounted. >> >> [1]http://yoda.c3sl.ufpr.br/SDI/sumario.html >> >> > > Tell me if it works. Regards >> > > >> > > >> > > >> > > -----Original Message----- >> > > From: listbounce@xxxxxxxxxxxxxxxxx on behalf of J.Bakshi >> > > Sent: Wed 9/17/2008 7:13 PM >> > > To: secureshell@xxxxxxxxxxxxxxxxx >> > > Subject: Debian SSH problem >> > > >> > > Dear list, >> > > >> > > I am managing 3 remote server all based on suse. 2 based on suse 10.2 >> > > and the one is based on suse 11.0. SSH are running on those server >> > > with out any problem. I have recently installed debian lenny in my >> > > home server. The openssh version of lenny is >> > > >> > > OpenSSH_5.1p1 Debian-2, OpenSSL 0.9.8g 19 Oct 2007 >> > > >> > > Now if I try to connect that home server I am getting as below >> > > >> > > ~~~~~~~~~~~~~~~~~~~~` >> > > joy@debian:~$ ssh shiva.selfip.org -v >> > > OpenSSH_5.1p1 Debian-2, OpenSSL 0.9.8g 19 Oct 2007 >> > > debug1: Reading configuration data /etc/ssh/ssh_config >> > > debug1: Applying options for * >> > > debug1: Connecting to shiva.selfip.org [203.171.240.55] port 22. >> > > debug1: Connection established. >> > > debug1: identity file /home/joy/.ssh/id_rsa type -1 >> > > debug1: identity file /home/joy/.ssh/id_dsa type -1 >> > > ssh_exchange_identification: Connection closed by remote host >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~ >> > > >> > > I have never seen such thing in Suse. Could any one kindly suggest me >> > > the reason behind it and how to solve this ? >> > > >> > > Many Thanks > > -- Thanks Paul Dean. QOTD "Life is not WHAT you make it, it's WHO you have in it..." QOTD: ========================================= Give him an evasive answer. =========================================
Attachment:
signature.asc
Description: PGP signature
