Fixed! Thanks Alan and other users for the help! usermod -a -G wbpriv radiusd radtest -t mschap Administrator nexa.2016 localhost 1234 testing123 Sending Access-Request Id 11 from 0.0.0.0:42285 to 127.0.0.1:1812 User-Name = 'Administrator' NAS-IP-Address = 127.0.0.1 NAS-Port = 1234 Message-Authenticator = 0x00 MS-CHAP-Challenge = 0x861aa408caf9ecc0 MS-CHAP-Response = 0x0001000000000000000000000000000000000000000000000000e703a1b74c04b5304049dce9dbb0a48de40c4f9dccf1ade7 Received Access-Accept Id 11 from 127.0.0.1:1812 to 127.0.0.1:42285 length 84 MS-CHAP-MPPE-Keys = 0x MS-MPPE-Encryption-Policy = Encryption-Allowed MS-MPPE-Encryption-Types = RC4-40or128-bit-Allowed FInally I need to test against a Switch! On Fri, Sep 23, 2016 at 11:01 AM, Marcelo Martinez < marcelo.martinez@nexa.com.uy> wrote:
Yes I'M using radius as root.
On Fri, Sep 23, 2016 at 10:52 AM, Alan DeKok <aland@deployingradius.com> wrote:
On Sep 23, 2016, at 9:41 AM, Marcelo Martinez < marcelo.martinez@nexa.com.uy> wrote:
winbind and ntlm_auth are fine:
Then the problem is the interaction between FreeRADIUS and winbind.
Are you running FreeRADIUS as root?
Does FreeRADIUS have permission to read the winbind socket?
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list /users.html