From: Holger Rauch on
Hi,

I'm using Samba 3.2.5 in conjunction with kernel 2.6.26-2-686-bigmem
(Debian Lenny) and recognized that when setting up ldapsam:editposix
in accordance with

http://wiki.samba.org/index.php/Ldapsam_Editposix

it turns out that

net rpc info -U Administrator

on Linux box works as expected, whereas

net rpc join -U Administrator

yields NT_STATUS_LOGON_FAILURE

In the server log (file <ip-address-of-server>.log) I see

=======

change_to_user: SMB user nobody (unix user nobody, vuid 100) not
permitted access to share IPC$.
[2009/10/23 17:19:00, 0] smbd/service.c:make_connection_snum(1086)
Can't become connected user!
[2009/10/23 17:19:00, 3] smbd/connection.c:yield_connection(31)
Yielding connection to IPC$
[2009/10/23 17:19:00, 3] smbd/error.c:error_packet_set(61)
error packet at smbd/reply.c(662) cmd=117 (SMBtconX)
NT_STATUS_LOGON_FAILURE

=======

So, it seems like "Administrator" is mapped to "nobody" on the Linux
side. I checked the Administrator account in LDAP using JXplorer to
verify whether it's not only a smabaSamAccount, but also a
posixAccount. It indeed is.

Any idea what's wrong. Do I have to perform any additional stetps
(right granting, user mapping, etc. for the Administrator user)?

Do I have to create an additional root user in the LDAP database and
then run "smbpasswd -a" for that user?

Thanks in advance for any info.

Kind regards,

Holger
 | 
Pages: 1
Prev: samba+ldap
Next: [Samba] NTConfig.POL ignored