-----Oorspronkelijk bericht----- Van: freeradius-users- bounces+p.kaagman=atlascollege.nl@lists.freeradius.org [mailto:freeradius-users- bounces+p.kaagman=atlascollege.nl@lists.freeradius.org] Namens alan buxey Verzonden: woensdag 30 mei 2012 14:11 Aan: FreeRadius users mailing list Onderwerp: Re: Reading winbind reply failed! (0xc0000001)
Hi,
You were absolutely right.
hmmm, usually if there is group issues for that socket then you get some winbind_privileged error with the word 'crap' in it (literally!) - maybe 3.6.x has changed that behaviour/message? I'd have to look at the sourcecode of SAMBA...<shudder>
alan
Ghehe... Samba... it does the job... had a lot of fun with it in the past ;) Once heard that the kernel source had to be censured for use in Australia because of all the strong language in the comments.... this was back in the 2.2 time I think. But all I know is that authentication worked after I added the freerad user to the group winbindd-privileged. Ran into problems again with the authorization though... but will post separately on that subject. Peter