X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <907511.5337.qm@web55103.mail.re4.yahoo.com> References: <684542.66011.qm@web55105.mail.re4.yahoo.com> <907511.5337.qm@web55103.mail.re4.yahoo.com> Date: Thu, 13 May 2010 14:31:47 -0600 Message-ID: Subject: Re: sshd From: Steven Collins To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Thu, May 13, 2010 at 14:17, Eric Berge <> wrote: > > > Check the service to see if it's configured using "Services" > under "Administrative Tools" in the control panel. If it is > you might want to check the firewall, but it sounds like it > was working before the update so it shouldn't be that. > > Eric Services is fine. Your comment about the firewall caused me to double check that. Once I started down that road I quickly found the problem. In the same time frame that I updated Cygwin versions corporate switched us from Symantec to McAfee. The new McAfee stuff added a firewall which I'd not configured to allow ssh. Thanks for the comments and shining a light in the dark corner I'd neglected. Steven -- 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