2/23/2023 0 Comments Ipv4 not connected windows 10![]() but windows uses only my local dns on the client side / not from the pfsense server side. Although nslookup on dual stack is not slow the ping is also as fast as expected if I disable Make Windows 10 Clients Block access to DNS servers except across OpenVPN while connected, forcing clients to use only VPN DNS servers. It feels like win10 tries to use ipv6 first and than falls back to ipv4 but that's just a guess. If I disable ipv6 on the windows system everything works as expected. If now a win10 client having dual stack (ipv4 and ipv6) requests to the ipv4 targets take several seconds (nsookup returns instantly while ping takes ~10 sec). on the server to work around the issue that the win10 systems uses the first dns in the network stack instead of using the openvpn dns. Make Windows 10 Clients Block access to DNS servers except across OpenVPN while connected, forcing clients to use only VPN DNS servers. The openvpn tunnel is running on ipv4 only and i checked ![]() This happens whether from an image, or from the HP build. ![]() ![]() But not only annoying, it stops O365 products, they report no connection so are not available properly. OpenVPN clients on win10 have now trouble using the dns thru the tunnel if they have a dual stack connection. The (wired, we don't have wifi internally to test) network connection shows a yellow exclamation mark with 'no internet access' next to it. Our office pfsense (2.5.1) is connected to the internet with ipv4 only. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |