Or if a nameserver in /etc/resolv.conf is not really available --- it can cause timeouts as reverse lookups on the incoming IP address are done...
Make sure your /etc/resolv.conf lists nameservers that are actually reachable.. Scott On Fri, Mar 20, 2009 at 11:30 AM, Mauro Souza <[email protected]> wrote: > Hi George! > > I had this issue in RHEL4 too... > Try this: > > ssh -v u...@host.... > > You will see sshd trying to load lots of auth schemes (even mic, I > think)... > You can then edit /etc/ssh/sshd_config and get rid of the unused auth > schemes... > > Mauro > http://mauro.limeiratem.com - registered Linux User: 294521 > Scripture is both history, and a love letter from God. > > > On Fri, Mar 20, 2009 at 2:28 PM, Shedlock, George <[email protected] > >wrote: > > > We are running SUSE SLES 10 SP 2. When we login to the server via SSH, > our > > pam module that validates the userid against Active Directory completes > with > > a successful logon (as seen on the syslog), but it is some 40-50 seconds > > before we see the logon prompt to the user. Can anyone suggest a course > of > > action to isolate and resolve this delay? Pointers to a logic flow of the > > modules involved would be helpful. > > > > George > > > > ---------------------------------------------------------------------- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO LINUX-390 or > > visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
