From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23002 invoked by alias); 23 Jun 2008 20:26:51 -0000 Received: (qmail 22992 invoked by uid 22791); 23 Jun 2008 20:26:50 -0000 X-Spam-Check-By: sourceware.org Received: from mail2.flooddata.com (HELO mail2.flooddata.com) (67.96.169.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 23 Jun 2008 20:26:27 +0000 Received: from localhost (localhost [127.0.0.1]) by mail2.flooddata.com (Postfix) with ESMTP id D3B1727EDA; Mon, 23 Jun 2008 15:26:25 -0500 (CDT) Received: from mail2.flooddata.com ([127.0.0.1]) by localhost (mail2.flooddata.com [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 31608-08; Mon, 23 Jun 2008 15:26:24 -0500 (CDT) Received: from callisto.flooddata.com (callisto.flooddata.com [10.5.0.33]) by mail2.flooddata.com (Postfix) with ESMTP id 7A2D327EC1; Mon, 23 Jun 2008 15:26:24 -0500 (CDT) Received: from fdsvast06sxch01.flooddata.net (athena.flooddata.com [10.3.1.61]) by callisto.flooddata.com (Postfix) with ESMTP id 7856CB52F; Mon, 23 Jun 2008 15:26:24 -0500 (CDT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Error starting sshd: "Win32 error 1069" Date: Mon, 23 Jun 2008 20:50:00 -0000 Message-ID: <3B3EFBD49B94AD4DBB7B7097257A8046F4D7AD@FDSVAST06SXCH01.flooddata.net> In-Reply-To: <485DEDF5.3080503@eburg.com> References: <485DEDF5.3080503@eburg.com> From: "Schutter, Thomas A." To: "Gordon Messmer" , X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2008-06/txt/msg00473.txt.bz2 > -----Original Message----- > Sent: Sunday, June 22, 2008 12:15 AM > To: cygwin@cygwin.com > Subject: Error starting sshd: "Win32 error 1069" >=20 > 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. >=20 > I tried starting the service by hand, and got: >=20 > $ cygrunsrv.exe -S sshd > cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error > 1062: > The service has not been started. >=20 > 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: >=20 > $ cygrunsrv.exe -S sshd > cygrunsrv: Error starting a service: StartService: Win32 error 1069: > The service did not start due to a logon failure. >=20 > 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. >=20 > 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/