From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 115010 invoked by alias); 22 Feb 2018 17:25:39 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 115001 invoked by uid 89); 22 Feb 2018 17:25:39 -0000 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 Received: from smtp-out-so.shaw.ca (HELO smtp-out-so.shaw.ca) (64.59.136.139) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 22 Feb 2018 17:25:37 +0000 Received: from [192.168.1.100] ([24.64.240.204]) by shaw.ca with ESMTP id oucgeDQXvLkozoucheumhP; Thu, 22 Feb 2018 10:25:35 -0700 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.Inglis@SystematicSw.ab.ca Subject: Re: Sudden, unexplained failure of ssh To: cygwin@cygwin.com References: <60c360a2021449ccbd780c5b51c4db92@OMZP1LUMXCA08.uswin.ad.vzwcorp.com> From: Brian Inglis Message-ID: <20691ee7-7a06-4c68-08d4-87b4c5e59769@SystematicSw.ab.ca> Date: Thu, 22 Feb 2018 17:25:00 -0000 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> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfEXs/ap5hVO3OLLzszucryp4CcnSj3J/5ziuv7oenoh35Te3ukwhF+CsB2yJWkadWzA8JtCJU4XcxhrebLUFyagQzzZUA+CtekksGd1Yq4N5UdRER/0S pfIo7TLAROi0W5lphN8lbJVdoREm9HVGqhd5c9UOkntcdNiMDcaidjGWEMboi3TkUUnPG/mClMtz5Q== X-IsSubscribed: yes X-SW-Source: 2018-02/txt/msg00248.txt.bz2 On 2018-02-22 09:56, mark.paulus@verizon.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