Hello MJ, I’m betting your issue is that your newly re-configured station have “Unknown CA” error right ? They do default to checking the server identity and do computer authentication.
If it’s the case, one solution to fix it. Issue a certificate on PacketFence (RADIUS service) that would be trusted by your clients. Issue a certificate from a MS PKI for example (AD CS). Make sure your workflow does accommodate the computer authentication on the LDAP source that you used (Make sure to match on ServicePrincipalName) Thanks, Ludovic Zammit [email protected] <mailto:[email protected]> :: +1.514.447.4918 (x145) :: www.inverse.ca <http://www.inverse.ca/> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu <http://www.sogo.nu/>) and PacketFence (http://packetfence.org <http://packetfence.org/>) > On Nov 9, 2020, at 10:45 AM, mj via PacketFence-users > <[email protected]> wrote: > > Hi, > > We are using packetfence with 802.1x authentication on our wired network. > This works nicely. > > However, what we have now repeatedly seen, is that after (bigger) windows > updates, the windows 10 clients 802.1x authentication configurations are > reset back to the default -> no network for the windows client. > > I know this is not packetfence's fault, but talking to microsoft is > difficult. :-) > > So, Anyone else here using wired 802.1x, and seeing this same behaviour..? > > Anyone with a clue on how to STOP this from happening? > > As the workstations then have NO connectivity, the only solution is to walk > to them, and re-configure the settings. (or turn off authentication on the > switch) > > Curious to your experiences. > > MJ > > > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
