+4With the recent release of the M5, we’ve been trying to connect MacBook Pro’s to our 802.1x secured Wifi Network.
We’re using the same configuration profile that has worked on the rest of our fleet. Our network team have looked at the logs and have determined the issue is on the endpoint side “WLC keep sending EAP-TLS request and no response from client”.
Wondering if anyone else has encountered this issue and what if anything was done to fix it.
Thanks
+8Hey .. yes Im seeing with M5 systems and havn’t got a fix for it yet..
so far we have determined that on a non jamf enrolled mac - we can connected to our corp network wit no issued..
Then when enrolled - It seems to work for a few min / hours but if we reboot or let the mac sleep for a few min - it looses the connection and will never connect again …
very frustrating ...
I haven’t hit the M5-specific issue myself, but since your failure point looks like EAP-TLS/client response, I’d sanity-check the cert chain + Wi-Fi payload against Configuring a RADIUS Policy for macOS (with SCEP). It’s not Jamf-specific, but it has a solid checklist for the certificate / 802.1X pieces that usually break after enrollment, reboot, or sleep.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
