Re: Radius 2.22.40: Can't authenticate against NT

Darryl Ackernecht ( )
Wed, 4 Feb 1998 17:20:16 -0500

We did get this working - a reinstall of NT solved the problem (it was a
development machine). The only extra right that we granted was Log on

Darryl Ackernecht

-----Original Message-----
From: Kurt Schafer <>
To: <>
Date: Tuesday, February 03, 1998 3:17 PM
Subject: Re: Radius 2.22.40: Can't authenticate against NT

>Uhm, is the name of your NT domain "DOMAIN"
>ie, if the name of the NT domain you log into is FLUFFY your password entry
>for the user you want to authenticate via the SAM should read
>- Kurt
>-----Original Message-----
>From: Darryl Ackernecht <>
>To: RadiusNT Mailing List <>
>Cc: Darryl Ackernecht <>
>Date: Monday, February 02, 1998 5:13 PM
>Subject: Radius 2.22.40: Can't authenticate against NT
>>We've been unsuccessful in trying to get RadiusNT to authenticate against
>>the NT SAM. So far we've been testing by starting up with 'radius -x15'
>>the command prompt, logged into the domain as an Administrator (using
>>radlogin to test).
>>Here is our USERS file:
>>testuser Password="WINNT\DOMAIN"
>> User-Service=Framed-User
>>Debug output:
>>radrecv: Request from host ac100810 code=1, id=1, length=0
>> NAS-Identifier =
>> NAS-Port = 0
>> User-Name = "testuser"
>> Password = "\356\0228|U;$)\355\2139\336M\345\316P"
>>Checking user record PW_PASSWORD type
>>chkPwd->strvalue is WINNT\DOMAIN
>>decrypted pwd is newpass
>>(WINNT) User:testuser Domain:DOMAIN Password:newpass
>>Sending Reject of id 1 to ac100810 (
>>Resp Time: 10 Auth: 1/2 -> 3 Acct: 0/0/0 -> 0
>>We don't have any problems trying to authenticate a non-NT user. Any help
>>would be appreciated.
>>Darryl Ackernecht