Mario Gzuk schrieb:
Hi,
Am Montag, den 17.03.2008, 13:41 -0400 schrieb Adam Tauno Williams:
we have similiar problems with samba+ldap after updating to 3.0.27.
But in our case, the following ldap-Attributes won't get updated:
sambaPwdMustChange
sambaPwdCanChange
only sambPwdLastSet gets altered.
in newly created accounts the two Attributes even won't be created !?
I already checked every log-file i can think of, I played with verbose
logging, but I really can't find a solution up to now.
I also asked about this stuff here in the mailinglist several weeks ago,
but no answer til now.
So what could we do ?
Is there a policy set to affect these attributes?
littleboy:~ # pdbedit -P "minimum password age"
account policy value for minimum password age is 86400
littleboy:~ # pdbedit -P "maximum password age"
account policy value for maximum password age is 5184000
We have a policy for the maximum password age (value is: 15552000). But
this doesnt matter. The timestamps in the LDAP get updated correctly,
but the pdbedit -Lv user shows the wrong dates and the functionality is
broken as you may read in my previous mail...
A similar problem was reported in "Strange NT_STATUS_PASSWORD errors
after upgrade to 3.0.26a" if you search the lists (actually, I see you
mentioned it, too).
I guess this bug is worth reporting on http://bugzilla.samba.org?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba