We upgraded our Samba DCs from 3.0.11 to 3.0.13 last week and now see that some
tools are reporting the incorrect password expiration date.  Running pdbedit for
both 'maximum password age' and 'maximum password age (seconds since 1970)' fails.

[root@rchs10dc locks]# /usr/local/samba/bin/pdbedit -P "maximum password age
(seconds since 1970)"
account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password age
(seconds since 1970)), returning 0
valid account policy, but unable to fetch value!

[root@rchs10dc locks]# /usr/local/samba/bin/pdbedit -P "maximum password age"
No account policy by that name
Account policy names are :
min password length
password history
user must logon to change password
maximum password age (seconds since 1970)
minimum password age (seconds since 1970)
lockout duration
reset count minutes
bad lockout attempt
disconnect time
refuse machine password change

Dumping the tdb shows only the old name:

[root@rchs10dc locks]# ../../bin/tdbdump account_policy.tdb
<cut most output>
{
key = "maximum password age\00"
data = "\00\A7v\00"

I worked around the issue by using tdbtool to insert a new key value pair with a
key of "maximum password age (seconds since 1970)"