ECO NUMBER: ASUV51BECO001 ----------- PRODUCT: Advanced Server for UNIX -------- UPDATED PRODUCT: Advanced Server for UNIX Version 5.1B ---------------- RELEASE DATE: May, 2003 -------------- The Advanced Server for UNIX (ASU) Version 5.1B ECO #001 kit provides enhancements and corrections for problems found in the ASU Version 5.1B software and in earlier versions of the ASU software. This release note document has the following sections: - ASU General Problem Descriptions and Solutions - ASU TruCluster Server Version 5.x Problem Descriptions and Solutions - New ASU Registry Entries - ASU General Changes - ASU Installation Instructions ---------------------------------------------- ASU General Problem Descriptions and Solutions ---------------------------------------------- Problem Addressed: If a user encounters an ASU logon problem or if the User Manager or Server Manager fails and displays a message that it could not find the domain controller, follow these steps to correct the problem: 1. Enter the following command to display if there is a datagram flow controlled problem: # lmstat -n | grep flow There is a datagram flow controlled problem if the following message is displayed: total datagrams flow controlled nn datagrams flow controlled nn Follow these steps to correct a datagram flow controlled problem: a. Enter the following command to stop the ASU server: # net stop server b. Add the following line in the /usr/net/servers/lanman/lanman.ini file under the [ lmxserver ] section: ccmsgtodcname = no c. Enter the following command to start the ASU server: # net start server 2. If the ASU server has a trust relationship with a domain whose PDC is in a different TCP/IP subnet, then you must use one of the following name resolution methods: - If the ASU server uses WINS for name resolution, make sure that the ASU server and the PDC of the trusted domain are using the same WINS servers. Use the asusetup utility to check whether WINS name resolution is enabled (Use NBNS: yes), and to change the address of primary and secondary WINS servers if necessary. (Note: To avoid stopping the ASU server, you can directly examine the /usr/net/servers/lanman/transports.ini file, but do not manually edit this file.) - If the ASU server does not use WINS for name resolution, or if the ASU server and its trusted domain do not use the same WINS servers, then the /usr/net/servers/lanman/datafiles/lmhost file on the ASU server must have an entry for the PDC of the trusted domain. For example, if SERVER1 is the name of the PDC in the trusted domain called WORK.DOM with an IP address of 1.2.3.4, add the entry: 1.2.3.4 SERVER1 #DOM:WORK.DOM #PRE Problem Addressed: Using the promote command to promote an ASU BDC to PDC does not automatically demote the PDC. Follow these steps to use the promote command to promote an ASU BDC to PDC: 1. Demote the PDC to be the BDC and stop it 2. Promote the BDC to be the PDC 3. Restart the BDC Alternatively, you can use the promote feature in the Server Manager utility to avoid manually demoting the PDC. Problem Addressed: When the UseUnixGroups registry entry was set, users could not save Windows XP roaming profiles on the ASU server. This problem has been corrected. Problem Addressed: DOS attributes were not properly retained on a file if the file was copied or saved from Microsoft Windows clients into a share on the ASU server. This problem has been corrected. Problem Addressed: If you deleted an ASU special share (C$, D$, ADMIN$, IPC$, or PRINT$), the ASU server would recreate the share when it restarted, but with incorrect permissions. This problem has been corrected. Permissions are set correctly when a special share is recreated. Problem Addressed: Duplicate ASU messages were sometimes posted to the Event Manager (EVM). This problem has been corrected. Problem Addressed: When the Tru64 UNIX EVM Channel manager restarted, the ASU server posted a mark event, which was similar to an EVM mark event. The ASU mark event was confusing and unnecessary. This problem has been corrected. The ASU server no longer posts a mark event. Problem Addressed: On a client, displaying files in an ASU share took an excessive amount of time if there were a large number of files in the share. This problem has been corrected. Problem Addressed: The ASU directory replicator service was not replicating the Access Control Lists (ACLs) on files and directories. This problem has been corrected. Problem Addressed: The browser service on an ASU server might stop if it was configured in a domain that contained a system running Samba Version 2.2 or earlier that was configured as the Domain Master Browser. To correct this problem, upgrade to a newer version of Samba. Problem Addressed: If the daemon account was not in the /etc/passwd file, the ASU server did not start. This problem has been corrected. If the daemon account is not in the /etc/passwd file, the ASU server now logs the problem to the ASU system event log, which can be viewed by the following command: # elfread -d system Problem Addressed: NetApp Filer is a device that works as a network storage server. Previously, you could not use the cifs setup command to configure NetApp Filer as a member server in a domain in which the ASU server was a PDC. When doing so, the following error message was displayed: LsaOpenPolicy2: Exception rpc_s_call_id_not_found caught This problem has been corrected. Problem Addressed: The ASU lmx.ctrl process crashed when reading a browse list that had more entries than specified by the value of the MaxIpcReadCount registry entry in the SYSTEM\CurrentControlSet\Services\AdvancedServer\Parameters ASU registry path. This problem has been corrected. Problem Addressed: Both the LmCompatibilityLevel parameter in the [ lmxserver ] section in the lanman.ini file and the LMCompatibilityLevel registry entry in the SYSTEM/CurrentControlSet/Control/Lsa registry path specify the mode of authentication and session security that the ASU server uses for Network logins. By default, the LmCompatibilityLevel registry entry is: - Set to zero (0) (the default) when the asusetup utility runs - The value used when the ASU server starts You must ensure that the LmCompatibilityLevel parameter in the lanman.ini file has the same value as the LmCompatibilityLevel registry entry. Problem Addressed: Some applications, such as the Event Viewer, Server Manager (srvmgr), User Manager for Domains (usrmgr), and the Registry Editor (regedt32) might fail when establishing a connection to an ASU server from a Windows client and display an error message indicating that access was denied and that the domain controller for the domain could not be found. To fix this problem, use one of the following methods to first establish a network connection from the client to any share on the ASU server, and then rerun the application. - Map Network Drive menu item from Windows Explorer. - Enter the net use command from a command prompt; for example: # net use j: \\pdc_name\netlogon Problem Addressed: The netlogon service might not log users into an ASU server that is configured as a member server in a domain in which a BDC was promoted to the PDC. To correct this problem, enter the following command to restart the netlogon service: # net start netlogon Problem Addressed: The ASU lmx.ctrl process would stop if the ASU server was using the deckanji, sdeckanji, or eucJP server codeset to perform server to client codeset conversion. This problem has been corrected. Problem Addressed: You could not use Microsoft Explorer to rename a folder in an ASU share if that folder was selected by another user using Microsoft Explorer. The following error message was displayed: Cannot rename 'folder_name': The process cannot access the file because another process has locked a portion of the file. This problem has been corrected. Problem Addressed: Windows 2000 users could not share a Microsoft Excel 2000 document with shared workbook in an ASU share. The following error message was displayed: File is locked. In order to save changes to the file, you can either close the file before making any changes and then re-open it, use Save As (File menu) to save the file using another filename, or turn off Shared Workbooks and then save the file. This problem has been corrected. Problem Addressed: Configuring the ASU directory replicator service on an ASU member server to log on as a user account from the domain (as opposed to a local user account) fails and the following message is displayed: Cannot set the startup parameters for the directory replicator service. Error 1057 occurred: The account name is invalid or does not exist This problem will be corrected in a future release. Problem Addressed: The procedure to configure the directory replicator service on an ASU server is not included in the ASU documentation. Please refer to the following URL for information on how to configure the directory replicator service: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ - dnntpro00/html/directory.asp The ASU documentation will be updated in a future release. The following extra listen name problems have been corrected: * You can now add a printer share using an extra listen name as the server name. * Removing an extra listen name that consisted of only a dot (.) no longer removes all single character extra listen names. * The asusetup utility no longer fails when adding an extra listen name that contained a dot (.) if the name pattern matched an existing extra listen name. For example, you can add an extra listen name of server.1 if the extra listen name of serverx1 exists. The following command problems have been corrected: * The elfread command no longer crashes if it were run while the ASU server was starting (Note: The Event Manager (EVM) automatically invokes the elfread command every five minutes). * The statistics totals displayed by the lmstat command would sometimes decrease if an ASU server process terminated. The lmstat command now displays statistics totals that include both terminated ASU server processes and currently running ASU server processes. * The lmstat -n command has been enhanced to display the following information that is useful for debugging and performance analysis purposes: - The number of times that the ASU server entered datagram flow controlled state. Note the value of this number under normal circumstances for your domain. If this number significantly increases, set the value of the ccmsgtodcname parameter in the lanman.ini file to no as described in the first release note in this document. If the problem persists, notify HP software support. - The number of times that the ASU server failed to acquire a byte range lock. This can happen because another UNIX process has a lock on the same byte range. * The acladm -U command no longer deletes too many Access Control Entries (ACEs) on an ASU member server. * The samcheck -s command on an ASU member server no longer displays the following error message: 1 built-in objects were missing. 2 membership links were incomplete. -------------------------------------------------------------------- ASU TruCluster Server Version 5.x Problem Descriptions and Solutions -------------------------------------------------------------------- Problem Addressed: When using the asusetup utility to configure the ASU server to run in single mode, the following error message is displayed if the cluster alias name and the server name are different: ERROR: An account for this machine cannot be created. ERROR: The Compaq Advanced Server V5.1B ECO1 for UNIX was unable to be configured successfully. To fix this problem, use the same name for the cluster alias name and server name. For example, if the cluster alias name is rack and the server name is mini20, specify rack as the server name. The following problems have been corrected: - Using the asusetup utility to reconfigure an ASU server from single mode (CAA) to multi mode now unregisters the ASU server with CAA. - You can now configure extra listen names on TCP/IP in a CAA cluster. - The ASU directory replicator service no longer fails to start on ASU servers configured in multi mode. - The ASU lmx.srv process no longer crashes while processing a transaction Server Message Block (SMB) that included the cluster alias. ------------------------ New ASU Registry Entries ------------------------ New Entry: The PreserveUnixGroups registry entry was added to the SYSTEM\CurrentControlSet\Services\AdvancedServer\FileServiceParameters path in the ASU registry. The PreserveUnixGroups entry specifies whether or not the ASU server preserves the UNIX groups on files in ASU shares. The default value is 0 (do not preserve UNIX groups). Setting the value to 1 preserves UNIX groups on files in ASU shares. If the value of the UseUnixGroups entry is 0, then the UNIX group is used to store DOS attributes instead of group ids. However, if the value of the PreserveUnixGroups entry is 1, then files created through UNIX will not have the group id changed to store DOS attributes. New Entry: The HideDotFiles registry entry was added to the SYSTEM\CurrentControlSet\Services\AdvancedServer\FileServiceParameters path in the ASU registry. The HideDotFiles entry specifies whether or not file names that start with a dot (.) are displayed on a client. The default value is 0 (display all file names). Setting the value to 1 causes file names that start with a dot to be hidden. New Entry: The AutoDisconnectNullSessions registry entry was added to the SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters path in the ASU registry. The AutoDisconnectNullSessions entry specifies the interval, in minutes, the ASU server waits before disconnecting the virtual circuit to an inactive client that has no logged-in sessions. The purpose of this registry entry is to prevent null sessions (sessions from clients with no logged-in users) from using ASU licenses unnecessarily. The default value is 5 minutes. A value of zero (0) means no automatic disconnect of null sessions. New Entry: The UnixDirectoryPerms registry entry was added to the SYSTEM\CurrentControlSet\Services\Replicator\Parameters path in the ASU registry. The UnixDirectoryPerms entry specifies the permissions of directories that are imported by the ASU directory replicator service. The default value is 775 (octal). New Entry: The UnixFilePerms registry entries was added to the SYSTEM\CurrentControlSet\Services\Replicator\Parameters path in the ASU registry. The UnixFilePerms entry specifies the permissions of files that are imported by the ASU directory replicator service. The default value is 664 (octal). New Entry: The SyncUnixPerms registry entry was added to the SYSTEM/CurrentControlSet/Services/AdvancedServer/FileServiceParameters path in the ASU registry. The SyncUnixPerms entry specifies whether or not the ASU server updates Tru64 UNIX permissions when a Windows NT Access Control List (ACL) is created or updated for a file or directory. The default value is 0 (do not update Tru64 UNIX permissions). If you set the value to 1, Tru64 UNIX permissions are updated when an ACL is created or updated. The following table identifies which Windows NT Access Control Entry (ACE) affects which Tru64 UNIX permissions: Windows NT ACE user/group Tru64 UNIX permissions affected ------------------------- ------------------------------- NT owner of file owner permissions NT group mapped to the Unix group owner of file group permissions, if UseUnixGroups=1 Everyone group permissions, if UseUnixGroups=0 Everyone other permissions Anyone not in the above list none If there is no explicit Windows NT ACE to map to a particular Tru64 UNIX permission, the default Windows NT permission is No Access. Note that the default value of the UseUnixGroups entry is 0. The following table identifies the mapping of Windows NT permissions to Tru64 UNIX permissions: Windows NT permissions Tru64 UNIX permissions ---------------------- ---------------------- Full Control (All) rwx Change (RWXD) rwx Read (RX) r-x No Access --- Special Access (R) r-- Special Access (W) -w- Special Access (X) --x Special Access (D) --- Special Access (P) --- Special Access (O) --- If there are multiple Special Access permissions, the corresponding Tru64 UNIX permissions are combined. ------------------- ASU General Changes ------------------- Change: The ASU server supports systems configured with LAG (Link aggregation) network support. You can configure the ASU server to listen on NetBIOS over TCP/IP and NetBEUI over the LAG interface. Change: When negotiating a protocol with a remote server, the ASU server now sends the list of dialects that it supports in one SMB packet. This improves ASU server performance and keeps the lmx.dmn process from hanging when the remote server is Windows NT. Change: The default size of the debug log has increased from 20,000 KB to 100,000 KB. Change: The blob manager has been enhanced to shrink the hash table areas in blob files when many blobs have been deleted. This means that the acladm -T command to trim redundant ACLs will very often shrink the ACL hash table. Change: A new parameter called asuevm was added to the lanman.ini file in the [lmxserver] section. The asuevm parameter specifies whether or not ASU events are logged by the Event Manager (EVM). The default value is yes (log ASU events to EVM). Setting the value to no will cause EVM to not log ASU events. Change: The ASU server displayed the following error message when saving files with names containing Unicode characters in an ASU share on a system that did not have the Tru64 UNIX World Wide Language Support subsets installed: The filename syntax is incorrect. This error message has been changed to display: No mapping for the Unicode character exists in the target multi-byte code page. The following lists ASU command changes: * The getrole command has a new -l option that displays the name of the local domain for an ASU member server. * The elfread command displays an event for each corrupt type of blob file. * The lmstat -n command displays the blob error counts for each type of blob file. * The mapuname command supports mapping of Windows NT groups to UNIX groups when the SyncUnixPerms and UseUnixGroups registry entries are enabled. Mapping a Windows NT group to a UNIX group allows the SyncUnixPerms entry to determine which NT group corresponds to the UNIX group owner of a file. You use the -g option with the -l, -a, -d, or -p options to manage group mappings. For example, to add a mapping of the Windows NT group project1 in master.dom domain to the UNIX group project1, enter: # mapuname -a -g master.dom:project1 project1 The Windows NT group name and the UNIX group name do not have to be the same. Also, map only one Windows NT group to any particular UNIX group. * The net perms command would display the following error message if it encountered an access control entry (ACE) for a deleted user or group: Error 13 has occurred The net perms command now displays: domain_name\hex_rid The domain_name is the name of the domain from which the user or group was deleted and hex_rid is the deleted user or group's relative ID (RID) formatted as a hex number. A hex number is displayed because the user or group name is no longer available. To remove ACEs for deleted users and groups, enter: # acladm -U ----------------------------- ASU Installation Instructions ----------------------------- This ECO kit is a complete software kit that includes the features and functionality of previous ASU software releases, and provides corrections for the problems described in this document. If you are installing the ASU software for the first time, change to the directory where the ECO software was downloaded, enter the following command, and follow the instructions on the screen: # setld -l . If you have ASU, ASDU, or PATHWORKS for DIGITAL UNIX subsets installed, you must use the Tru64 UNIX setld command to deinstall those subsets before you install the subsets in this ECO kit. Follow these steps to use the setld command to deinstall ASU, ASDU, or PATHWORKS subsets and install the ECO software: 1. Display the installed ASU, ASDU, or PATHWORKS subsets. Enter one of the following commands depending on the software installed: # /usr/sbin/setld -i | grep ASU | grep installed # /usr/sbin/setld -i | grep ASDU | grep installed # /usr/sbin/setld -i | grep PATHWORKS | grep installed 2. Deinstall the ASU, ASDU, or PATHWORKS subsets. Enter the /usr/sbin/setld -d command followed by the name of each subset. For example, to deinstall the ASU Version 5.0 base, transport, and reference page subsets enter: # /usr/sbin/setld -d ASUBASE500 ASUTRAN500 ASUMANPAGE500 While subsets are being deinstalled, you are prompted to save configuration files and the user account and share databases. Save these files and databases if you want to reuse them with the ASU Version 5.1B ECO1 software. 3. Install the ASU Version 5.1B ECO1 software. Change to the directory where the ASU Version 5.1B ECO1 software was downloaded, enter the following command, and follow the instructions on the screen: # setld -l . See the ASU Installation and Administration guide for more information on installing the ASU software. =============================================================== Copyright 2003 Hewlett-Packard Company. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Hewlett-Packard Company. Possession, use, duplication, or dissemination of the software and media is authorized only pursuant to a valid written license from Hewlett-Packard Company.