CIFS Release Notes

Workaround
When prompted, answer "overwrite changes" otherwise the file must be saved under a
different name.
To avoid the error altogether, a registry change can resolve the problem as described in the
MS knowledge base article found at http://support.microsoft.com/default.aspx?kbid=324491
Samba community also observed the problem and has further characterized it in the Bugzilla
at https://bugzilla.samba.org/show_bug.cgi?id=1094
• Problem
Because of increased Windows security requirements, profile storing may 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 as this will result in incorrect ownership of the files
created on those shares.
• Problem
64 bit Windows XP clients cannot connect to the CIFS Server when it is configured with
smb.conf parameter "security=server". Other Windows clients could also fail to connect
if they have the local policy for LAN Manager set to "Send NTLM response only" as
does the 64 bit Windows XP clients by default.
Workaround
Use the Administrative Tool and proceed with the following steps 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 it to "Send LM & NTLM response" or "Send LM & NTLM - use NTLMv2
session security if negotiated”.
• Problem
When using the smbpasswd command the first time you add a Samba user to a new CIFS
Server installation, the command may respond with a misleading message. See the following
example:
./smbpasswd -a user1
New SMB password:
Retype new SMB password:
The misleading messages are displayed 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
9