HP CIFS Server 3.0k Release Notes version A.02.
© Copyright 2009 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.
Table of Contents Announcement.......................................................................................................................................5 Summary of changes in HP CIFS Server A.02.04..............................................................................5 Product Revision Number ................................................................................................................5 What's new in HP CIFS Server A.02.04...............................................
Announcement This document contains information about some changes and defect fixes provided in HP CIFS Server A.02.04, as well as other helpful information. HP CIFS Server A.02.04 is supported on HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3. The following list is a summary of the changes in this release. Summary of changes in HP CIFS Server A.02.04 • • HP CIFS Server A.02.04 is based on Samba 3.0.30 with selected fixes from 3.0.31 to 3.0.34.
What's new in HP CIFS Server A.02.04 Starting with the HP CIFS Server A.02.04 release, HP CIFS Server supports Windows Server 2008 and Windows Vista operating systems. HP CIFS server A.02.04 can join as a member server in the Active Directory Services (ADS) security mode to a Windows 2008 domain. Also, Windows Vista clients can now access resources (shares) of the HP CIFS Server.
Fixes in HP CIFS Server A.02.04 HP CIFS Server A.02.04 includes the following defect fixes: • HP CIFS Server cannot join Windows Server 2008 domain in ADS security mode. QXCR1000837533 This problem is fixed. HP CIFS Server A.02.04 supports Windows Server 2008 operating system. • The net time set uses invalid date string for HP-UX /bin/date. QXCR1000839337 This problem is fixed. • Joining the net ADS creates machine account with USE_DES_KEY_ONLY flag set. QXCR1000851926 This problem is fixed.
Installation and Patch Requirements for HP CIFS Server A.02.04 Operating System Requirements HP CIFS Server A.02.04 can be installed on HP 9000 or HP Integrity systems running HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3. HP CIFS Server Installation Requirements The HP CIFS Server requires approximately 108 MB of disk space for installation on an HP-UX 11i v1 system, 210 MB of disk space for installation on an HP-UX 11i v2 system, and 215 MB of disk space for installation on an HP-UX 11i v3 system.
usershare allow guests usershare max shares usershare owner only usershare path usershare prefix allow list usershare prefix deny list usershare template share winbind offline logon winbind refresh tickets ldap ssl max stat cache size dos filemode enable asu support enable privileges host msdfs strict locking winbind enum users winbind enum groups winbind nested groups acl group control ldap port change notify timeout lock spin count enable rid algorithm hosts equiv winbind max idle children wins partners
Known Problems and Workarounds The following is a list of known problems and, where possible, the appropriate workarounds for the HP CIFS Server A.02.04: Problem The -c or -C options are removed from the wbinfo command. Workaround There is no known workaround.
Problem A non-root user running smbstatus may 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 disallows a normal user to initialize tdb files. A normal user must preform smbstatus after HP CIFS Server is started by root, or tdb files have been initialized.
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 Samba community also observed the problem and has further characterized it in the Bugzilla at https://bugzilla.samba.org/show_bug.cgi?id=1094 Problem Because of increased Windows security requirements, profile storing may fail if adequate authority has not been configured for roaming profiles.
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 will be added correctly and the misleading messages will only be displayed with the first occurrence of adding a new Samba user. Workaround Verify that the user has been added correctly and ignore the misleading messages. Problem 64 bit Windows XP clients are unable to add a new ACE.
Workaround Use the "-m" option with useradd when adding a POSIX machine account. The home directory will be created for the new account if it does not exist. Problem The delete operation on a large number of files from a directory takes a long time to complete. Workaround One workaround is to close the 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 zero.
