HP CIFS Server Release Notes version A.03.01.06 (769570-002, June 2014)

files open by a process, too many locks, and performance degradation for the clients, since the
clients share a single SMBD process.
Workaround
For the Windows NT, you can set a registry parameter, MultipleUsersOnConnection , to 1,
which forces each terminal server client to negotiate its own connection, so that each client receives
a separate SMBD process. For the Windows 2000 terminal services, Microsoft provides a hotfix,
Q818528. You can apply this hotfix, and then set the following values:
Subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRxSmb\Parameters
Type:REG_DWORD
Entry: MultiUserEnabled
Value: 1
NOTE: Do not install the Q818528 hotfix on a system running Windows 2003. This hotfix only
applies to Windows 2000.
For more information, see the Microsoft Q818528 article: http://support.microsoft.com/
Issue
The The file may have been changed error message appears when you save an Excel file
to Samba. The error message also provides choices to either save a copy or overwrite
changes.
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.
Known issues and workarounds 11