HP CIFS Server 3.0f Release Notes version A.02.03 for HP-UX 11i v3 (December 2006)

Problem

The HP CIFS Server creates a smbnull user for guest access, which does not have or require a home directory.

However the password/group file checker tool, pwck, on HP-UX always assumes that each entry in the

/etc/passwd file should have its own login directory. If there is no entry, the pwck command will complain

about it and give the following checking result:

smbnull:*:101:101:DO NOT USE OR DELETE - needed by Samba:/home/smbnull:/sbin/sh

For the same reason, the pwck command also complains for machine trust accounts in the HP CIFS Server.

Workaround

No workaround exits.

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 degredation 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".

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

Problem 11