As far as I remember, the VMC client application can be configured to use various parameters - static/dynamic IP, static/dynamic dns etc. - once set, these settings should be read by windows and applied to the registry, typically under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces{GUID}
Which is then read for the appropriate information by services that need network access.
For now, I have two options: stay with CISA V5, or disable the CIS Firewall Driver and use the Windows Firewall while I'm on the adapter.
If you don’t want to keep installing/removing version 6, just disable te driver and use Windows firewall.
By the way, is this an indication that the problem is not really a DNS server problem?(CIS Firewall not selected):
C:\Windows\system32>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=1120ms TTL=43
Reply from 8.8.8.8: bytes=32 time=453ms TTL=43
Reply from 8.8.8.8: bytes=32 time=613ms TTL=43
Reply from 8.8.8.8: bytes=32 time=427ms TTL=43Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 427ms, Maximum = 1120ms, Average = 653ms(CIS Firewall selected):
C:\Windows\system32>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),C:\Windows\system32>
It’s obviously an indication that something is not working correctly but I’d guess this is just part of a larger problem, which, if solved, will also correct the DNS issues.
I'll be happy to heed any advise you may come up with, but even if you're at a dead end as well, thanks for all your efforts.
Can you remind me what settings you have in the VMC client application please?