SSH takes a long time (2 minutes) to connect
 

I have a linux box and whenever I try to connect to it, it takes a long time( 2 minutes) to connect using ssh from any other machine (even on the same LAN) before the prompt for password comes up. Then I tried sshing the machine from the same machine and even that took the same time. I ran ssh with the verbose option and it seems that a lot of time is spent on the

debug1: identity file /home/mani/.ssh/id_dsa type -1

line before

debug1: Remote protocol version 1.99, remote software version OpenSSH_3.5p1
debug1: match: OpenSSH_3.5p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.5p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
......

appear and I get logged on

This is where the ssh gets stuck seemingly.

OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to crestlab34.ece-int.gatech.edu [192.168.26.23] port 22.
debug1: Connection established.
debug1: identity file /home/mani/.ssh/identity type -1
debug1: identity file /home/mani/.ssh/id_rsa type -1
debug1: identity file /home/mani/.ssh/id_dsa type -1


If someone can help me with this problem, I would really appreciate it.

Thanks in advance.

Anyone has any suggestion?:(


Thanks.

Not sure ... but I wonder if it's timing out trying to do a reverse DNS lookup. Do you have DNS or an /etc/hosts entry that resolves the name of the host you are connecting from?

turn off the option to do reverse hostname lookups.



hope i could help!!!!




:Pengy:

Yes, I actually I had done that because I had read about it. But, that did not seem to help.

Thanks though.

Looking at your first post again, maybe it's something with the id_dsa file it's trying to look at in your .ssh directory. Does such a file actually exist? If so it might be trying to do authentication with DSA public key encryption, and then falling back to password authentication. This is just a guess, but did you ever try to get something like that set up?