Forum Discussion
Solved
(Another) Issue with RADIUS authentication for some users
Hi I thought I'd found the solution to our problem in this Tech Community thread from 2021, only to find that there was only one reply. Our NPS logs looks very very similar to those described...
- Yes, for my few users the solution was to not use for example an "ä" in their password.
For everyone else running into this problem. Check for special characters in the passwords..
Are you suggesting this is the solution?
- Yes, for my few users the solution was to not use for example an "ä" in their password.
Further info: We found these two special characters to be problematic
- £
- ¬
Although I'd argue the £ sign isn't really 'special', but there we are.
All of these were fine for us:
`!"$%^&*()-=_+[]{};'#:@~,./<>?\|
It's still a mystery though, since passwords are (or should be!) passed as hashes anyway!
- Also, how the heck did you work that out?
- I found this link while troubleshooting the "Reason code: 21" error:
https://learn.microsoft.com/en-us/answers/questions/613549/intermittent-login-failed-with-azure-mfa-extension
The only answer there is from a Microsoft Employee and his first suggestion says you should not have unicode characters in the password.
Rather common characters not allowed that I have found triggering this error: ü, ö, ä, ß, §, €, £
If this is your problem, you will also get an eventlog entry in the Security log with ID 4625 ("Failure Reason: Unknown user name or bad password.")
- That's madness! Madness, I tell you!!