Thank you for sharing. I'm experiencing the exact issue. When I remove "Cisco AnyConnect Socket Filter" DNS resolution starts working.
But like you said it adds itself back and DNS resolution breaks.
Original Message:
Sent: Apr 21, 2025 05:56 PM
From: A Blake
Subject: Can't reach DNS server from Windows 11 virtual machine
I have tried every suggestion listed in this post, nothing has worked for me except for disabling 'Cisco Secure Client - Socket Filter' Type: 'DNS Proxy' under Network > Filters. The problem is it gets re-enabled soon after I disable it.
Original Message:
Sent: Apr 21, 2025 05:30 PM
From: Technogeezer
Subject: Can't reach DNS server from Windows 11 virtual machine
That's an interesting find. IPv6 is always enabled in current macOS from what I see - you just get the ability to configure it automatically. link-local only, or manually.
I'm running with a link-local only IPv6 configuration on my M1 Mac mini (Sequoia 15.4) but with IPv6 enabled in Windows. Name resolution works without issue. I wonder if this is related to configuring IPv6 automatically on the Mac.
It seems that IPv6 is enabled for you automatically in Windows and it's not as easy to turn it off in Windows 24H2 as it was in prior versions (the configuration is hidden in the legacy Control Panel > Network and Internet)..
------------------------------
- Paul (technogeezer)
vExpert 2025
Original Message:
Sent: Apr 21, 2025 03:06 PM
From: Davor Guttierrez
Subject: Can't reach DNS server from Windows 11 virtual machine
Hello,
I have found the source of the issue. If I do not have IPv6 enabled on the host - MacOS latest, or if the IPv6 is non-functional, the network Shared With my Mac in Windows 11 does not work, or I only receive IPv6 link-local addresses for DNS through DHCP, and resolving does not work. If I have functional IPv6 on the host, then the network in Windows 11 works without any issues. Also, if I disable IPv6 in Windows 11, DNS does not work. However, I do not know where the source of the problem lies, whether in VMWare, Windows 11, or MacOS. Resetting network settings in Windows does not help, nor does flushing DNS.
Best regards, Davor
Original Message:
Sent: Apr 21, 2025 12:58 PM
From: Paul Rockwell
Subject: Can't reach DNS server from Windows 11 virtual machine
One other thought: Have you tried to flush the Windows DNS cache:
Open a Windows terminal and issue the following:
ipconfig /flushdns
------------------------------
- Paul (technogeezer)
vExpert 2025
Original Message:
Sent: Apr 21, 2025 12:02 PM
From: Technogeezer
Subject: Can't reach DNS server from Windows 11 virtual machine
I can perform an nslookup that returns correctly, but I can't ping the FQDN. I can ping the IP address.
I'm scratching my head as to why that isn't working. One would think that if nslookup is giving you the right IP address for the FQDN and that you can ping using the IP address, then ping using the FQDN should work. A result fron nslookup shows that the resolver is working with Fusion.
Can you open a Windows terminal and run the nslookup for the FQDN, run the ping to the IP address it returns, then run the ping to the FQDN -- and post the output here?
------------------------------
- Paul (technogeezer)
vExpert 2025
Original Message:
Sent: Apr 20, 2025 03:56 PM
From: Davor Guttierrez
Subject: Can't reach DNS server from Windows 11 virtual machine
I also notice the same problem on the MacBook Pro M4, the latest version of Fusion, and Windows 11 on ARM architecture. It doesn't matter whether I have host networking or bridge. I can perform an nslookup that returns correctly, but I can't ping the FQDN. I can ping the IP address. If I set the DNS settings to manual, for example to 1.1.1.1, everything works; however, it doesn't work if the DNS settings are automatic.
Original Message:
Sent: Apr 19, 2025 03:56 AM
From: Takashi Yoshida
Subject: Can't reach DNS server from Windows 11 virtual machine
>Did you power off your VMs and shut down Fusion before you connected to the hotel network?
I turned off Mac Book during the flight, after arriving the hotel I turned on MacBook and started up Fusion and VM.
Anyway I tried following instruction, then the issue is still same. Nothing change.
>could power down your VMs, shut down the Fusion GUI, then restart Fusion and your VMs - see if anything changes?
Original Message:
Sent: Apr 18, 2025 08:55 PM
From: Technogeezer
Subject: Can't reach DNS server from Windows 11 virtual machine
Did you power off your VMs and shut down Fusion before you connected to the hotel network? If not, could power down your VMs, shut down the Fusion GUI, then restart Fusion and your VMs - see if anything changes?
------------------------------
- Paul (technogeezer)
vExpert 2025
Original Message:
Sent: Apr 18, 2025 06:27 PM
From: Takashi Yoshida
Subject: Can't reach DNS server from Windows 11 virtual machine
@Technogeezer san
Thank you for your reply.
>Did this work in the past?
Yes, it had worked for more than a year.
And I upgrade MacOS on 2nd of April, but it still worked.
The issue has started since 8th April when I started overseas business trip.
Once I connect to Hotel WiFi via Captive site, the issue started.
And the output of the commands you told me.
1) nslookup google.com 192.168.144.2
======================================================
;; connection timed out; no servers could be reached
======================================================
2) ifconfig -a
======================================================
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
anpi0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 06:e3:9c:59:2a:e1
media: none
status: inactive
anpi1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 06:e3:9c:59:2a:e2
media: none
status: inactive
en3: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 06:e3:9c:59:2a:c1
nd6 options=201<PERFORMNUD,DAD>
media: none
status: inactive
en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 06:e3:9c:59:2a:c2
nd6 options=201<PERFORMNUD,DAD>
media: none
status: inactive
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 36:45:90:41:86:40
media: autoselect <full-duplex>
status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 36:45:90:41:86:44
media: autoselect <full-duplex>
status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 36:45:90:41:86:40
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 8 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 9 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: <unknown type>
status: inactive
ap1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether da:b1:74:7e:47:de
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (none)
status: inactive
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether 2e:81:fa:14:f8:13
inet6 fe80::8b8:b208:20fb:b47c%en0 prefixlen 64 secured scopeid 0xb
inet 172.20.4.43 netmask 0xfffff000 broadcast 172.20.15.255
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
awdl0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether 22:ff:d2:17:ed:15
inet6 fe80::20ff:d2ff:fe17:ed15%awdl0 prefixlen 64 scopeid 0xd
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 22:ff:d2:17:ed:15
inet6 fe80::20ff:d2ff:fe17:ed15%llw0 prefixlen 64 scopeid 0xe
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (none)
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
inet6 fe80::8eae:5c0:94bf:96ad%utun0 prefixlen 64 scopeid 0xf
nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::fe14:e57b:c85f:9a4d%utun1 prefixlen 64 scopeid 0x10
nd6 options=201<PERFORMNUD,DAD>
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
inet6 fe80::adda:93a5:f145:f640%utun2 prefixlen 64 scopeid 0x11
nd6 options=201<PERFORMNUD,DAD>
utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000
inet6 fe80::ce81:b1c:bd2c:69e%utun3 prefixlen 64 scopeid 0x12
nd6 options=201<PERFORMNUD,DAD>
utun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::a9ce:c832:190f:1ebd%utun4 prefixlen 64 scopeid 0x13
nd6 options=201<PERFORMNUD,DAD>
utun5: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::ad53:7a25:98a7:a8b3%utun5 prefixlen 64 scopeid 0x14
nd6 options=201<PERFORMNUD,DAD>
utun6: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::b64b:593d:8811:19d5%utun6 prefixlen 64 scopeid 0x15
nd6 options=201<PERFORMNUD,DAD>
utun7: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::8466:ffea:26d8:d77b%utun7 prefixlen 64 scopeid 0x16
nd6 options=201<PERFORMNUD,DAD>
utun8: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::3451:af49:90b9:872d%utun8 prefixlen 64 scopeid 0x17
nd6 options=201<PERFORMNUD,DAD>
vmenet0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether 26:b2:5e:fc:cb:01
media: autoselect
status: active
bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=3<RXCSUM,TXCSUM>
ether a2:78:17:87:b7:64
inet 172.16.56.1 netmask 0xffffff00 broadcast 172.16.56.255
inet6 fe80::a078:17ff:fe87:b764%bridge100 prefixlen 64 scopeid 0x19
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: vmenet0 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 24 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
vmenet1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether ba:9a:90:f9:b9:52
media: autoselect
status: active
bridge101: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=3<RXCSUM,TXCSUM>
ether a2:78:17:87:b7:65
inet 192.168.144.1 netmask 0xffffff00 broadcast 192.168.144.255
inet6 fe80::a078:17ff:fe87:b765%bridge101 prefixlen 64 scopeid 0x1b
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: vmenet1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 26 priority 0 path cost 0
member: vmenet2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 28 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
vmenet2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether 9a:64:02:fc:ef:6b
media: autoselect
status: active
===================================================
Many thanks
Original Message:
Sent: Apr 18, 2025 03:38 PM
From: Technogeezer
Subject: Can't reach DNS server from Windows 11 virtual machine
For NAT networking, the DNS server is being provided by. the vmnet-natd service. What appears happening is that the DNS service on the NAT network segment is either not starting successfully, or isn't forwarding packets to the host's DNS service configuration.
Did this work in the past? And if so, what has changed since then (was there a macOS upgrade or a Fusion upgrade?)
Can you open the Fusion application (you don't need to start any virtual machines), open the Terminal app on the Mac, then post the output of the following commands run in the terminal:
nslookup google.com 192.168.144.2ifconfig -a
------------------------------
- Paul (technogeezer)
vExpert 2025
Original Message:
Sent: Apr 18, 2025 01:57 PM
From: Takashi Yoshida
Subject: Can't reach DNS server from Windows 11 virtual machine
Suddenly I can't reach DNS server from Windows 11 virtual machine.
Environment:
Host : MBP (2021) MacOS 15.4.1 + VMware Fusion 13.6.3 (Network Settings is NAT)
Guest: Windows 11 (24H2)
what I tried
1) ipconfig /renew + ipconfig /release
2) reset network
3) Network driver uninstall and reinstall
Only workaround is to use Public DNS manually. But once I changed back DNS settings to "Automatic", I can't reach DNS server.
Host Machine (Mac) is connected to Internet
ipconfig ơn Windows 11:
And other guest OS (RHEL) is connected to Internet.