The reality is that it broke "something* in certain lpt2/ipsec connections using certain authentication protocols, although they haven’t yet specified which particular connection technologies are affected.
However this does not mean that a blanket affect of ALL VPN connection not working is an issue.
So far we are unaffected on clients using ipsec and PAP protocol authentication, nor connections using Anyconnect (aka Cisco Secure Connect).
I have also not seen any affect on private VPN clients such as PIA or Nord on machines that have this update.
I suspect what broke was clients using MSChap, Microsoft’s own protocol for authentication for VPN clients.
Source: an admin with 200+ client machines with VPN connections that are not impacted after installing this update.
The reality is that it broke "something* in certain lpt2/ipsec connections using certain authentication protocols, although they haven’t yet specified which particular connection technologies are affected.
However this does not mean that a blanket affect of ALL VPN connection not working is an issue.
So far we are unaffected on clients using ipsec and PAP protocol authentication, nor connections using Anyconnect (aka Cisco Secure Connect).
I have also not seen any affect on private VPN clients such as PIA or Nord on machines that have this update.
I suspect what broke was clients using MSChap, Microsoft’s own protocol for authentication for VPN clients.
Source: an admin with 200+ client machines with VPN connections that are not impacted after installing this update.