X-Spam-Check-By: sourceware.org Message-ID: X-Sender: robbosch AT msn DOT com From: "Rob Bosch" To: , Subject: Re: Potential bug in sshd Date: Tue, 12 Sep 2006 08:17:09 -0600 Message-ID: <000001c6d676$223a5110$0300a8c0@iPremise.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Sshd will spawn processes that deal with individual connections so even though you stop the service there may still be sshd processes running. The way to tell if your sshd daemon is stopped is to run a netstat -a | find "ssh" | find "LISTEN". This will only find sshd processes that are listening for new connections and not the ones that are established to deal with existing ssh connections. I've experienced connection problems from time to time with sshd on cygwin. Almost always this is either due to high load on the receiving server and it just can't handle it, or a problem with the network connection. Are your connections all on the LAN or WAN? -- 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/