Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is more of a curiosity question then a problem at this point. I have resolved my problem which i'll post the solution that worked for me.


I was getting rather slow authentication times when i attempted to log in from a windows 7 box (using putty) to a linux RHEL5 box. The initial connection request was fast. however, after typing in my username, the authentication time was very slow (exponentially obnoxious with my git pushes).


I checked the logs and found ssh attempting to use GSSAPI authentication. my 20 second authentication timeout was obvious. i simply adjusted putty (and egit) to not use GSSAPI authentication. Login and authentication times were normal.

the question

my RHEL box was never touched. SSH configs (and timestamps confirmed) have not changed since over a year ago. My putty settings were never changed and AFAIK GSSAPi auth is defaulted to on in putty. I'm just incredible curious if anyone else has seen this issue? if GSSAPI was failing in the past because i don't use that feature, why all of a sudden did the timeout kick in and slow me down?

share|improve this question

I think it is more probably a DNS issue than GSSAPI. sshd likes prompt DNS responses to work promptly during connection phase... cause of logging and access checks.

share|improve this answer
i'll upvote you but do you have proof of this? it could be very related to useDns no which i have set and works. See related post – au_stan Aug 16 '12 at 11:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.