HP CIFS Server Release Notes Version A.03.01.04 (5900-2294), April 2012

Issue
The wbinfo command fails sometimes when a large number of users or groups (~32k users or
groups) are in a trusted domain.
Workaround
No known workaround exists.
Issue
If the libnss_wins NSS library is used, then the sh_load() error message is returned.
Workaround
The libnss_wins NSS library is not tested. Therefore, it must not be used. The library will be
removed in the future versions of the product.
Issue
After the wins server option is set in the smb.conf file, it cannot be cleared using SWAT utility
Workaround
Manually edit the smb.conf file to remove the wins server entry.
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
Known issues and workarounds 9