Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 To: cygwin@cygwin.com From: giuseppe Subject: Re: sshd problems Date: Mon, 18 Apr 2005 07:11:43 +0000 (UTC) Lines: 36 Message-ID: References: <4260E74D.29371.DFA10@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 141.108.3.210 (Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020 Firefox/0.10.1) X-IsSubscribed: yes Hi, John! Of course thanks againn! So, let's start. this time you asked - From your data it appears that you can ssh to the localhost which means your sshd server is - running. However, you can't connect to your localhost from the Linux machine; the connection - times out. Your other examples all look like they are connections from the localhost to other - machines, which all appear to work. - - Is this a Windows XP machine with Service Pack 2 installed? Have you opened up the firewall - to allow port 22 through? If not, that explains your problem. Port 22 is blocked by default. - - The firewall won't block ssh connections originating from your localhost to other machines. - That would be consistent with the data you've shown. Yes, it's a Windows XP machine with Service Pack 2 installed. I added an exception for port 22 in Firewall options; anyway I could have done some mistakes so I ask you to explain me, please, the correct procedure to allow foreing incoming through port 22. best regards giuseppe -- 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/