CIFS-SERVER Release Notes (5900-1765, September 2011)

Workaround
When prompted, select overwrite changes otherwise the file must be saved under a different
name.
To avoid this error, change the registry as described in the Microsoft knowledge base article at
http://support.microsoft.com/default.aspx?kbid=324491
The Samba community also addressed the issue and has further characterized it on the Bugzilla
webpage at https://bugzilla.samba.org/show_bug.cgi?id=1094
Issue
Because of increased Windows security requirements, profile storing might fail if adequate authority
has not been configured for roaming profiles.
Workaround
Set profile acls = yes for the profile share used for the user profile files. Do not set profile
acls = yes on normal shares because this causes the incorrect ownership of the files created
on those shares.
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
Known issues and workarounds 9