I have a case open on this but I thought I'd throw it out to the community to see if anyone has run across this. I'm running UAC 3.1R4 (just upgraded from 3.0R1 last weekend and saw this same issue on that code revision). I'm using EAP-TTLS with EAP-JUAC as the inner protocol. UAC is using native AD as the backend auth server and everything works just fine with that configuration. I use OAC 4.72 and 5.10 as the client in this configuration. However, when I try to add any other inner protocol to the .1x authentication set, I cannot authenticate with AD creds. In fact, even if I add other outer protocol, such as EAP-PEAP, the only inner protocol that will work with it is EAP-JUAC. I've tried multiple clients (Windows and WIndows CE) with this and none work (not using JUAC as the inner protocol in those tests, obviously). A twist is that if I switch the auth server for the realm to native admin creds, any combination of outer and inner EAP protocols works just fine. Looks like a bug to me and JTAC is having me redo the AD setup, but I'm not confident this is going to help the situation at all. Thanks in advance... ... View more

Hello - I'm testing AD authentication with my IC4000. The IC4000 is properly configured with the AD domain-controller information and the IC-4000 successfully added itself to the domain. However, all my user authentication is failing. The domain-controller is reporting error messages 5722 and 5723: The session setup from the computer JRADIUS2 failed to authenticate. The name of the account referenced in the security database is JRADIUS2 . The following error occurred: Access is denied. -------------- The session setup from the computer JRADIUS2 failed because there is no trust account in the security database for this computer. The name of the account referenced in the security database is JRADIUS2$. Anyone have any ideas? ... View more