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 From: "Dave Korn" To: Subject: RE: can't connect to ssh server on windows xp Date: Fri, 1 Jul 2005 17:55:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" In-Reply-To: Message-ID: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j61GtSBw007468 ----Original Message---- >From: Will Parsons >Sent: 01 July 2005 17:35 > René Berber wrote: >> Will Parsons wrote: >> [snip] >>>> If the answer to my above question is yes, then you have to enable >>>> sshd use of port 22 on Windows XP's own firewall. Otherwise, I don't >>>> know, but "connection refused" means something is listening on that >>>> port and refusing connections so >>> >>> >>> I think "connection refused" is the message you get when *nothing* is >>> listening on the port. >> >> No, you get a timeout when nothing is listening. > > Hmm... I just tried telnetting to a some Unix/QNX machines where I have > no telnet or inetd daemon running. I got "connection refused". > > - Will "Connection refused" has a very precise meaning: it means that in response to the outbound SYN packet, the remote host returned a RST instead of a SYN/ACK. This happens when the port in question is closed - nothing listening - but *not* firewalled. A firewalled port will return nothing at all, which is generally referred to as "stealthed", and which will eventually cause the socket initiating the outbound connection to time out. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/