HP CIFS Server Release Notes Version A.03.01.01 HP-UX 11i v2 and HP-UX 11i v3

Issue
No 64 bit Windows XP clients can connect to the CIFS Server when configured with smb.conf
parameter security=server. Other Windows clients, including the 64-bit version of Windows
XP clients by default , might also fail to connect if they have the local policy for LAN Manager set
to Send NTLM response only.
Workaround
Using the Administrative Tool on each failing client:
1. Select Local Security Policy.
2. Select Local Policies.
3. Select Security Options.
4. Select Network security: LAN Manager authentication level.
5. Set the authentication level to Send LM & NTLM response or Send LM & NTLM - use
NTLMv2 session security if negotiated.
Issue
When using the smbpasswd command during the first time you add a Samba user to a new CIFS
Server installation, the command might respond with a misleading message as in the following
example:
./smbpasswd -a user1
New SMB password:
Retype new SMB password:
The misleading messages appear as follows:
startsmbfilepwent_internal: file /var/opt/samba/private/smbpasswd did not exist.
File successfully created.
account_policy_get: tdb_fetch_uint32 failed for field 1
(min password length), returning 0
account_policy_get: tdb_fetch_uint32 failed for field 2
(password history), returning 0
account_policy_get: tdb_fetch_uint32 failed for field 3
(user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32 failed for field 4
(maximum password age), returning 0
account_policy_get: tdb_fetch_uint32 failed for field 5
(minimum password age), returning 0
account_policy_get: tdb_fetch_uint32 failed for field 6
(lockout duration), returning 0
account_policy_get: tdb_fetch_uint32 failed for field 7
(reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32 failed for field 8
(bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32 failed for field 9
(disconnect time), returning 0
account_policy_get: tdb_fetch_uint32 failed for field 10
(refuse machine password change), returning 0
Added user user1
The user is added correctly, and the misleading messages only appear with the first occurrence
of adding a new Samba user.
Workaround
Verify that the user has been added correctly, and ignore the misleading messages.
Known issues and workarounds 9