Our AD group tried to move our main domain controller this morning and RADIATOR stopped authenticating users until the RADIATOR process on each RADIUS server was manually restarted.
RADIATOR is configured to use <AuthByLSA>, and is only configured to use a default domain, not a specific domain controller. The relevant lines from the configuration file are: <AuthBy LSA> Identifier authUIOWA UsernameMatchesWithoutRealm DefaultDomain IOWA Group ITS-WIRELESS-FLAT EAPType MSCHAP-V2 </AuthBy> My log level was set to 2 so the only messages in the auth log where "user not found". Is this normal operation for RADIATOR ? Shouldn't RADIATOR try a different domain controller if the one it is currently using is down ? Thanks. -Neil -- Neil Johnson Network Engineer The University of Iowa Phone: 319 384-0938 Fax: 319 335-2951 Mobile: 319 540-2081 E-Mail: neil-john...@uiowa.edu
_______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
