CIFS Release Notes

Workaround
Edit the smb.conf file manually to remove the wins server entry.
• Problem
A non-root user running smbstatus may 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 disallows a normal user to initialize tdb files. A normal
user must preform smbstatus after HP CIFS Server is started by root, or tdb files have been
initialized.
• Problem
Changing the password stored in the smbpasswd file from a Windows XP machine without
the sign and seal patch will fail and corrupt the password for the user.
Workaround
The password must then be reset by the administrator if this occurs.
• Problem
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. This can lead to a number of issues, including too many
files open by a process, too many locks, and performance degradation for the clients, since
they all 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 gets a separate SMBD process. For the Windows 2000 terminal services, Microsoft
provides a hotfix, Q818528. You can apply this hotfix and 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 hotfix, Q818528, on a system running the windows 2003. This
hotfix only applies to the Windows 2000.
For detailed information on the hotfix, see the Microsoft Q818528 article at: http://
support.microsoft.com/default.aspx?kbid=818528
• Problem
The error message "The file may have been changed" occurs when you save an
excel file to Samba. The error message also provides choices to either "save a copy" or
"overwrite changes".
8 Known problems and workarounds