Samba 2.2.0alpha1 snapshot released

[Richard Bollinger]

You might want to try re-joining the NT domain.  Although I can't explain
it, I found the same behaviour when attempting to test 2.2.0-alpha0 on a
machine which had been running 2.0.7 with DOMAIN authentication.  I think
the smbpassword authentication is just a fall-back in case the other method
fails.  It's probably possible to compile or configure that method out of
consideration.

Rich Bollinger, Elliott Company
----- Original Message -----
From: "Jason Haar" <Jason.Haar at trimble.co.nz>
To: "David Bannon" <D.Bannon at latrobe.edu.au>
Cc: <samba-technical at samba.org>
Sent: Thursday, November 23, 2000 11:22 PM
Subject: Re: Samba 2.2.0alpha1 snapshot released


> On Fri, Nov 24, 2000 at 02:50:39PM +1100, David Bannon wrote:
> > At 04:12 PM 24/11/2000 +1300, Jason Haar wrote:
> > >Why is it looking for *only* for smbpasswd.
> > >
> >
> > No, not 'only', why smbpasswd at all !
> >
> > Please check back further in the log to the part where the smb.conf file
is
> > read and see what it is saying about the 'security = '  and 'password
> > server =' lines.
>
> No mention of either of those two in the logs, however, testparm returns:
>
> security = DOMAIN
> encrypt passwords = Yes
> update encrypted = Yes
> allow trusted domains = Yes
> hosts equiv =
> min passwd length = 5
> map to guest = Never
> null passwords = No
> password server = PDC BDC
> smb passwd file = /etc/smbpasswd
> root directory =
>
> So everything looks as it should...
>
> --
> Cheers
>
> Jason Haar
>
> Unix/Special Projects, Trimble NZ
> Phone: +64 3 9635 377 Fax: +64 3 9635 417
>