             HP OpenVMS CIFS Version 1.2 
 Release Notes         : Copyright  2010 Hewlett-Packard Development Company, L.P.  5 Confidential computer software. Valid license from HP 8 required for possession, use or copying. Consistent with4 FAR 12.211 and 12.212, Commercial Computer Software,7 Computer Software Documentation, and Technical Data for : Commercial Items are licensed to the U.S. Government under5 vendor's standard commercial license. The information 9 contained herein is subject to change without notice. The : only warranties for HP products and services are set forth4 in the express warranty statements accompanying such9 products and services. Nothing herein should be construed 7 as constituting an additional warranty. HP shall not be 5 liable for technical or editorial errors or omissions  contained herein.   4 HP CIFS Server is derived from the Open Source Samba* product and is subject to the GPL license.  9 Intel and Itanium are trademarks or registered trademarks 6 of Intel Corporation or its subsidiaries in the United States and other countries.   7 Microsoft and Windows are U.S. registered trademarks of  Microsoft Corporation.  ; -----------------------------------------------------------    Table of Contents    1 About This Document        1.1 Intended Audience      1.2 Document Organization #     1.3 HP Encourages Your Comments    1 Introduction       1.1 Distribution Kit/     1.2 How to Build HP CIFS Sources on OpenVMS      1.3 General Information   
 2 Features  ;     2.1 New Features Provided by HP CIFS Server Version 1.2 7     2.2 Features Provided by HP CIFS Server Version 1.1          ECO17     2.3 Features Provided by HP CIFS Server Version 1.1    3 Problems Fixed 4 Known Problems
 5 Limitations    List of Tables   1-1 Mandatory Kits 1-2 Disk Space Requirements    About This Document    Table of Contents    1.1 Intended Audience  1.2 Document Organization  1.3 HP Encourages Your Comments   : This release notes describes the features, problems fixed,8 known problems, and limitations found in HP CIFS Server.   1.1 Intended Audience   ; This document is intended for OpenVMS system administrators : and network administrators. For more information about the5 HP CIFS Server, see the HP CIFS Server documentation:   ' http://h71000.www7.hp.com/doc/CIFS.html      1.2 Document Organization   % The document is organized as follows:   9 Chapter 1 Introduction Provides information about HP CIFS            Server software.  * Chapter 2 Features Describes the features.  6 Chapter 3 Problems Fixed Describes the problems fixed.  6 Chapter 4 Known Problems Describes the known problems.  0 Chapter 5 Limitations Describes the limitations.     1.3 HP Encourages Your Comments   3 HP encourages your comments and suggestions on this " document. Please send comments to:   mailto:openvmsdoc@hp.com   Chapter 1 Introduction   Table of Contents    1.1 Distribution Kit+ 1.2 How to Build HP CIFS Sources on OpenVMS  1.3 General Information    1.1 Distribution Kit  9 The HP CIFS Server software is supported on OpenVMS Alpha 8 and OpenVMS Integrity server systems. The following kits; are External Field Test versions of HP OpenVMS CIFS Version  1.2.  4   * For OpenVMS Alpha Versions 8.2, 8.3, and 8.4 is:  '     HP-AXPVMS-SAMBA-V0102--1.SFX_AXPEXE   :   * OpenVMS Integrity server Versions 8.2-1, 8.3, 8.3-1H1,     and 8.4 is:   '     HP-I64VMS-SAMBA-V0102--1.SFX_I64EXE    Mandatory Kits  8 The following kits must be installed prior to installing the HP CIFS Version 1.2 kit:   Table 1-1 Mandatory Kits  O +-----------------------------------------------------------------------------+ O |                                                    | OpenVMS |              | O | Kit Name                                           | Version | Architecture | O |----------------------------------------------------+---------+--------------| O | HP-I64VMS-VMS831H1I_ACRTL-V0400--4.PCSI$COMPRESSED | 8.3-1H1 | Integrity    | O |                                                    |         | servers      | O |----------------------------------------------------+---------+--------------| O | HP-I64VMS-VMS83I_ACRTL-V0800--4.PCSI$COMPRESSED    | 8.3     | Integrity    | O |                                                    |         | servers      | O |----------------------------------------------------+---------+--------------| O | HP-I64VMS-VMS821I_ACRTL-V0500--4.PCSI$COMPRESSED   | 8.2-1   | Integrity    | O |                                                    |         | servers      | O |----------------------------------------------------+---------+--------------| O | DEC-AXPVMS-VMS83A_ACRTL-V0600--4.PCSI$COMPRESSED   | 8.3     | Alpha        | O |----------------------------------------------------+---------+--------------| O | DEC-AXPVMS-VMS82A_ACRTL-V0600--4.PCSI$COMPRESSED   | 8.2     | Alpha        | O +-----------------------------------------------------------------------------+   6 You must also install Kerberos Version 3.0 and higher.    Note:7        HP OpenVMS CIFS Server does not support Kerberos :        authentication on OpenVMS Integrity servers Version:        8.2-1. Due to this reason, Kerberos Version 3.0 kit9        need not be installed on OpenVMS Integrity servers         Version 8.2-1.       Disk Space Requirement  : Table 1-1 lists the disk space required for installing the	 software.   ! Table 1-2 Disk Space Requirements   ; +---------------------------------------------------------+ ; |                                  | Disk Space           | ; |                                  | (approximate block   | ; | Operating System                 | size)                | ; |----------------------------------+----------------------| ; | OpenVMS Alpha V8.2, V8.3, and    | 94558                | ; | V8.4                             |                      | ; |----------------------------------+----------------------| ; | OpenVMS Integrity servers        | 108960               | ; | V8.2-1, V8.3, V8.3-1H1, and V8.4 |                      | ; +---------------------------------------------------------+   + 1.2 How to Build HP CIFS Sources on OpenVMS   7 Following are the steps to build the HP CIFS sources on  OpenVMS:  ;  1. Extract the sources provided with the HP CIFS PCSI file 3     from SAMBA$SRC.BCK to a directory on your disk.   6     To extract the source files after the installation+     completes, enter the following command:   7     $ PRODUCT EXTRACT FILE SAMBA /SELECT=SAMBA$SRC.BCK/      SOURCE=[TEST1]  9     The PCSI utility extracts the SAMBA$SRC.BCK file from :     the kit to the [TEST1] directory, which is the default     directory.  
      Note:5            The HP CIFS source can be extracted during :            installation by using the steps provided in the9            sample installation log. For more information, 0            see Appendix A in the HP OpenVMS CIFS!            Administrator's Guide.   :  2. Install the latest HP C compiler to build source files7     and the minimum version requirement for the same is      Version 7.1.  :  3. Install HP Module Management System (MMS) for OpenVMS.6     MMS software for OpenVMS is available from OpenVMS     DECSET software package.  *  4. Execute BUILD.COM in source directory.  1       * If BUILD.COM is executed with the RELEASE 8         parameter, all the executables are placed in the         [.BIN.REL] directory.   :       * If BUILD.COM is executed with the DEBUG parameter,8         all the executables are placed in the [.BIN.DBG]         directory.   1.3 General Information   : This section describes the information specific to HP CIFS Server.   8   * Before installing HP CIFS Server Version 1.2, ensure9     that you are not running HP CIFS Server version prior 8     to Version 1.0. If a version prior to HP CIFS Server8     Version 1.0 exists on the system, you must remove it"     and then verify the following:  7      1. Remove all the files under SAMBA_ROOT:[000000].   2      2. Logical names starting with SAMBA* must be         deassigned.   ;      3. After installing HP CIFS Server Version 1.2, if you 9         are copying existing SMB.CONF file to SAMBA$ROOT: 3         [LIB], you must change the following lines:   &           o SAMBA_ROOT with SAMBA$ROOT  ;           o guest account = SAMBA__GUEST with guest account              = SAMBA$GUEST   7   * Users must install the latest C RTL ECO kits before :     installing the HP CIFS Server software. Please contact7     HP customer support centers to get the latest C RTL      kit.  7   * Uninstalling the HP CIFS Server software displays a 8     prompt whether to retain the SMB.CONF and TDB files.3     Selecting the "No" option removes all the files &     including the configuration files.  ;   * The default SYSUAF account template, SAMBA$TMPLT can be 8     used to create new OpenVMS user accounts for HP CIFS     Server.   8     For more information about how to create new OpenVMS:     user accounts, see the HP OpenVMS CIFS Administrator's
     Guide.  :   * While adding new users to OpenVMS, ensure that the UIC5     is unique and use /ADD_IDENTIFIER qualifier while 8     creating the user. After the user is created, ensure8     that the user identifier matches with the user name,$     and the DISUSER flag is not set.  ;   * The installation of HP CIFS Server creates five OpenVMS 2     user accounts, namely, SAMBA$SMBD, SAMBA$NMBD,;     SAMBA$GUEST, SAMBA$TMPLT, and CIFSADMIN. These accounts :     are internal to HP CIFS Server. You are advised not to2     modify or change any attributes of SAMBA$SMBD,)     SAMBA$NMBD, and SAMBA$GUEST accounts.   b   * Executing SAMBA$SHUTDOWN.COM terminates all client                                            :     sessions or processes in addition to stopping the NMBD3     process and must be run during system shutdown.   ;   * HP CIFS Server honors only the default privileges of an      OpenVMS user account.   8   * Migration utility will be provided as a separate kit:     from HP CIFS Server Version 1.1 onwards. The migration4     utility can be downloaded from the following web     address:  9     http://h71000.www7.hp.com/network/CIFS_for_Samba.html    Chapter 2 Features   Table of Contents   7 2.1 New Features Provided by HP CIFS Server Version 1.2 8 2.2 Features Provided by HP CIFS Server Version 1.1 ECO13 2.3 Features Provided by HP CIFS Server Version 1.1   : This chapter describes the features of HP CIFS Server. The; following are some of the main features supported by the HP  CIFS Server:  7   * HP CIFS Server can be configured as a member in any '     domain (NT4-style and ADS domains).   6   * HP CIFS Server can be configured as a member in an7     NT-style Primary Domain Controller (PDC) and Backup      Domain Controller (BDC).  ,   * Provides complete browser functionality.  9   * Supports HP CIFS Server as a Member Server in OpenVMS      Cluster.  :   * Provides file security based on OpenVMS File Security.  $   * Supports ODS-5 and ODS-2 volume.   "   * Supports OpenVMS file formats.  0   * Supports ASCII, ISO-8859-1, UTF-8, and VTF-7     character-set.  9   * Supports shares present on NFS and DFS-mounted disks.   3   * Supports session security, NTLMSSP, and 128-bit      encryption.   !   * Supports new printer drivers.   7 2.1 New Features Provided by HP CIFS Server Version 1.2   6   * Improved installation and automated HP CIFS Server      configuration and management  1   * HP CIFS Server as member in Windows ADS Realm      * File security improvements:   2       o Simplify the use of mask and mode SMB.CONF         parameters  7       o Support for DELETE protection bit with mask and           mode SMB.CONF parameters  9       o Ability to set DELETE protection bit from Windows 1         for OWNER/GROUP/WORLD RMS protection mask   3       o Retain VMS ACE order while setting security   ;       o Map default_protection ace to create owner/group on          windows      * Performance enhancements:   9       o Storing file size in an ACE for non-stream format 
         files   8       o Utility to automatically update file length hint6         values for Sequential VAR and VFC format files  :       o Creation of TDB files using the optimized FDL file         o Open file caching      * ODS2 volume support:  5       o Directory enumeration performance improvement   5       o Handle extended ASCII characters in filenames   +       o Allow 79 character length filenames   8   * Support for fixed and undefined format file creation  9   * Support for share security migration from ASV to CIFS   3   * New CIFS utilities and improvements to existing 
     utilities   (   * Support for different idmap backends  8 2.2 Features Provided by HP CIFS Server Version 1.1 ECO1  3 The section lists the new features provided in this  release:     * Supports CONTROL flag.  5      a. When security is set on a file from a Windows 7         system, the Full Permission have been mapped to 8         READ+WRITE+EXECUTE+DELETE+CONTROL permission for'         that ACE on the OpenVMS system.   8      b. Windows "Take Ownership" and "Change permission"6         have been mapped to CONTROL on OpenVMS system.  8      c. The normal user who has "Full Permission", "Take:         Ownership" or "Change Permission" on a file/folder;         can now grant permissions to other users/groups for $         that particular file/folder.  6   * Allows administrators to modify owner of the file/8     folder by changing the ownership to either a Windows.     domain-user/-group or HP CIFS-user/-group.  8   * Supports the reading of sequential files with record6     formats of Fixed Length, Undefined, and files with     Indexed file organization.  8   * Allows HP CIFS Server to create files in a Stream_LF4     record format using the new SMB.CONF share level5     parameter vms rms format (rather than the default      Stream record format).  
      Note:8            Previously, this feature was controlled using4            the vfs objects parameter with a value of            streamlf.  9     By default, the value for vms rms format parameter is      stream.   ;     To create files with a Stream_LF record format, specify ;     the following in the share section of the SMB.CONF file      for the applicable share:        vms rms format = streamlf   
      Note:7            The parameter vfs objects = varvfc has to be ;            added either for each share definition or in the 1            [global] section of the SMB.CONF file.   5   * Creates SMBD process dumps in a single directory.   j     HP CIFS Server Version 1.2 for OpenVMS provides a                                                     /     logical SAMBA$PROCDMP, which can be defined 9     system-wide. In case there is an abnormal termination 9     of the SMBD process, the SMBD process dump is created -     in the directory pointed by this logical.   3   * SMBSTATUS displays node specific HP CIFS Server 9     information by using the option --nodename=<nodename>   :   * Supports migration from Advanced Server PDC to HP CIFS     Server PDC.      * Supports Windows 2008.  4     To support this feature, set the global SMB.CONF0     parameter require strongkey to yes as shown:       [global]       require strongkey = yes   3 2.3 Features Provided by HP CIFS Server Version 1.1   9 The section lists the features provided by HP CIFS Server  Version 1.1:  .   * The code is based on Samba Version 3.0.28a  3   * Improved performance of HP CIFS Server software   5   * Improved compatibility with Windows Vista clients      * Supports port 445   ,   * Supports Primary Domain Controller (PDC)  ,   * NTLMv2 support for Windows Vista clients     * VFC file support     * Improved TDB handling    :     To improve the TBD performance, hashing algorithm used7     for generating the TDB keys has been changed. Thus, 6     after installing HP CIFS Server Version 1.1 on the4     existing HP CIFS Server Version 1.0 kit, HP CIFS9     Version 1.0 TDB files needs to be migrated to Version 9     1.1 TDB files. During installation of HP CIFS Version ;     1.1, a TDB migration utility will automatically migrate :     HP CIFS Server Version 1.0 TDB files to HP CIFS Server     Version 1.1 TDB files.  6   * Inheritance of ACLs set on parent objects to child     objects   9   * "OPTIONS=DEFAULT" and "DEFAULT_PROTECTION" support in      ACEs   Chapter 3 Problems Fixed  4 This chapter describes the problems fixed in HP CIFS Server.     Note:8        The problems fixed in HP OpenVMS CIFS Version 1.27        will be included in the final release notes that 8        will be shipped with the SSB version of the same.  4 Problem Handling StreamLF and Record Formatted Files  7 HP CIFS Server does not support StreamLF and VARVFC VFS 7 object specification (vfs objects=varvfc streamLF) in a  share.  * Unable to Access Home Share on ODS-2 Disks  7 OpenVMS users who have a login directory pointing to an ; ODS-2 disk are not able to access the home share present on  the ODS-2 disk.   7 HP CIFS Server does not Honour Permissions for Built-in - Group Users or Resource Identifier cifs$users   3 When a user accesses an HP CIFS share that has full 6 permission granted for the built-in group Users or the; resource identifier cifs$users associated with it, the user  is unable to access the share.  1 Unable to Rename/Delete File if Host Owner has no 
 Permission  8 If two VMS users belonging to the same UIC group and the/ group has no permission to delete a folder, one ; corresponding domain user cannot delete or rename the files 3 created by the other user. This happens despite the 6 resource identifier granted to these accounts has full permissions to do so.   9 Unable to Access Files if User is Mapped by username. map  File  3 If a domain user is host mapped to a VMS user using 9 username.map file, the permissions granted to a share for ; the domain group to which the user belongs is not honoured.   9 Unable to Set Share Permissions Using Computer Management   8 With HP CIFS Server Version 1.1, an administrator cannot7 set share permissions using Computer Management utility  present on Windows.   7 SMBD Process Crashes During File Creation/Modification/  Deletion in a Share   8 SMBD crashes if change notify = no is not present in the7 SMB.CONF file and/or also if the share path name in the 7 SMB.CONF file is a logical name instead of the full VMS 	 pathname.   3 HP CIFS Server Ignores "vms path names" Set to "no"   ; Share path names in UNIX path format existing on ODS-5 disk : get converted to VMS path format, even if vms path names = no is specified for the share.  ' SMBD Process Crashes at Multiple Places   5 SMBD process crashes at multiple places due to memory  corruption.   5 TDB Migration Utility Crashes While Migrating HP CIFS  Version 1.0 TDBs  : During installation of HP CIFS Server Version 1.1 kit, TDB9 migration utility crashes while migrating HP CIFS Version 3 1.0 format TDBs to HP CIFS Version 1.1 format TDBs.   6 Unable to Print a Document if Data Exceeds Buffer Size  8 After the spool file is created during a print operation3 and if the data exceeds the user's buffer size, the  document is not printed.  8 NET RPC GROUP MEMBERS Crashes While Listing Global Group Members   6 When $ NET RPC GROUP MEMBERS is executed, sometimes it results in a NET utility crash.   7 User Permissions Disappear While Setting Permissions on  Files   4 In some cases, while setting permissions on files or8 folders from Windows the existing user permissions might
 disappear.  0 Too Many Audit Log Messages for Process Creation  9 For each SMBD process creation, audit messages are logged , leading to the accumulation of log messages.  4 SMBD Process Loops During Directory Enumeration from Windows   : With HP CIFS Server Version 1.1, SMBD process loops during7 directory enumeration from Windows if the share section + contains the following SMB.CONF parameters:    [sharename]    vms path names = no    vfs objects = vtf   7 Audit/Alarm Messages Generated While Trying to Access a  File  8 When a non-privileged user who is not an OWNER of a file8 tries to access the file having READ, WRITE, DELETE, and7 EXECUTE protection for WORLD, the following audit/alarm  message gets logged:  3 "%SYSTEM-F-NOPRIV, insufficient privilege or object  protection violation"   4 NET RPC VAMPIRE Utility Crashes While Migrating User Accounts  8 When NET RPC VAMPIRE utility is executed to migrate user6 accounts, it crashes with the following error message:  3 %SYSTEM-F-ACCVIO, access violation, reason mask=04, : virtual address=00000000000002EE, PC=00000000005C30A0, PS= 0000001B %TRACE-F-TRACEBACK  5 SMBD Process Crashes When Servicing Two User Sessions   : From a Windows client that is a member of the HP CIFS PDC,8 if two different user sessions are established to the HP8 CIFS Server, it leads to the abnormal termination of the    0 SMBD process that serves these session requests.  : SMBD Process Crashes if the SYSUAF File has READ Access to WORLD   7 When READ permission is granted to WORLD for the System 9 Authorization file instead of the default protection, and : when a normal user tries to connect to the HP CIFS server,9 the SMBD process created for this user session abnormally  terminates.   6 Unable to Print to HP CIFS Server from a Normal Domain Account   8 Unable to print to an HP CIFS Server when the session to7 the HP CIFS Server is established using a normal domain 7 user account and this account is mapped to the VMS host 8 account with minimum privileges using username map file.  + Accumulation of browse.dat Files in Cluster   : When the HP CIFS Server is configured on multiple nodes in9 a cluster that uses common samba$root disk, all the nodes 9 running the HP CIFS Server uses the same browse.dat file. : This leads to an accumulation of browse.dat files as there8 is no synchronization in writing to the browse.dat file.   Chapter 4 Known Problems  4 This chapter describes the known problems in HP CIFS Server.    NET RPC VAMPIRE Utility Fails    Problem:  7 $NET RPC VAMPIRE "-S" <AS-NODE-NAME> "-U<adminusername> : %password" command fails with the following error message:   Fetching DOMAIN database  ( Receiving SMB: Server stopped responding  9 rpc_api_pipe: Remote machine<AS-NODE-NAME> pipe \NETLOGON   fnum 0x4returned critical error.  6 Error was Call timed out: server did not respond after 10000 milliseconds  5 Failed to fetch domain database: NT_STATUS_IO_TIMEOUT   ! This occurs due to timing issues.    Workaround:   9 Execute the command with the debug log level 10 as shown:   7 $NET RPC VAMPIRE "-S" <AS-NODE-NAME> "-U<adminusername>  %password" -d10   ( NET RPC VAMPIRE Utility Response Delayed   Problem:  7 $NET RPC VAMPIRE "-S" <AS-NODE-NAME> "-U<adminusername> ( %password" takes a long time to respond.  9 This command tries to communicate through port 445, which  takes a long time to respond.    Workaround:   6 The solution is to hard code the port number to 139 as shown:  7 $NET RPC VAMPIRE "-S" <AS-NODE-NAME> "-U<adminusername>  %password" --port 139   4 NET RPC JOIN or NET RPC TESTJOIN Fails with an Error Message    Problem:  6 While configuring HP CIFS Server as member server to a9 domain with Advanced Server for OpenVMS (ASV) as PDC in a 3 cluster environment, the following error message is 
 displayed:  3 Error in domain join verification (credential setup  failed):   NT_STATUS_INVALID_COMPUTER_NAME    Workaround:   : If the cluster alias name exists for ASV, you must specify9 the ASV cluster alias name when attempting to communicate 6 with the ASV. This can be done using "-S" or "-server"; option on the NET commands and in HP CIFS Server utilities.   0 Protections and ACLs are not Displayed Correctly   Problem:  ; Protections and ACLs are not displayed correctly on Windows 6 by right-clicking and selecting Properties -> Security option.    Workaround:   : In order to avoid this problem, click on "Advanced" tab on; the Properties dialog box to view the correct values set on 4 a particular file or directory. HP will address this/ problem in a future release of HP CIFS Server .    SMBPASSWD Utility Crash    Problem:  7 Unprivileged users attempting to change the password by / using the SMBPASSWD utility results in a crash.    Workaround:   5 An administrator can log in to OpenVMS system using a ; privileged account and use SMBPASSWD utility to modify user 
 passwords.  4 On a Windows client, user can change the password by6 pressing Ctrl+Alt+Delete and then clicking the "change password" button.   0 "The Network Name cannot be Found" Error Message  4 "The network name cannot be found" is a common error* message and is due to one of the following misconfigurations:  1   * User trying to access the share does not have ;     sufficient permissions. To access the share, user needs )     to be granted the Read (r) permission   4   * User specified a share name that does not exist.  7 File Size Allocated on the Disk is more than the Actual 	 File Size    Problem:  9 When an attempt is made to save a text file using Notepad 6 application, the following error message is displayed:  / "file already exists, do you want to overwrite"   ; When you overwrite the file, it occupies 10000 blocks (5MB) 1 even though the size of the file is just 1 block.    Workaround:   : Edit SAMBA$SMBD_STARTUP.COM file and change the value for  /EXTEND_QUANTITY as shown:  , $ SEARCH [BIN]SAMBA$SMBD_STARTUP.COM;1 10000  $ $ SET RMS_DEFAULT /EXTEND_QUANTITY=1   $!   HP CIFS Utilities Crash    Problem:  9 Executing HP CIFS Server utilities such as PDBEDIT from a 6 user account that does not match the Rights Identifier results in a crash.    Workaround:   9 There is no workaround. HP will address this problem in a ! future release of HP CIFS Server.    NET RPC JOIN Command Fails   Problem:  ; When using the "-I" option with the $ NET RPC JOIN command, * it fails with the following error message:  0 $ NET RPC JOIN "-UADMINISTRATOR%IONETADM$1" "-I" 16.113.6.131  1 [2007/10/11 17:35:28, 0] SAMBA$SRC:[SOURCE.UTILS]  NET_RPC_JOIN.C;1:(349)  3 Error in domain join verification (credential setup  failed):   NT_STATUS_INVALID_COMPUTER_NAME     Unable to join domain IONETW2K3.     Workaround:   9 There is no workaround. HP will address this problem in a ! future release of HP CIFS Server.   6 Problem with User Mappings Stored in username.map File   Problem:  9 User mappings stored in the username map file do not work 6 if the file format is other than Stream record format.   Workaround:   7 In order to avoid this problem, ensure that you use the 6 username.map file located in the directory SAMBA$ROOT:4 [LIB]. If you create a user name map file on OpenVMS3 system, convert the file to Stream record format by   executing the following command:  ; $ SET FILE/ATTRIBUTE=(RFM:STM,MRS:0,LRL:0) SAMBA$ROOT:[LIB]  <USERNAME MAP FILENAME>   $ Problem with VFS Sharable on a Share   Problem:  8 On ODS-2 disk, if you specify "VARVFC" VFS sharable on a8 share, server becomes slow and sometimes operation fails due to large number of files.    Workaround:   9 There is no workaround. HP will address this problem in a ! future release of HP CIFS Server.   8 Unable to Open MS-Office Documents from the Other Client   Problem:  ; On OpenVMS Alpha V8.2 and OpenVMS Integrity servers V8.2-1, 5 you may fail to open the MS-Office documents from the  second client.   Workaround:   6 This is a limitation on OpenVMS Alpha V8.2 and OpenVMS; Integrity servers V8.2-1 due to the non-availability of the 9 byte range locking API. HP will address this problem in a ! future release of HP CIFS Server.    "net time" Utility Crash   Problem:  7 On OpenVMS Alpha, "net time" utility crashes with "-d2"  option.    Workaround:   9 There is no workaround. HP will address this problem in a ! future release of HP CIFS Server.   6 Telnetsymbion Print Queues Prints Arbitrary Characters   Problem:  : If HP CIFS Server is configured with Telnetsymbion printer: queue and tries to print a text file using the Notepad, an arbitrary character is printed.    Workaround:   6 Use the DCPS or LPD OpenVMS print queue which provides7 libraries by default. HP will address this problem in a ! future release of HP CIFS Server.   ) Setting Client Capacity with SAMBA$CONFIG      Problem:  : The client capacity is to set to double the number that is4 specified. Since HP CIFS Server Version 1.1 provides; support for connection on TCP port 445 (SMB over TCP/IP) in 7 addition to TCP port 139 (SMB over NetBIOS TCP/IP), the : "client capacity" set by SAMBA$CONFIG.COM is really double! what the administrator specifies.   6 For example, if the admin specifies a value of 50, the6 SMBD445 service has a limit of 50 and so does the SMBD service.   Workaround:   : You can divide the client capacity numbers between the 1397 and 445 ports. HP will address this problem in a future  release of HP CIFS Server.  9 Issues while Adding Advanced Server for OpenVMS as Member  Server   Problem:  ; While adding Advanced Server for OpenVMS as a member server : to HP CIFS PDC, there are issues while establishing secure0 channel with HP CIFS PDC, admin logon and so on.   Workaround:   6 There is no workaround and this is a limitation due to Advanced Server.  / Using Groups in Username Map File does not work    Problem:  ; The functionality of using a group name in the username.map  file does not work.    Workaround:   9 There is no workaround. HP will address this problem in a ! future release of HP CIFS Server.   % Issues with NET RPC TRUSTDOM Commands    Problem:  8 If you are trying to add a trust without a corresponding; OpenVMS account (with the name <domain>$) fails without any 4 error message. The command completes as though it is& successful but actually it has failed.  4 If you are trying to list the trusted domain entries4 containing the word "none" even when there are valid entries in the list.   Workaround:   9 There is no workaround. HP will address this problem in a ! future release of HP CIFS Server.   ; NMBD Process Starts Looping when Configured for WINS Server    Problem:  : When HP CIFS Server is configured for WINS server with the' following setting in the SMB.CONF file:    [global]   wins support = yes   dns proxy =yes  # NMBD process becomes compute bound.    Workaround:   8 Currently, HP CIFS does not support dns proxy parameter.8 So, set the dns proxy = no in the SMB.CONF file. HP will; address this problem in a future release of HP CIFS Server.   " Problems with Share Level Security   Problem:  7 Share level security does not allow any users to login.    Workaround:   3 You must have SAMBA$GUEST account in the passdb.tdb : database. HP will address this problem in a future release of HP CIFS Server.  ( NET RPC FILE CLOSE Command does not work   Problem:  7 When the user tries to close an open file using NET RPC 7 CLOSE FILE <fileID> command, it fails without any error  message.   Workaround:   9 There is no workaround. HP will address this problem in a ! future release of HP CIFS Server.   4 Cannot Login to Windows Vista with Microsoft Signing Enabled    Problem:  9 Currently, with SMB signing enabled on client ("Microsoft ; network client: Digitally sign communication (always)") and 5 server, Windows client can be added successfully as a 7 workstation to the domain. But after joining the domain 4 successfully, Windows cannot login using the HP CIFS5 account and the following error message is displayed:   8 "The trust relationship between this workstation and the" primary domain controller failed."  . With "Microsoft network client: Digitally sign: communication (if server agrees)" enabled both joining and login works fine.    Workaround:   9 There is no workaround. HP will address this problem in a ! future release of HP CIFS Server.    Chapter 5 Limitations   9 This chapter describes the limitations in HP CIFS Server. 8 The limitations that are applicable to HP CIFS Server on8 OpenVMS Integrity servers are also applicable to HP CIFS Server on OpenVMS Alpha.  9   * Advanced Server for OpenVMS cannot be configured as a 5     Member Server to the HP CIFS PDC due to technical      limitations.  8   * With HP CIFS Server, it is not possible to access or7     create a directory containing "." (dot) in its name 3     when the directory is located on an ODS-2 disk.   6   * On OpenVMS Alpha Version 8.2 and OpenVMS Integrity6     servers Version 8.2-1, there is severe performance5     degradation as FCNTL API lacks the SETLKI feature $     required for byte range locking.  ,   * HP CIFS Server does not support external     authentication.   8   * The SMB.CONF printing parameter is hard-coded to the*     value "OpenVMS" and cannot be changed.  9   * The SMB.CONF load printers parameter is hard-coded to )     the value "NO" and cannot be changed.   5   * Printcap file is not supported on HP CIFS Server.   8   * If the file share are present on ODS-2 disk, HP CIFS6     Server does not support Unicode characters in file
     names.  :   * HP CIFS Server does not support Windows Administrative     tools such as User Manager.   4   * HP CIFS Server does not support SMB File Systems     (SMBFS).  7   * The Windows 200x or Windows XP Microsoft Management :     Console (MMC) cannot be used to manage HP CIFS Server.  1   * While using the VTF modules you cannot create 5     directories with non-ASCII characters on Windows.   6   * HP CIFS Server does not support SMBPASSWD backend.  ;   * HP CIFS Server does not support "smbcquotas" utility as 3     the quotas are not supported by the VMS server.   6   * On HP CIFS Server, there is a limit on the maximum;     number of users that can be created automatically. This 6     restriction is due to the SYSUAF database group on9     OpenVMS as the UIC value cannot be greater than 37776 :     (Octal) which equals to 16382 (decimal). If the number:     of automatically created users exceeds the limit, then9     HP CIFS Server fails with the following error message ;     in the log file if the log level is set to greater than      5.  
     334598850   3     Which translates to %UAF-E-UICERR, error in UIC      specification.  ;   * If HP CIFS Server is configured as PDC, the name of the 9     workstations that are getting added to HP CIFS Server 9     PDC must not exceed 11 characters. This limitation is 5     due to the OpenVMS user name length limited to 12 "     characters in SYSUAF database.  :   * SMBSTATUS utility does not display session information8     for anonymous sessions. This is by design as storing5     anonymous session information in sessionid.tdb is      expensive.  3                                                     