From: Carl-Erik Kopseng <carlerik@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin unable to resolve hostnames
Date: Fri, 12 Feb 2016 13:29:00 -0000 [thread overview]
Message-ID: <CAA05WiaqKoaRuxTCYmrqOquSPGVO+jO0gLLVhcX1L7N0Tr+hLg@mail.gmail.com> (raw)
In-Reply-To: <20160212090614.GA19968@calimero.vinschen.de>
I don't think it's a "generic Cygwin problem" either. If it was, the
mailing list would be flooded with people having problems with every
net based utility in existence :-)
I think it has to do with how Cygwin interfaces with VMs. Perhaps it
has something to do with network tunnelling or something related to
how ip and DNS works when being NAT'ed through VMWare Fusion.
I am running the Windows 8 VM on VMWare Fusion on OS X 10.11.3
Carl-Erik Kopseng
about.me/kopseng
2016-02-12 10:06 GMT+01:00 Corinna Vinschen <corinna-cygwin@cygwin.com>:
> On Feb 11 11:58, Carl-Erik Kopseng wrote:
>> I disabled IPv6. No change.
>> I pinged my gateway. Went fine, but still ssh fails.
>> I tried creating a /etc/resolv.conf with the same contents as the one
>> on my mac. Same difference.
>>
>> And of course I have tried rebooting my VM. No change.
>>
>> I still get
>>
>> ssh: Could not resolve hostname timbuktu.kopseng.no: Non-recoverable
>> failure in name resolution
>
> I don't think this is a generic Cygwin problem. I can resolve the
> hostname just fine:
>
> $ uname -svr
> CYGWIN_NT-10.0 2.4.1(0.293/5/3) 2016-01-24 11:26
> $ ssh timbuktu.kopseng.no
> The authenticity of host 'timbuktu.kopseng.no (51.175.197.68)' can't be established.
> RSA key fingerprint is SHA256:ddcghrb6BI6+TVDKDE3Yf+U43v9EL6u7HsNw7Hec+y8.
> Are you sure you want to continue connecting (yes/no)? no
> Host key verification failed.
>
>
> Corinna
>
> --
> Corinna Vinschen Please, send mails regarding Cygwin to
> Cygwin Maintainer cygwin AT cygwin DOT com
> Red Hat
--
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
next prev parent reply other threads:[~2016-02-12 13:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 20:53 Matthew Fountain
2015-07-22 21:50 ` René Berber
2015-12-11 10:18 ` Carl-Erik Kopseng
2015-12-11 12:12 ` Jan Bruun Andersen
2016-02-11 10:59 ` Carl-Erik Kopseng
2016-02-12 9:06 ` Corinna Vinschen
2016-02-12 13:29 ` Carl-Erik Kopseng [this message]
2016-02-16 9:31 ` Brian Inglis
2016-03-13 22:08 ` Carl-Erik Kopseng
2016-03-14 0:34 ` Jun-ya Kato
2016-03-14 9:55 ` Corinna Vinschen
2016-03-15 1:17 ` Jun-ya Kato
2016-03-15 10:42 ` Corinna Vinschen
2016-03-16 1:57 ` Jun-ya Kato
2016-03-16 10:05 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA05WiaqKoaRuxTCYmrqOquSPGVO+jO0gLLVhcX1L7N0Tr+hLg@mail.gmail.com \
--to=carlerik@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).