X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: Failure of name resolution with ssh on windows 7 and VMware Date: Sun, 14 Aug 2011 09:20:22 +0200 Lines: 15 Message-ID: References: <4E46E867 DOT 4080903 AT stevens DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/3.0.4 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 * John Dzielski (Sat, 13 Aug 2011 17:11:03 -0400) > I am unable to get name resolution to work with ssh. The command ssh X > returns the error "ssh: could not resolve hostname X: Non-recoverable > failure in name resolution." The command nslookup X returns a valid IP > address. Run a Wireshark trace when ssh fails and see if you actually have an attempt for name resolution. I'd rather suspect UAC or the firewall. > I've created a partial workaround in my .bashrc file that creates > variables containing the IP addresses of the names I need to resolve. This is a weird idea. Use /etc/hosts for that. Thorsten -- 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