public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Peter <mandango@freenet.de>
To: cygwin@cygwin.com
Subject: Re: cygwin ssh login long login delay while showing "last login"
Date: Thu, 06 Aug 2015 17:19:00 -0000	[thread overview]
Message-ID: <55C39689.5080202@freenet.de> (raw)
In-Reply-To: <1438879959.34691.ezmlm@cygwin.com>

On 06.08.2015 18:52, cygwin-digest-help@cygwin.com wrote:
>
> Peter writes:
>> >I have installed the cygwin ssh daemon on my w7 box with cygwin64.
>> >
>> >When I try to login I always get a long delay or timeouts on the client
>> >side.
>> >
>> >I get quick response for the password and then a showing "Last login: ..."
>> >
>> >At this point the connection hangs for about 30s to 1min before I
>> >finally get a login .
>> >
>> >This is what it shows when I try to do an ssh to my local host from my
>> >local host:
>> >
>> >$ ssh testuser <at> myw7host
>> >testuser <at> myw7host's password:
>> >Last login: Thu Aug  6 12:46:23 2015 from 128.139.80.101
>> >
>> >The password request and the Last login is almost instant but then it
>> >hangs for about a minute before I get the login .
>> >
>> >I also tried to ssh testuser <at> localhost or testuser <at>
> 128.139.80.101  but
>> >the effect is the same.
>> >
>> >How can I troubleshoot the issue?
> It's unclear to me whether you're saying the delay is in completing the
> "last login" line (and showing the IP address) or the delay is after the IP
> address is shown and before you get a shell prompt.  If it's the first of
> these, it sounds like there's a DNS timeout trying to find the machine name
> for that address and failing.  If it's the second of these, I would suspect
> something in one of the profile or login files for the shell involved.
>
> ..mark
>
Sorry for the confusion.
As I said I get quick response for the password and then that line 
showing the "Last Login: ..." stuff.
At this point I suppose that connection to the sshd has been established.
So I go with your suspicion about the profile or login files of the shell.
The thing that puzzles me ist that I do it from localhost to localhost 
and opening a cygwin terminal with bash on localhost takes less than 2 
seconds.
 From my understanding the login/profile stuff should be almost the same.
One thing that comes to my mind is that there may be something with my 
domain credentials.
The password I need to supply is my windows domain login password, so I 
think I am logged in as the domain user.
But if there is something wrong with the credentials it could be that 
during the login process there are attempts to access network shares 
which possibly fail and give timeouts.
Thanks for pointing me in that direction so I am going to put some set 
-x into the login scripts to see if I can find the reason.

Peter

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

       reply	other threads:[~2015-08-06 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1438879959.34691.ezmlm@cygwin.com>
2015-08-06 17:19 ` Peter [this message]
2015-08-06 15:29 Peter
2015-08-06 16:52 ` Mark Geisert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55C39689.5080202@freenet.de \
    --to=mandango@freenet.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).