i found the topic about "No logon workstation trust account (0xc0000199)". i've the same problem using freeradius-2.0.0-pre2 samba 3.0.24 on debian etch is it required to update to samba 3.0.28 (debian unstable) to fix this issue, or could it be anything else? thx michael freeradius-log: +- entering group MS-CHAP rlm_mschap: No Cleartext-Password configured. Cannot create LM-Password. rlm_mschap: No Cleartext-Password configured. Cannot create NT-Password. rlm_mschap: Told to do MS-CHAPv2 for host/trelane.ka.foobar.de with NT-Password expand: --username=%{mschap:User-Name} -> --username=trelane$ mschap2: 95 expand: --challenge=%{mschap:Challenge} -> --challenge=36fc487a5fe99e03 expand: --nt-response=%{mschap:NT-Response} -> --nt-response=b8ec109fa4b1a1ed3b2832f4e9704456febebeb4d790574e Exec-Program output: No logon workstation trust account (0xc0000199) Exec-Program-Wait: plaintext: No logon workstation trust account (0xc0000199) Exec-Program: returned: 1 rlm_mschap: External script failed. rlm_mschap: FAILED: MS-CHAP2-Response is incorrect ++[mschap] returns reject -----Original Message----- From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Phil Mayers Sent: 01 October 2007 09:55 To: FreeRadius users mailing list Subject: Re: 802.1x machine authentication patch help On Fri, 2007-09-28 at 12:06 +0100, Marco Casulli wrote:
Hi Jamie,
Marco from BBC in london.
I have read your message (http://lists.cistron.nl/pipermail/freeradius-users/2005-November/0485 76.html related to the error when the radius is trying to authenticate
in AD and I am getting exactly the same message.
"No logon workstation trust account (0xc0000199)".
The article is dated Nov 2005 so I hope you have the solution by now! ;-)
You need a suitably recent version of Samba. I can't remember the exact version number, but I'm sure judicious use of Google will find it, or just use the most recent.
Michael Patzer wrote:
i found the topic about "No logon workstation trust account (0xc0000199)".
i've the same problem using freeradius-2.0.0-pre2 samba 3.0.24 on debian etch
is it required to update to samba 3.0.28 (debian unstable) to fix this issue, or could it be anything else?
It's completely determined by Samba. I would ask the Samba people where or not this was possible. Alan DeKok.
participants (2)
-
Alan DeKok -
Michael Patzer