HP CIFS Server Release Notes Version A.03.01.03 (5900-1997, October 2011)

Issue
A non-root user running smbstatus might receive the following errors when HP CIFS Server is
not started and tdb files have not been initialized:
could not open file /var/opt/samba/locks/sessionid.tdb: No such files
or directory
Error: Failed to initialize locking database
Workaround
The current version of smbstatus does not allow a normal user to initialize tdb files. A normal
user must perform smbstatus after HP CIFS Server is started by root, or tdb files have been
initialized.
Issue
Changing the password stored in the smbpasswd file from a Windows XP machine without the
sign-and-seal patch fails and corrupts the user's password.
Workaround
The administrator must reset the password.
Issue
When you use terminal server clients to access to shares on a CIFS server, all of the clients from
that terminal server connect over a single virtual connection and are serviced by a single SMBD
process on the CIFS Server. These actions might lead to a number of issues, including too many
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/default.aspx?kbid=818528
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 copyor overwrite
changes.
Workaround
When prompted, select overwrite changes otherwise the file must be saved under a different
name.
Known issues and workarounds 9