-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Bartlett wrote:
| If that's what caused the issue, then there is a bug
| (which I'm happy to look into and fix).
| The intention of the logic was that if the value was
| undefined in LDAP, the flags would be set to PDB_DEFAULT and it
| would
On Mon, 2004-07-05 at 06:56, Gerald (Jerry) Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sat, 3 Jul 2004, Tilo Lutz wrote:
>
> > None of my acounts in ldap have set sambaPwdLastSet, even those acounts
> > which became disabled. If I have understand you right, samba shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 3 Jul 2004, Tilo Lutz wrote:
> None of my acounts in ldap have set sambaPwdLastSet, even those acounts
> which became disabled. If I have understand you right, samba should not
> disable account if the attribute sambaPwdLastSet is not defined
Hi
> > > TL> I have a problem with samba 3.0.5pre1.
> > > TL> Many of my users are disabled by samba
> > > TL> and I can't find the reason why.
> > > Hmm, not shure, did you look at the eventlog from your win box ??
> > > i had something alike, (before 304) and the win log showed that
> > > the pa
On Sat, 2004-07-03 at 18:15, Tilo Lutz wrote:
> Hi
>
> > TL> I have a problem with samba 3.0.5pre1.
> > TL> Many of my users are disabled by samba
> > TL> and I can't find the reason why.
>
> > Hmm, not shure, did you look at the eventlog from your win box ??
> > i had something alike, (before 30
Hi
> TL> I have a problem with samba 3.0.5pre1.
> TL> Many of my users are disabled by samba
> TL> and I can't find the reason why.
> Hmm, not shure, did you look at the eventlog from your win box ??
> i had something alike, (before 304) and the win log showed that
> the password change was corru
Hmm, not shure, did you look at the eventlog from your win box ??
i had something alike, (before 304) and the win log showed that
the password change was corrupt (was a bug before 304)..
there might be some debug info there..
for the rest, i dunno..
