On Thu, 27 Nov 2003 [EMAIL PROTECTED] wrote: > bash-2.05# /opt/samba/bin/wbinfo -a login%password > plaintext password authentication failed > error code was NT_STATUS_INVALID_PARAMETER (0xc000000d) > error messsage was: Unexpected information received > Could not authenticate user login%password with plaintext password > challenge/response password authentication succeeded
Then you need to investigate what in your Samba installation is not working correctly. This is a Samba question and is best answered in the Samba forums. As long as you have this Samba problem there is very slim chances authentication via Samba will work properly. > bash-2.05# /opt/samba/bin/ntlm_auth --username=login > password: > NT_STATUS_OK: Success (0x0) This is the same as the challenge/response test above.. > PS: can you tell me why I have that in my cache.log: > [2003/11/27 17:00:49, 0] lib/charcnv.c:init_iconv(134) > Conversion from UCS-2LE to CP850 not supported > [2003/11/27 17:00:49, 0] lib/charcnv.c:init_iconv(134) > Conversion from UTF8 to CP850 not supported > [2003/11/27 17:00:49, 0] lib/charcnv.c:init_iconv(134) > Conversion from 646 to CP850 not supported > [2003/11/27 17:00:49, 0] lib/charcnv.c:init_iconv(134) > Conversion from CP850 to UCS-2LE not supported > [2003/11/27 17:00:49, 0] lib/charcnv.c:init_iconv(134) > Conversion from CP850 to UTF8 not supported > [2003/11/27 17:00:49, 0] lib/charcnv.c:init_iconv(134) > Conversion from CP850 to 646 not supported > [2003/11/27 17:00:49, 0] lib/charcnv.c:init_iconv(134) > and so on This might hint as to where the problem is. It seems your clients or server are running with a national code page not supported by Samba. But I am sure the Samba people can give a clear explanation. Regards Henrik
