2.2.0-alpha1 and smbpasswd -j

[Axel Thimm]

On Sun, Jan 28, 2001 at 10:17:08AM -0700, Patrick wrote:
> Axel Thimm wrote:
> > On Sun, Jan 28, 2001 at 10:35:09AM +0100, Axel Thimm wrote:
> > > I cannot join a Samba PDC with a Samba member both running 2.2.0-alpha1:
> > > [...]
> > > On the other hand it has been reported to me that NT4 could successfully
> > > join the domain (W9x anyway).
> > I managed to narrow down the problem: It seems that 2.2 clients cannot
> > register to 2.2 PDCs, while a 2.0.7 client can. E.g., if the PDC is
> > running 2.2.0-alpha1, then a client calling smbpasswd from 2.2.0-alpha1
> > yields:
> > > [root at puariko samba]# /usr/beta/bin/smbpasswd -j physik -D3
> [...]
> > > cli_pipe: return critical error. Error was code 0
> > > cli_pipe: return critical error. Error was code 0
> > > modify_trust_password: unable to obtain domain sid from PASSWD. Error was :
> > > code 0.
> > > 2001/01/28 15:14:09 : change_trust_account_password: Failed to change password
> > > for domain PHYSIK.
> > > Unable to join domain PHYSIK.
> > while the 2.0.7 smbpasswd does the job right (no other changes, client's
> > smbd/nmbd not running in both cases):
> > > [root at puariko samba]# smbpasswd -j physik -D3
> [...]
> > > 2001/01/28 15:14:25 : change_trust_account_password: Changed password for
> > > domain PHYSIK.
> > > Joined domain PHYSIK.

> I know this may sound stupid but did you add the machine account for the samba
> member machine?   If so did you delete it in all occurrences and  try adding the
> account again?

Yes, I did and checked that I did. And in the example above, I first try to
join (and thus change the password) with the unsuccessfull 2.2.0-alpha1 and
then with the successfull 2.0.7.

So at all times the passwd/smbpasswd was in the right state.

Has anyone joined 2.2.0-alpha1 domains from 2.2.0-alpha1 clients (under
OSF1 or Linux)?
-- 
Axel.Thimm at physik.fu-berlin.de