I would compare the LDAP attributes between a problem machine and a
working machine. Each machine has to have a unique unix account name
and SID.
Normally you don't need to precreate the samba acct with "smbpasswd -a
-m" or pdbedit. However it may help with the diagnostics to see
what is not getting created. If you use smbpasswd or pdbedit to create
the account, then use the ldap editor to fill in the missing attributes
then you should be able to join the domain.
Also double check that machine accounts are not being created in some
other LDAP ou than you expected. you might be trying to fix one ldap
entry while samba is creating one somewhere else.
It gets tricky when you use smbpasswd or pdbedit to create an account
and it sees some attributes ther
On 06/14/13 07:49, Luis H. Forchesatto wrote:
> Hi Gaiseric
>
> Thanks for the reply.
>
> I believe the problem is not the flags but I will check them again as
> you suggested. I've found quite annoying this problem because is not
> on my network, it's on a remote network and I need to move physically
> to another place in order to test the environment, quite boring also.
>
> Regarding the sambaPrimaryGroupSID I'll check again but I believe it
> MAY be the problem :) Also, can this cause this problem? "Another
> machine was already created previously..." something like....?
>
>
> 2013/6/10 Gaiseric Vandal <
gaiseri...@gmail.com
> <mailto:
gaiseri...@gmail.com>>
> --
> Att.*
> *
> Luis H. Forchesatto