X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 14 May 2008 10:57:34 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Unable to run sshd under a domain sshd_server account [SOLVED] Message-ID: <20080514085734.GJ18799@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3B3EFBD49B94AD4DBB7B7097257A8046DD020D AT FDSVAST06SXCH01 DOT flooddata DOT net> <20080513073720 DOT GA22193 AT calimero DOT vinschen DOT de> <3B3EFBD49B94AD4DBB7B7097257A8046DD02FC AT FDSVAST06SXCH01 DOT flooddata DOT net> <20080513163756 DOT GC18799 AT calimero DOT vinschen DOT de> <3B3EFBD49B94AD4DBB7B7097257A8046DD031A AT FDSVAST06SXCH01 DOT flooddata DOT net> <20080513165732 DOT GF18799 AT calimero DOT vinschen DOT de> <3B3EFBD49B94AD4DBB7B7097257A8046DD0327 AT FDSVAST06SXCH01 DOT flooddata DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B3EFBD49B94AD4DBB7B7097257A8046DD0327@FDSVAST06SXCH01.flooddata.net> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On May 13 12:07, Schutter, Thomas A. wrote: > Corinna Vinschen wrote: > > You're jumping to conclusions. The reason why USERNAME and USERDOMAIN > > are wrong I explained in my first reply. Both values don't matter > when > > Cygwin tries to connect to the PDC, as long as the /etc/passwd > pw_gecos > > field contains a valid U-DOMAIN\username entry. This information is > > used to connect to the PDC. > > > > > > Corinna > > OK. My /etc/passwd file was generated with the "mkpasswd -l -d" > command. > The /etc/passwd pw_gecos field for tschutter is just > "U-FLOODDATA\tschutter". So what debugging step can I take next? Try to find out what goes wrong. Can Cygwin get the DC for the domain? An strace of an sshd session will help, look for an error message in a function called get_logon_server. Does the DC refuse information? You should find something in the DC's event logs. Btw., a workaround for such problems is to add the user to the appropriate groups in /etc/group. This will give you a nice user token even if the DC is not cooperative. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/