The problem appears to be a change in the DNS resolution in glibc, which causes Windows guests to be unable to resolve DNS queries. The same is probably true for older versions of VMWare, but I have not tested those. See e.g. the following links for people suffering from this problem. The last link appears to have a detailed analysis. https://bbs.archlinux.org/viewtopic.php?id=201946 https://github.com/manjaro/packages-openrc/issues/8 https://communities.vmware.com/thread/533697?start=0&tstart=0 Additionally it appears that the problem has been fixed in a new version of VMWare Workstation (12.1.1). See e.g. the change log for VMWare 12.1.1 here: https://pubs.vmware.com/Release_Notes/en/workstation/12pro/workstation-1211-release-notes.html It mentions the following: > DNS names are not resolved in a Windows virtual machine running on an Ubuntu 16.04 host > ------------------------------------------------------------------------- > When you select a Network Address Translation (NAT) network for a Windows > virtual machine running on an Ubuntu 16.04 host, Domain Name System (DNS) > names are not properly resolved. > > This issue is resolved. I have tested this new version and can confirm that the DNS problem is resolved in VMWare Workstation 12.1.1.
thanks for pointing it out, you can find the latest vmware version in the overlay
(In reply to Da Fox from comment #0) ... > Additionally it appears that the problem has been fixed in a new version of > VMWare Workstation (12.1.1). ... > I have tested this new version and can confirm that the DNS problem is > resolved in VMWare Workstation 12.1.1. REFERENCE: Bug 616958 : app-emulation/vmware-workstation-12.5.7 version bump [for "stable", excluding "~amd64"] Attachment --> emerge--info__vmware__gentoo.txt: "sys-libs/glibc: 2.23-r4::gentoo" # equery list glibc [IP-] [ ] sys-libs/glibc-2.23-r4:2.2 To me, this bug seems to be FIXED / OBSOLETE.
(In reply to Manfred Knick from comment #2) > > To me, this bug seems to be FIXED / OBSOLETE. Ack
