This is confirmed by looking at the security event logs where I can see events 4625 and 6273. So it took them 2 weeks to come to that conclusion when the subject line of my premiere ticket had the E691 error code in it which means mismatched username and password and despite the very lengthy paragraph of me explaining that I have done everything possible to ensure it is not a bad username and password. It's possible there is some other potential incompatibility there, but so far I haven't been able to reproduce it here so I can't say for sure what might fix it yet. According to Pfsense documentation its possible to migrate configuration. The Subject fields indicate the account on the local system which requested the logon. Can anybody on here advise or should I be posting this to the Freeradius mailing list? Cannot perform authentication Date: Fri, 30 Oct 2015 12:15:11 +0000 My mistake.
However, before reinstalling Windows I did do a reset on the computer account. To find which part goes wrong, a few tests should be implemented. Now the passwords are stored as clear text even in the database. The most common types are 2 interactive and 3 network. Either the user name provided does not map to an existing user account or the password was incorrect. The Logon Type field indicates the kind of logon that was requested.
Here are the additional tests I have performed. I can post the debug info I am getting if requested. Besides, note that your password is case sensitive. I didn't read far enough. So at least I know it is the password it is failing on.
The authentication side of things is another matter. The Subject fields indicate the account on the local system which requested the logon. The client machine being a Windows 8. However, before reinstalling Windows I did do a reset on the computer account. This is confirmed by looking at the security event logs where I can see events 4625 and 6273.
I didn't read far enough. The problem is the response I get back is always an access-reject message with a reason code of 16 Authentication failed due to a user credentials mismatch. Your sub status comment should help. This seemed highly unlikely to me so I asked for some documentation stating this for which he then change the subject and never provided any documentation. Support for this will go away soon. Ferraris, 2 - 42122 Reggio Emilia Tel.
This seems like an upstream issue, not like an issue with the Debian packaging. If anyone can confirm this before I do please let me know. Did you restart radiusd after adding the realm? If someone posts a solution or has comments I will respond. Now I know this is common especially among failed logons but given that this issue is stating an invalid username or bad password, perhaps it matters in this case. The Network Information fields indicate where a remote logon request originated. All in all it is a fairly basic setup and hopefully I have provided enough information for someone to get an idea of what might be going on. From this document you can see what these codes mean:.
The current version can be obtained from. Ferraris, 2 - 42122 Reggio Emilia Tel. Funny how easy it is to find these articles after you no longer need them. Support for this will go away soon. You should see version 0. After replacing two pieces of hardware most appliances came up correctly as intended, however after reinstalling Freeradius 3 over the previously installed Freeradius 2. Either the user name provided does not map to an existing user account or the password was incorrect.