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.01 Release Notes..........................................4 Announcement.........................................................................................................................4 Changes in HP CIFS server A.03.01.01 ..................................................................................4 Product revision number .......................................................................................................
1 HP CIFS Server Version A.03.01.01 Release Notes Announcement This document describes HP CIFS Server A.03.01.01 changes, defect fixes, and other information. HP CIFS Server A.03.01.01 is supported on HP-UX 11i v2 and HP-UX 11i v3. Changes in HP CIFS server A.03.01.01 • HP CIFS Server A.03.01.01 is a feature release based on Samba 3.4.3, with defect fixes and applicable security fixes. HP CIFS Server now 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 1GB 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 Fixes in HP CIFS server A.03.01.
default_tkt_enctypes = RC4-HMAC DES-CBC-CRC DES-CBC-MD5 preferred_enctypes = RC4-HMAC DES-CBC-CRC DES-CBC-MD5 NOTE: Ensure that the default_realm parameter matches with realm that you want to join. Issue The wbinfo command fails sometimes when a large number of users or groups (~32k users or groups) are in a trusted domain. Workaround No known workaround exists. Issue The wbinfo command hangs when the trusted domain is unavailable. Workaround No known workaround exists.
Workaround The administrator must reset the password. Issue When you use terminal server clients to access to shares on a CIFS server, all of the clients from that terminal server connect over a single virtual connection and are serviced by a single SMBD process on the CIFS Server. These actions might lead to a number of issues, including too many files open by a process, too many locks, and performance degradation for the clients, since the clients share a single SMBD process.
Issue No 64 bit Windows XP clients can connect to the CIFS Server when configured with smb.conf parameter security=server. Other Windows clients, including the 64-bit version of Windows XP clients by default , might also fail to connect if they have the local policy for LAN Manager set to Send NTLM response only. Workaround Using the Administrative Tool on each failing client: 1. 2. 3. 4. 5. Select Local Security Policy. Select Local Policies. Select Security Options.
Issue The 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 the following error message: This program cannot open the required dialog box because the specified computer cannot be determined to belong to a domain. Try again. Workaround No workaround exists.
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. When set to 0, change notification messages are not sent and long delays do not occur. Clients must initiate updates to view changes (by pressing F5) that might have occurred on the file share. Beginning with A.02.03.01, the change notify timeout parameter moves from a global to share level parameter.
