public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Problem with ssh on Windows 2012 R2
Date: Mon, 24 Aug 2015 19:13:00 -0000	[thread overview]
Message-ID: <8737z8h53r.fsf@Rainer.invalid> (raw)
In-Reply-To: <55DB6805.9090100@turriff.net> (Andreas Turriff's message of	"Mon, 24 Aug 2015 11:52:53 -0700")

Andreas Turriff writes:
> I am running Cygwin (i686 / 32-bit) on Windows 2012 R2 in an Active
> Directory environment; the version in use is

I (continue to) have the same or a similar problem and meanwhile I've
come believe this is caused by a group policy (I can't look at all of
those unfortunately).  It might be worth a try to set up a 64bit Cygwin,
since that is working for me with no problems.  I've also no problems on
a Windows 8.1 w/ Bing box.

If you only ever intend to log into this machine using a single account
(for administration), you can also have the sshd run under that account,
as what fails is likely the switch to another user.  I've been trying to
debug this with Corinna a while back, but she couldn't reproduce it in
her environment and the only fishy thing going on in the strace is that
the switch to a different user fails for no apparent reason.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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-24 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 18:52 Andreas Turriff
2015-08-24 19:13 ` Achim Gratz [this message]
2015-08-24 19:42   ` Andreas Turriff

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=8737z8h53r.fsf@Rainer.invalid \
    --to=stromeko@nexgo.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).