public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Stephen Carrier <carrier@berkeley.edu>
Cc: cygwin@cygwin.com
Subject: Re: sshd problem on WS2008R2 64bit
Date: Wed, 06 Mar 2019 12:12:00 -0000	[thread overview]
Message-ID: <20190306121154.GN3785@calimero.vinschen.de> (raw)
In-Reply-To: <20190306010254.GA4210@zebra>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

On Mar  5 17:02, Stephen Carrier wrote:
> Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
> fail unless some user logs into Windows first.  In this case, that is by
> RDP, and it doesn't need to be the same user as the one logging in by ssh.
> After logging out of the windows-native session, ssh continues to work.
> 
> Windows event logs report a failed attempt for "NULL SID" and
> 
> ----
> Failure Reason: An error occured during Logon.
> Status:         0xc00000bb

This is weird.  Status 0xc00000bb is STATUS_NOT_SUPPORTED.  That
doesn't make sense, at least not on 2008 R2 with 64 bit Cygwin.

Are you trying to login via sshd with a local account or a domain
account?

I tried to reproduce your issue with Cygwin 3.0.2 on a Windows 10
machine.  I rebooted the machine and did not login locally or via
RDP.  Sshd login worked in both cases (local/domain account).

Can you test this again, in particular with installing Cygwin 3.0.2?

In the meantime, I need some time to set up a Windows 2008 R2
machine for testing.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-03-06 12:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  1:03 Stephen Carrier
2019-03-06 12:12 ` Corinna Vinschen [this message]
2019-03-06 12:48   ` Corinna Vinschen
2019-03-06 14:17     ` Corinna Vinschen
2019-03-06 14:34       ` Corinna Vinschen
2019-03-06 15:30         ` Bill Stewart
2019-03-06 15:34           ` Corinna Vinschen
2019-03-06 15:59             ` Bill Stewart
2019-03-06 16:45             ` Bill Stewart
2019-03-06 20:13               ` Corinna Vinschen
2019-03-06 20:48                 ` Bill Stewart
2019-03-06 20:59                   ` Corinna Vinschen
2019-03-06 21:25                     ` Bill Stewart
2019-03-06 23:44                       ` Stephen Paul Carrier
2019-03-06 23:54                         ` Stephen Paul Carrier
2019-03-07  6:15                     ` Brian Inglis
2019-03-07  8:54                       ` Corinna Vinschen
2019-03-07 14:04                         ` Brian Inglis

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=20190306121154.GN3785@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=carrier@berkeley.edu \
    --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).