On Mar 16 10:57, Jun-ya Kato wrote:
>
>
> > Thank you! I just uploaded 2.5.0-0.7 with the proposed patch.
> > It should be available on the mirrors shortly.
>
> I fetched version 2.5.0-0.7.
>
> ipv6 enabled command like a git or wget works fine under VMware NAT.
>
> I also configured network
> Thank you! I just uploaded 2.5.0-0.7 with the proposed patch.
> It should be available on the mirrors shortly.
I fetched version 2.5.0-0.7.
ipv6 enabled command like a git or wget works fine under VMware NAT.
I also configured network adaptor to point to Google public cache
DNS directly. It
On Mar 15 10:16, Jun-ya Kato wrote:
> > Is anybody here affected by this problem willing to give this a test?
> > I can create another Cygwin 2.5.0 test release pretty soon...
>
> I think it's useful workaround for cygwin user under VMware NAT.
> I'd like to test it.
Thank you! I just uploaded 2
> Is anybody here affected by this problem willing to give this a test?
> I can create another Cygwin 2.5.0 test release pretty soon...
I think it's useful workaround for cygwin user under VMware NAT.
I'd like to test it.
From: Corinna Vinschen
Subject: Re: Cygwin u
On Mar 14 09:34, Jun-ya Kato wrote:
> It also depends on query againt VMware's DNS proxy server.
>
> For more analysis, see vmware community site,
> https://communities.vmware.com/thread/518949?start=15&tstart=0
>
>
> I think it is not cygwin's bug at all. but any workaround may be
> implem
ddrInfoW() API.
From: Carl-Erik Kopseng
Subject: Re: Cygwin unable to resolve hostnames
Date: Sun, 13 Mar 2016 23:07:36 +0100
> Just a follow up for anyone else experiencing this. I fixed the DNS
> issues by directly specifying a DNS server in the IPV4 settings for my
> network adapt
Just a follow up for anyone else experiencing this. I fixed the DNS
issues by directly specifying a DNS server in the IPV4 settings for my
network adapter in the Windows VM. I used Google's public DNS server
(8.8.8.8) and it worked instantly.
The cue to check out DNSSEC was a dead-end as the hostn
Carl-Erik Kopseng gmail.com> writes:
>>> 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-
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
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 sti
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.n
The only thing in that list of interfaces that have IP is the
"Ethernet adapter Ethernet0". Right of my head I don't see anything
obviously wrong. My first suggestion would be to disable IPv6 on the
adapter, just on the odd chance that it is the cause.
After that I would start ping'ing the default
> > I'm not sure when this started, but recently Cygwin has been unable to
> > resolve (certain) hostnames.
> >
> > Example:
> > wget github.com
> > --2015-07-22 15:17:04-- http://github.com/
> > Resolving github.com (github.com)... failed: Non-recoverable failure
> > in name resolution.
[snip]
On 7/22/2015 3:53 PM, Matthew Fountain wrote:
> I'm not sure when this started, but recently Cygwin has been unable to
> resolve (certain) hostnames.
>
> Example:
> wget github.com
> --2015-07-22 15:17:04-- http://github.com/
> Resolving github.com (github.com)... failed: Non-recoverable failure
14 matches
Mail list logo
