delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/06/23/16:26:57

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Subject: RE: Error starting sshd: "Win32 error 1069"
Date: Mon, 23 Jun 2008 15:26:23 -0500
Message-ID: <3B3EFBD49B94AD4DBB7B7097257A8046F4D7AD@FDSVAST06SXCH01.flooddata.net>
In-Reply-To: <485DEDF5.3080503@eburg.com>
References: <485DEDF5 DOT 3080503 AT eburg DOT com>
From: "Schutter, Thomas A." <tschutter AT proxix DOT com>
To: "Gordon Messmer" <yinyang AT eburg DOT com>, <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m5NKQubb017624

> -----Original Message-----
> Sent: Sunday, June 22, 2008 12:15 AM
> To: cygwin AT cygwin DOT 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/


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019