+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
Best answer by rcorbin
Is this something that might now be resolved in MacOS 26.4.1 ?
Apple’s Enterprise release notes reveal that this resolves “an issue where MacBook Air with M5 and MacBook Pro with M5 Pro or M5 Max failed to join 802.1X Wi-Fi networks while using content filter extensions.”
https://eclecticlight.co/2026/04/09/apple-has-just-release-an-update-to-macos-tahoe-to-version-26-4-1/
Hey .. 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.
Hi, I’ve encountered similar issue, however eapolclient logs show that the EAP request is received, and a response identity is sent to the access point, and the access point confirms, that it received it with State=Acquired Status=OK (0). Then mac transmits a couple of EAPOL Start (1), and then it times out.
We are experiencing similar issues with an 16in Macbook Pro M5 and EAP-TLS WiFI. We noticed that when we turn off the Crowdstrike Falcon sensor, the wifi connects. Is this a hardware issue? Has anyone spoke to Apple?
Is this something that might now be resolved in MacOS 26.4.1 ?
Apple’s Enterprise release notes reveal that this resolves “an issue where MacBook Air with M5 and MacBook Pro with M5 Pro or M5 Max failed to join 802.1X Wi-Fi networks while using content filter extensions.”
https://eclecticlight.co/2026/04/09/apple-has-just-release-an-update-to-macos-tahoe-to-version-26-4-1/
Is this something that might now be resolved in MacOS 26.4.1 ?
Apple’s Enterprise release notes reveal that this resolves “an issue where MacBook Air with M5 and MacBook Pro with M5 Pro or M5 Max failed to join 802.1X Wi-Fi networks while using content filter extensions.”
https://eclecticlight.co/2026/04/09/apple-has-just-release-an-update-to-macos-tahoe-to-version-26-4-1/
This worked for us. our Pre-Sales Apple Engineer suggested we do the update and it worked swimmingly.
+4Is this something that might now be resolved in MacOS 26.4.1 ?
Apple’s Enterprise release notes reveal that this resolves “an issue where MacBook Air with M5 and MacBook Pro with M5 Pro or M5 Max failed to join 802.1X Wi-Fi networks while using content filter extensions.”
https://eclecticlight.co/2026/04/09/apple-has-just-release-an-update-to-macos-tahoe-to-version-26-4-1/
This worked for us. our Pre-Sales Apple Engineer suggested we do the update and it worked swimmingly.
I haven’t had access to the hardware to test yet, but hopeful it will resolve our issue especially after you’re comments.
Is this something that might now be resolved in MacOS 26.4.1 ?
Apple’s Enterprise release notes reveal that this resolves “an issue where MacBook Air with M5 and MacBook Pro with M5 Pro or M5 Max failed to join 802.1X Wi-Fi networks while using content filter extensions.”
https://eclecticlight.co/2026/04/09/apple-has-just-release-an-update-to-macos-tahoe-to-version-26-4-1/
It worked for us as well 🙂
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
