HP CIFS Server Release Notes version A.03.01.
© Copyright 2012, 2014 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 HP secure development lifecycle......................................................................4 1 HP CIFS server version A.03.01.06 release notes............................................5 Announcement.........................................................................................................................5 What's new in HP CIFS server A.03.01.06...................................................................................5 Product revision number.......................
HP secure development lifecycle Starting with HP-UX 11i v3 March 2013 update release, HP secure development lifecycle provides the ability to authenticate HP-UX software. Software delivered through this release has been digitally signed using HP's private key. You can now verify the authenticity of the software before installing the products, delivered through this release. To verify the software signatures in signed depot, the following products must be installed on your system: • B.11.31.
1 HP CIFS server version A.03.01.06 release notes Announcement This document describes HP CIFS server A.03.01.06 changes, defect fixes, and other information. HP CIFS server A.03.01.06 is supported on HP-UX 11i v3. What's new in HP CIFS server A.03.01.06 HP CIFS server A.03.01.06 is a defect fix release based on Samba 3.4.3. For more information on defects fixed in this release, see “Defect fixes in HP CIFS server” (page 7). The known issue “Address space model for the latest HP CIFS binaries, version A.
HP-UX memory and disk requirements The minimum requirements of 64-bit 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 v3 64-bit – 1 GB RAM for each CPU – 2 to 8.5 GB of disk space. Kerberos product requirements Kerberos v5 Client version E 1.6.2 or later is required to support HP CIFS server integration with Windows 2003 or later ADS Domain Controller (DC) on HP-UX 11i v3 systems.
Parameter Name Description Default preferred master Changed default No idmap backend Changed default tdb idmap cache time Changed default 604800 ldap ssl Modified start tls 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 server version A.03.01.
Table 3 Defects fixed in HP CIFS server version A.03.01.04 (continued) Identifier Description Resolution auth/auth_util.c:create_builtin_users(810) create_builtin_users: Failed to create Users [2011/11/24 18:19:41, 2] auth/auth_util.c:create_local_nt_token(993) create_local_nt_token: Failed to create BUILTIN\Users group! Table 4 Defects fixed in HP CIFS server version A.03.01.03 Identifier Description Resolution QXCR1001105154 When a samba_setup script is This issue is fixed in this release.
Table 4 Defects fixed in HP CIFS server version A.03.01.03 (continued) Identifier Description Resolution the DNS lookup incorrectly takes the autofs map file as a hostname. QXCR1001158887 Significant parameters are missing from the CIFS server A.03.01.xx smb.conf manpage. This issue is fixed in this release. QXCR1001157707 In the CIFS server Administrator This issue is fixed in this release. Guide, thesmb.conf examples are not listed correctly. The CIFS Server Administrator Guide versions A.02.04.
[ ] Reinstall filesets even if same revision exists [ ] Reinstall files even if same one already there [ ] Allow installation of lower version than current 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 If the libnss_wins NSS library is used, then the sh_load() error message is returned. Workaround The libnss_wins NSS library is not tested. Therefore, it must not be used.
files open by a process, too many locks, and performance degradation for the clients, since the clients share a single SMBD process. Workaround For the Windows NT, you can set a registry parameter, MultipleUsersOnConnection , to 1, which forces each terminal server client to negotiate its own connection, so that each client receives a separate SMBD process. For the Windows 2000 terminal services, Microsoft provides a hotfix, Q818528.
4. 5. Select Network security: LAN Manager authentication level. Set the authentication level to Send LM & NTLM response or Send LM & NTLM — use NTLMv2 session security if negotiated. Issue When using the smbpasswd command during the first time you add a Samba user to a new CIFS Server installation, the command might respond with a misleading message as in the following example: .
Workaround When required to accommodate the intra/inter-forest trusts that HP CIFS member servers might be exposed to in a forest, shortcut trusts can be explicitly created. HP CIFS PDCs support external trusts, which can be sufficient for Samba and Windows inter-domain trust relationships. For more information about Windows 2000/2003 trusts, see the MS TechNet documentation at http:// technet.microsoft.com.
2 Related documentation To obtain the documents, see the following sources and then select HP-UX Common Internet File System (CIFS) client/server Software: • HP CIFS Server Administrators Guide is available at: www.hp.com/go/hpux-networking-docs • Release Notes for this version and for previous versions of HP CIFS server are available at: www.hp.
3 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
