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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=WGmyAc8tIMkr7qgD
	BwqTLVqQX6nQZBXzDWf0zp22ld4qZJkrxNHWMiHlYq5uRcjp6Y+OL9gctLyaJHxm
	sp3ly3c+YK5acXWfxGn0f1oodtXmgEy+Yx6o/98JjETzFCzFEoo2x2t9H8QG/Ndj
	c+yOQgKsFVyjM88w+GM18cfdkhc=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=WvrbDOtbpMkzPafGWn37rU
	L4iig=; b=QwPXRQCalQyZp/J8l277UqxikTxDiYPDsOniACUp/N72/RJzzzDluZ
	epP+hx2VdQ9WhIZxG9QCH7fDN55S8KGuzUnlOk/6zMNgWGxNMJC0qkK9z7h1zna/
	nrSKFarmEX8V3h4VQs4J00XaPZWBzPaw0T3vB0GSUCS6NQLf2SdHw=
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=-1.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=company, agent, Agent
X-HELO:	smtp-out-so.shaw.ca
X-Authority-Analysis:	v=2.3 cv=OeS28CbY c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=N659UExz7-8A:10 a=ZsyXEVtvAAAA:8 a=b1HW5k5wAAAA:8 a=w_pzkKWiAAAA:8 a=rUfaviZvpE0JZ6jBsBQA:9 a=jOjwdIFq_l6NUG3j:21 a=dVLW_mEM-_2UeEdk:21 a=pILNOxqGKmIA:10 a=9c8rtzwoRDUA:10 a=gCE4WevuyLj8D5TXWPGm:22 a=sRI3_1zDfAgwuvI8zelB:22
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject:	Re: Sudden, unexplained failure of ssh
To:	cygwin AT cygwin DOT com
References:	<60c360a2021449ccbd780c5b51c4db92 AT OMZP1LUMXCA08 DOT uswin DOT ad DOT vzwcorp DOT com>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID:	<20691ee7-7a06-4c68-08d4-87b4c5e59769@SystematicSw.ab.ca>
Date:	Thu, 22 Feb 2018 10:25:33 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version:	1.0
In-Reply-To:	<60c360a2021449ccbd780c5b51c4db92@OMZP1LUMXCA08.uswin.ad.vzwcorp.com>
X-CMAE-Envelope:	MS4wfEXs/ap5hVO3OLLzszucryp4CcnSj3J/5ziuv7oenoh35Te3ukwhF+CsB2yJWkadWzA8JtCJU4XcxhrebLUFyagQzzZUA+CtekksGd1Yq4N5UdRER/0S pfIo7TLAROi0W5lphN8lbJVdoREm9HVGqhd5c9UOkntcdNiMDcaidjGWEMboi3TkUUnPG/mClMtz5Q==
X-IsSubscribed:	yes

On 2018-02-22 09:56, mark DOT paulus AT verizon DOT com wrote:
> I've been running 2.9.x under windows 7 on my 16GB laptop for a long time (probably the 
> last year), when late last week my ssh outbound quit working.  The failure is indicated with 
> this error message:
> 
> ssh: Could not resolve hostname csu6220509.vzbi.com: Non-recoverable failure in name resolution
> 
> I checked the forums, and what I saw seemed to relate to connecting to VM boxes.
> In my case, this is not the cause of the failure.
> This machine is my company provided (and software managed) laptop, so I don't have a 
> lot of control over (in fact, I don't have hardly any control) what gets "pushed" to it.
> However, the one thing that I noticed that seemed to coincide with the failure is that
> the company pushed an "Elastica Reach Agent 1.0.20930.0" to my machine.

Another poorly written cloud "security"/intercept/monitor BLODA app; see:

	https://cygwin.com/faq/faq.html#faq.using.bloda

appears to be interfering with resolving.
Try "cygcheck ssh wget" to see if non-Cygwin non-Windows DLLs are in your PATH,
remove those directories from your Cygwin PATH, and retry to see if that helps.
Use host/nslookup/dig to get the IP address, and retry using that instead of the
host name, to bypass the resolver, and see if that helps.
See if you can add a bypass in the product for ssh and wget, or have your admins
do so, and report the problem to the vendor.

> I thought the issue might have been a version problem, so I updated to the latest 
> Cygwin version
> $ uname -a
> CYGWIN_NT-6.1 TCO10106LKVTAHB 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin
> 
> That didn't fix the problem.  I've also tried some other utilities,  which are working, 
> such as mobaxterm(Cygwin based), babun(Cygwin based)  and putty.  All those seem to work
> fine.
> 
> Once I determined that it wasn't my actual network stack, I then tried running ssh under
> strace, and now it works.  So, I can use ssh if I use it with strace, but natively by itself
> it continues to get the failure in name resolution.
> 
> Any clues, hints or pointers on how to go about either determining what the problem is, or 
> how to clean it up?
> 
> (I am also seeing the same issue with wget, and strace clears that up also
> $ wget http://linux1.vzbi.com
> --2018-02-22 09:55:38--  http://linux1.vzbi.com/
> Resolving linux1.vzbi.com (linux1.vzbi.com)... failed: Non-recoverable failure in name resolution.
> wget: unable to resolve host address 'linux1.vzbi.com'

You could try running ssh and wget with debugging options to see if that
bypasses the problem similar to running under strace.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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

- Raw text -