public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Schutter, Thomas A." <tschutter@proxix.com>
To: "Gordon Messmer" <yinyang@eburg.com>, <cygwin@cygwin.com>
Subject: RE: Error starting sshd: "Win32 error 1069"
Date: Mon, 23 Jun 2008 20:50:00 -0000	[thread overview]
Message-ID: <3B3EFBD49B94AD4DBB7B7097257A8046F4D7AD@FDSVAST06SXCH01.flooddata.net> (raw)
In-Reply-To: <485DEDF5.3080503@eburg.com>

> -----Original Message-----
> Sent: Sunday, June 22, 2008 12:15 AM
> To: cygwin@cygwin.com
> Subject: Error starting sshd: "Win32 error 1069"
> 
> I'm having trouble starting sshd on a host running Windows Server
2003,
> SP1.  It was working several days ago, and then stopped for no reason
> that I can determine.
> 
> I tried starting the service by hand, and got:
> 
> $ cygrunsrv.exe -S sshd
> cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error
> 1062:
> The service has not been started.
> 
> I tried removing the service definition with "cygrunsrv -R sshd" and
> running "ssh-host-config -y" again, and now the error has changed.
Now
> I get:
> 
> $ cygrunsrv.exe -S sshd
> cygrunsrv: Error starting a service: StartService: Win32 error 1069:
> The service did not start due to a logon failure.
> 
> Permissions on /var/emtpy look correct, it's owned by "sshd_server",
> group "Administrators".  The system is a member of an AD domain; the
> "sshd_server" account is part of the domain.
> 
> cygcheck's output is attached.  What can I do to troubleshoot the
> problem further?

Did also you check the permissions and ownership of /etc/ssh*,
/var/log/lastlog, and /var/log/sshd.log?

It may be instructive to run this command to see what rights the
sshd_server has:
  editrights -l -u sshd_server

Once you get this fixed, you may have sporadic problems starting sshd
when rebooting.  To fix them, make sure that the Netlogon service has
started before starting the sshd service. Edit the registry and add
Netlogon to the DependOnService value in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sshd key.  In
short, you are ensuring that the system can talk to the domain
controller before it tries to start sshd.

--
Tom Schutter
First American - Proxix Solutions
(512) 977-6822


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

  reply	other threads:[~2008-06-23 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22 13:06 Gordon Messmer
2008-06-23 20:50 ` Schutter, Thomas A. [this message]
2008-06-23 21:43 ` Adam Thompson
2017-01-14 12:24 ` kinjo via cygwin
2017-01-14 15:40   ` Corinna Vinschen
2017-01-16  7:52     ` kinjo via cygwin

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=3B3EFBD49B94AD4DBB7B7097257A8046F4D7AD@FDSVAST06SXCH01.flooddata.net \
    --to=tschutter@proxix.com \
    --cc=cygwin@cygwin.com \
    --cc=yinyang@eburg.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).