HP CIFS Server 3.0o Release Notes version A.02.04.
© Copyright 2010, 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 Announcement...........................................................................................4 Summary of changes in HP CIFS Server A.02.04.03.....................................................................4 Product Revision Number...........................................................................................................4 2 What's new in HP CIFS Server A.02.04.03....................................................5 3 Fixes in HP CIFS Server A.02.04.03..............
1 Announcement This document contains information about the changes and defect fixes provided in HP CIFS Server A.02.04.03 as well as other helpful information. HP CIFS Server A.02.04.03 is supported on HP-UX 11i v3. The following list provides a summary of the changes in this release. Summary of changes in HP CIFS Server A.02.04.03 • HP CIFS Server A.02.04.03 is a defect fix release based on Samba 3.0.30 with selected fixes from Samba 3.0.31 to Samba 3.0.37 versions. HP CIFS Server A.02.04.
2 What's new in HP CIFS Server A.02.04.03 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 and later 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. The Dynamic DNS update option is available in HP CIFS Server A.02.04.01 and later.
3 Fixes in HP CIFS Server A.02.04.03 HP CIFS Server A.02.04.03 provides the following defect fixes: 6 • CIFS-Server.CIFS-RUN improper checkinstall script in IC357QXCR 1001084055 • 1103 ic357 - CIFS-Server.CIFS-RUN fileset configure script fails on PA-RISC QXCR 1001083490 • CIFS Server:preinstall script calls is_upgrading() which fails if file matches QXCR 1000993982 Fixes in HP CIFS Server A.02.04.
4 Installation and patch requirements for HP CIFS Server A.02.04.03 Operating system requirements HP CIFS Server A.02.04.03 can be installed on the following operating systems: • HP-UX 11i v3 on HP 9000 systems • HP-UX 11i v3 on HP Integrity systems HP CIFS Server installation requirements The HP CIFS Server requires approximately 108 MB of disk space for installation on an HP-UX 11i v3 system. The HP CIFS Server source code files requires approximately 36 MB of disk space.
5 Known problems and workarounds The following is a list of known problems and, wherever possible, the appropriate workarounds for the HP CIFS Server A.02.04.03: • Problem The net rpc trustdom establish command fails while attempting to establish a trust relationship with a Windows 2008 domain, and the following error message is displayed: NetServerEnum2 error: Couldn't find primary domain controller for domain 2K8DOMAIN. Workaround There is no known workaround.
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. • 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 Because of increased Windows security requirements, profile storing may fail if adequate authority has not been configured for roaming profiles. Workaround Set profile acls = yes for the profile share used for the user profile files. Do not set profile acls = yes on normal shares as this will result in incorrect ownership of the files created on those shares. • Problem 64 bit Windows XP clients cannot connect to the CIFS Server when it is configured with smb.conf parameter "security=server".
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. Adding an ACE through Windows Explorer File->Properties->Security interface to a file or directory from a Windows XP Professional 64-bit edition results in an error that reads: This program cannot open the required dialog box because the specified computer cannot be determined to belong to a domain. Try again.
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. When set to zero, change notification messages will not be sent and the long delays will not occur. Clients will then need to initiate updates (pressing F5) to view changes that may have occurred on the file share. Beginning with A.02.03.
