HP CIFS Server Release Notes Version A.03.01.
© Copyright 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 HP CIFS Server Version A.03.01.03 Release Notes..........................................4 Announcement.........................................................................................................................4 Changes in HP CIFS Server A.03.01.03 .................................................................................4 Product revision number .......................................................................................................
1 HP CIFS Server Version A.03.01.03 Release Notes Announcement This document describes HP CIFS Server A.03.01.03 changes, defect fixes, and other information. HP CIFS Server A.03.01.03 is supported on HP-UX 11i v2 and HP-UX 11i v3. Changes in HP CIFS Server A.03.01.03 • HP CIFS Server A.03.01.03 is a defect release based on Samba 3.4.3. HP CIFS Server supports Windows Server 2008 and 2008R2, Windows Vista, and Windows 7 operating systems.
HP-UX memory and disk requirements The minimum requirements of 64-bit HP-UX 11i v2 and HP-UX 11i v3 systems are 1 GB RAM and 2 GB disk space. HP recommends the following minimum memory and disk requirements to enable upgrade and maintenance: • HP-UX 11i v2, HP-UX 11i v3 64-bit – 1 GB RAM for each CPU – 2-8.5 GB disk Kerberos product requirements Kerberos v5 Client version D 1.6.
Parameter Name Description Default max open files Changed default 1024 max stat cache size Changed default 256 preferred master Changed default No ldap ssl Modified start tls idmap backend Changed default tdb idmap cache time Changed default 604800 allocation roundup size Modified 1048576 kernel oplocks Modified Yes use kerberos keytab Removed read bmpx Removed mangled map Removed kernel share modes Removed Defect fixes in HP CIFS Server Table 1 Defects fixed in HP CIFS Se
Table 1 Defects fixed in HP CIFS Server version A.03.01.03 (continued) Identifier Description Resolution • vfs_full_audit.8 • vfs_netatalk.8 • vfs_shadow_copy.8 • vfs_shadow_copy2.8 • winbind_krb5_locator.7 NOTE: In addition to the auditing manpages, other functionality manpages that are not supported by HP CIFS Server are also removed. QXCR1001115123 If a CIFS share is used as a This issue is fixed in this release.
| been installed. | Either remove this fileset or change the "allow_downdate" | option to "true". | * Reading source for file information. | * Executing preDSA command. | NOTE: Could not install the bundle "B8725AA,r=A.03.01.01" because | none of its filesets could be installed.
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.
To avoid this error, change the registry as described in the Microsoft knowledge base article at http://support.microsoft.com/default.aspx?kbid=324491 The Samba community also addressed the issue and has further characterized it on the Bugzilla webpage at https://bugzilla.samba.org/show_bug.cgi?id=1094 Issue Because of increased Windows security requirements, profile storing might fail if adequate authority has not been configured for roaming profiles.
(bad lockout attempt), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 9 (disconnect time), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 10 (refuse machine password change), returning 0 Added user user1 The user is added correctly, and the misleading messages only appear with the first occurrence of adding a new Samba user. Workaround Verify that the user has been added correctly, and ignore the misleading messages.
Workaround Use the -m option with useradd when adding a POSIX machine account. If the home directory does not exist for the new account, it is created. Issue The delete operation on a large number of files from a directory takes a long time to complete. Workaround Close Windows Explorer after the delete process is started. Beginning with A.02.03.01, another workaround is to set the change notify timeout smb.conf parameter to 0.
