This is because of DNS resolution, and to test my theory Vi /etc/hosts And add the host in there you are ssh'ing from and this will get rid of it. But of course the proper thing to do is find out what is going on with DNS resolution. -----Original Message----- From: Hans du Plooy [mailto:hansdp@newingtoncs.co.za] Sent: Wednesday, August 18, 2004 4:32 AM To: suse-linux-e@lists.suse.com Subject: [SLE] Slow SSH login Hi all, We just replaced our office mail/file/web server (P-II running SUSE 9.0 Pro) with a faster machine. I loaded SUSE 9.1 Pro. Everything is working fine, except for one detail. When I ssh into it, there's a delay of about 6 seconds before I get a password prompt. The password prompt was instant on the older machine. I don't see anything in the config files, and the logs don't give me anything useful either: Aug 18 09:57:03 eos sshd[23798]: Accepted keyboard-interactive/pam for hansdp from ::ffff:192.168.16.25 port 60847 ssh2 Any ideas where to look? Thanks -- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wednesday 18 August 2004 13:12, Elijah Savage wrote:
This is because of DNS resolution, and to test my theory
Vi /etc/hosts
And add the host in there you are ssh'ing from and this will get rid of it.
That worked, thanks a lot. What is your theory, specifically? My workstation wasn't in the old server's hosts file, and I didn't have the delay. DNS setup is exactly the same on both machines - our firewall first, then two of the ISP's DNS servers. -- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
Hans wrote regarding 'Re: [SLE] Slow SSH login [solved]' on Wed, Aug 18 at 06:27:
On Wednesday 18 August 2004 13:12, Elijah Savage wrote:
This is because of DNS resolution, and to test my theory
Vi /etc/hosts
And add the host in there you are ssh'ing from and this will get rid of it.
That worked, thanks a lot. What is your theory, specifically? My workstation wasn't in the old server's hosts file, and I didn't have the delay. DNS setup is exactly the same on both machines - our firewall first, then two of the ISP's DNS servers.
Perhaps the server has updated to a newer version that does a double lookup on the connecting machine, while the old version only looked up the IP, and the additional forward lookup is not responding at all / as quickly as it should? --Danny
On Wednesday 18 August 2004 21:59, Danny Sauer wrote:
Perhaps the server has updated to a newer version that does a double lookup on the connecting machine, while the old version only looked up the IP, and the additional forward lookup is not responding at all / as quickly as it should?
That sounds possible, except that I have tested this with three different SUSE 9.1 Pro machines, all running the same versions of everything, all having exact same (default) config, and it's only the one box that does this. That's why I'm wondering if there isn't anything else (like some obscure network issue) that's playing up. I just don't know where to look. I have checked my network settings, and all appears fine. Thanks -- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
Hans wrote regarding 'Re: [SLE] Slow SSH login [solved]' on Thu, Aug 19 at 03:11:
On Wednesday 18 August 2004 21:59, Danny Sauer wrote:
Perhaps the server has updated to a newer version that does a double lookup on the connecting machine, while the old version only looked up the IP, and the additional forward lookup is not responding at all / as quickly as it should?
That sounds possible, except that I have tested this with three different SUSE 9.1 Pro machines, all running the same versions of everything, all having exact same (default) config, and it's only the one box that does this.
That's why I'm wondering if there isn't anything else (like some obscure network issue) that's playing up. I just don't know where to look. I have checked my network settings, and all appears fine.
Do all of the hosts have proper forward and reverse DNS entries? If the machines are all identically configured, then it's obviously something else. :) You might also check your known_hosts and authorized_keys to make sure there isn't some key that's being tried first. Maybe even stick a -v or two on your ssh command to see what exactly's going on from the client side. --Danny
participants (3)
-
Danny Sauer -
Elijah Savage -
Hans du Plooy