X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=czShAlNoDZCqj4if MDl0rYIxgnchOPndW4lGHwV2A1fpDlHAb3nHXbx6GOnKELxFilQhw8xCFTlU9IpE U0brHTJJGpNvfCnrJNN3lfJt1yxP1bq58MRueyjJ6nwmLfxvCJxkiQpwdhb8GcBF QQYJvDkozxcLX9V6CQ5LTFvHTe4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=default; bh=XZtUQ7FZYOxy7LB3h+Hgsh mLcaM=; b=g4uwfgyXhct2MI+2YTy2F99o7oN6U6a3WsmCy/MuyBmu4rSB6I1JTe kJVmjOZ7iwWeuhW0sQSSQYlI+haLDUimg+fP8Wm8H/ultwtjlegWlokfbdA0d7L/ xx0QjgVu0S8Jw2S+wnz4A5bg6zbA3LCqYRd9cReExXeDTfaT7nZAA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED autolearn=ham version=3.3.2 X-HELO: vms173013pub.verizon.net Message-id: <523748CD.5070205@cygwin.com> Date: Mon, 16 Sep 2013 14:07:09 -0400 From: "Larry Hall (Cygwin)" Reply-to: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Fwd: Way to test cyglsa? References: <5237373E DOT 1070905 AT cygwin DOT com> In-reply-to: Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit On 9/16/2013 1:47 PM, Evan Rowley wrote: > Thanks for the recommendaitons Larry. > > If $USER is the test, then it appears cyglsa is working on this machine. > > The firewall is disabled. > > Thanks for refering me to the BLODA. I noticed some Symantec products > listed there. Symantec's Endpoint Protection and Symantec's Bakcup > Exec are installed on this server. I doubt those are causes because > the same programs are installed on another server where sshd works. In > fact, that other server is a copy of this server in question AKA the > one which isn't working. The copy was made a few years ago so there > are minor differences between the two machines. During my testing I've > used the same sshd configurations on both and I can't for the life of > me figure out why one works while the other doesn't. > > For a while, I thought there was an issue with user switching but > event log shows success for cyg_server and even for the users I > attempt to login with via ssh. If you haven't enabled debugging for sshd, I'd recommend trying that. It can provide info about what the server is doing which can reveal some helpful details. Presumably you've been able to get communication to work fine using password authentication? > These servers sit on a domain with a 'strong password' requirement. > I'm wondering if there are special keyboard characters in the > passwords which may interfere with the way cygwin handles user > authentication. Since you're currently dealing with password-less authentication, I don't think that should be a problem. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple