I'm currently dealing with a frustrating 802.1x authentication issue on my network setup, which includes an HP Procurve switch, Microsoft NPS, and a Windows 10 client. My admin logins work perfectly with Radius, and they even show up in the event log, but I can't seem to get 802.1x authentication to work. The NPS receives the request but doesn't log anything—unless there's a bad username or password, in which case it logs the failure. The logs appear to suggest a successful connection, but the switch and client are just not cooperating. Occasionally, I see an "unexpected EAP response" error on the switch. Has anyone successfully set up a similar configuration? I'm eager to see some sanitized settings from a working setup to help identify what I'm missing!
4 Answers
It might help if you provide more specifics about your NPS configuration. Are you using EAP-TLS or something else? Also, make sure you've enabled both success and failure logs in NPS for troubleshooting. This can often be done via GPO or a secdit command. You may find some hidden details in those logs that could point you in the right direction.
I've faced some similar issues when upgrading systems, especially when Windows 11 is involved; it can complicate things with hidden settings and configurations. Ensure your VLANs are set correctly, and double-check that all relevant authentication settings are applied consistently across clients and switches. Sometimes, even small overlooked details can disrupt the whole setup. Good luck with it all!
It sounds like you've made some good progress. I had a similar issue before and swapping to a different model like you did with the switch sometimes makes all the difference. If you share sanitized configs once you're ready, it might help others. Glad to hear the logs started appearing after that switch change! Keep us posted on whether that fix remains consistent.
Check your Network Adapter settings on the Windows 10 device. Make sure that the "Enable IEEE 802.1X" option is checked, and confirm that you're using the correct EAP method, like PEAP or EAP-TLS. If you're using PEAP, try unchecking the option to validate the server certificate during testing. Also, that EAP response error you're encountering often relates to fragmented packets, which can be resolved by updating the ProCurve firmware if it's outdated.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures