Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP CIFS Server 2.2e Release Note: Version A.01.09.04 > Chapter 1 HP CIFS Server Release Note

Known Problems and Workarounds in the HP CIFS Server A.01.09.04

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The following is a list of known problems and, where possible, the appropriate workarounds for A.01.09.04:

Problem

Share mode security does not work with POSIX ACLs.

Workaround

Microsoft servers do not support share mode security and Windows NT ACLs. No workaround currently exists.

Problem

CIFS clients cannot delete open files. Related Bug: CIFS clients cannot delete hard links to open files while the file remains open.

Workaround

Delete files and hard links after files are closed.

Problem

The smbstatus utility and SWAT status screen do not display any information before a client connects to the CIFS Server.

Workaround

Connect to the CIFS Server before using the smbstatus utility and SWAT status screen.

Problem

Matching single characters in file names from the DOS prompt on a shared CIFS Server drive using wild card operations and multi-byte character sets does not always work (for example, using Japanese Shift-JIS and ???? matches two multi-byte characters instead of four multi-byte characters).

Workaround

Use ?? for each single character. For example, if you are trying to match 4 characters, you must use 8 wild cards, ????????.

Problem

A registry key is required when a Windows XP client needs to successfully join and logon to a Samba domain.

Workaround

Run the /opt/samba/docs/Registry/WinXp_SignOrSeal.reg script on the Windows XP client that is joining the Samba domain.

Problem

The nmbd log file does not go in the log file directory after setting log file, the smb.conf variable, to change debug log file destinations.

Workaround

For a workaround when starting the CIFS Server, specify where the nmbd log file goes by entering the following at the command line:

nmbd -l "/new/log/file/path/logfilename" -D

For a permanent workaround, edit /opt/samba/bin/startsmb.

  1. Change ${samba_path}/nmbd -D
    to
    $ {samba_path}/nmbd-l/new/log/file/path/logfile -D

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2003 Hewlett-Packard Development Company, L.P.