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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; q=dns; s=default; b=SqYQZxEydQGI5il+
	f1WfWckNZ4Sfag4j4BgFQekx5+IOhZENLI6NrMJE5aiqAVhNEtRfZAmm2b8k7xTC
	gOUmwgJGOCCEdg51/DA62wEG0JgsGpZ/mPkzBQXQ8P5ggoBwOmaBfGxm5r07xYih
	/2qQKNNZgiNcNUjQ0/duG2h/UkY=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; s=default; bh=Jb2Ipe6eCQWDdyio38jt4S
	DUS6s=; b=srfqk0kJfzUEOMHMHH+V/L2jIYdmcVqmtyDHDrY2BzXTwwX7fAvKpj
	g8F0dJx4DeOK0D4duf8EnC9ypFleS/q18CFPsmxrA9oesBhYz4PvPZQDTDoK102T
	S1G5MNTk3OEIpWF4LR7zKS360DASyvifUVQ86ZP1uo2dE/9ncAvHY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=-2.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=dinwoodie, Dinwoodie, _before_, lee
X-HELO: mail-wm0-f47.google.com
MIME-Version: 1.0
X-Received: by 10.194.204.166 with SMTP id kz6mr109429209wjc.174.1452094719346; Wed, 06 Jan 2016 07:38:39 -0800 (PST)
In-Reply-To: <20160104231226.GP14466@dinwoodie.org>
References: <568AA766 DOT 7010101 AT gmail DOT com>	<568AD08C DOT 6080204 AT gmail DOT com>	<20160104231226 DOT GP14466 AT dinwoodie DOT org>
Date: Wed, 6 Jan 2016 10:38:39 -0500
Message-ID: <CAD8GWsvSpQHMUVRk395jpM+CbSnnB_Wmrinrdxw=QRHPsmkQ-A@mail.gmail.com>
Subject: Re: Fwd: SSHD not connecting from outside(real) IP
From: Lee <ler762 AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u06FcpwF005064

On 1/4/16, Adam Dinwoodie wrote:
> On Mon, Jan 04, 2016 at 06:05:32PM -0200, João Paulo wrote:
>> Hello all,
>> I have a mystery and I need help. I have openssh(Cygwin) installed
>> and working just fine in here.
>> I can connect normally from any of my machines to the server using
>> local IPs. Ex: ssh localhost or ssh 192.168.0.2. BUT, when using my
>> external IP(over internet->real IP) it times out.
>> I can validate that the service is up and running on
>> http://www.canyouseeme.org/ on the port FW I did for this service.
>> Port 22 is correctly FW to my SSHD server. On windows, I can only
>> see an entry on Security Events(attached) and nothing else after
>> that. (Means it is reaching my machine)
>> I have tried to reinstall Cygwin, change ports. sshd_config is in
>> default, disable firewall, AV. I ran out of ideas......
>> I had this working fine on previous window 7, now I am on Windows 10.
>> Thanks.
>
> To check I'm understanding you correctly: you're using Cygwin on your
> Windows 10 machine to run an sshd service, you're attempting to connect
> to this using SSH from another machine, this works when the other
> machine is within your local network but not when the other machine is
> external.
>
> If that's the case, I think it's very unlikely that Cygwin is the
> problem  -- if Cygwin were the problem, I would expect connections to
> fail on your local network too.  To check that, can you run a packet
> capture on the system running Cygwin sshd while you attempt to connect?
> I expect it will show no received packets, which means the problem lies
> elsewhere in your network.
>
> For packet capture I normally use Wireshark, but alternatives are
> available (doing it on your router would be ideal if it supports that).

Just be aware that a wireshark capture on the target machine captures
packets _before_ they're processed by the windows firewall, so if
wireshark shows the packets reaching the machine make sure to also
check the windows firewall log.

Regards,
Lee

--
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