cancel
Showing results for 
Search instead for 
Did you mean: 

Authentication using machine credentials with 2.2R2 and Odyssey 4.8

bhrume_
Not applicable

Authentication using machine credentials with 2.2R2 and Odyssey 4.8

Hello all,

I'd like to use machine account authentication and machine credentials WITHOUT using certificate but only with the machine AD password.

I've configured the OAC, but if I reboot the station, the authentication fails:

Info AUT23457 2008-11-25 15:44:29 - rtlbruinfranet01 - [0.0.0.0] RTLNET\rtlbrulap1365$(Realm_RTL_Users)[] - Login failed using auth server Active Directory (Samba). Reason: Failed Info AUT24327 2008-11-25 15:44:29 - rtlbruinfranet01 - [0.0.0.0] RTLNET\rtlbrulap1365$(Realm_RTL_Users)[] - Primary authentication failed for RTLNET\rtlbrulap1365$/Active Directory from 00-0D-56-B2-13-B3

If I use an AD user login/password, the authentication is successful (so I guess the UAC is correctly communicating with the Active Directory DCs):

Info AUT24326 2008-11-25 15:51:02 - rtlbruinfranet01 - [0.0.0.0] RTLNET\stest(Realm_RTL_Users)[] - Primary authentication successful for RTLNET\stest/Active Directory from 00-0D-56-B2-13-B3

Am I missing something ?

Thank you for your help

Message Edited by bhrume on 11-25-2008 06:57 AM
2 REPLIES 2
Raph_
Not applicable

Re: Authentication using machine credentials with 2.2R2 and Odyssey 4.8

Hi,

I have exactly the same issue with OAC 5.0 and 3.0R1 version of Infranet Controller.

Did you finally find a solution ?

Regards

Raphael

Ad_Nauseam_
New Contributor

Re: Authentication using machine credentials with 2.2R2 and Odyssey 4.8

I was experiencing this same issue in the lab on 2.2R3 with OAC 4.8. 1st and 2nd level J-TAC could not pin it down. Finally got a conf call with a really experienced guy out of the Cambridge office. He reviewed the OAC and IC config and found nothing wrong. The only thing we did was remove EAP-PEAP from the OAC machine auth config and after that machine auth started working. However, when I added EAP-PEAP back, it continued to work. In the end no one knows what was causing the issue we saw and it has not reoccurred since.

.joel