Dear SCO Customer, Support Level Supplement (SLS) APP606A, the Advanced File and Print Server 3.5.2n Supplement, corrects the NetBEUI transport protocol with regard to file transfer failures, the capture of network logoff activity into the event log, domain naming, server version numbering, net command output, ACL creation and management, file system operations, browser service, printing to networked printers, and several Year 2000 items. SLS APP606A supersedes the earlier AFPS 3.5.2 supplement, APP477A, in that all fixes provided in APP477A are provided in SLS APP606A. This includes all Year 2000 related fixes. There are no new Year 2000 fixes provided in SLS APP606A. SLS APP477A is not being obsoleted at this time. It will continue to be available for systems that need to remain at a known state of readiness for the year 2000. The updates contained in SLS APP606A are outlined below. The NetBEUI Transport Protocol: Copying files from the server to the client would fail when using a Compaq Netelligent network card in the server. The message "The device is no longer available" appeared on the client during the file transfer. Examining the network traffic using a dedicated network monitor revealed a large number of short/runt packets originating from the server. Changes have been made to the NetBEUI driver to provide correct interoperability with the Compaq Netelligent network interface card. Event Logging: Logon and logoff events were not being correctly recorded into the event log for Microsoft Windows 95 clients. This activity is now captured and recorded correctly and is visible in the event log viewer. Domain Names: The server configuration tool forced the domain name of "DOMAIN" to the lowercase equivalent of "domain". The server configuration tool has been changed to allow the assignment of "DOMAIN" as a valid domain name. It is usual practice, however, to choose a domain name that more appropriately reflects the environment in which the server will be used. Server Version Numbering: The version number that is displayed when the server is started has been changed from 3.5.1 to 3.5.2 to agree with all other visible server version information, such as that which is displayed by the "net version" command. Year 2000 Readiness: The following changes have been made to the SCO Advanced File and Print Server 3.5.2n to support Year 2000 SCO criteria: 1. The net user /EXPIRES:mm/dd/00 command now correctly assumes that the year "00" is the year 2000. 2. The command /usr/bin/lmshell properly displays file date/timestamps for the year 2000 and beyond. 3. The net user /TIMES command no longer returns an error when the year is past 1/1/2000. 4. The command /usr/net/servers/lanman/bin/elfread no longer displays dates past 1/1/2000 incorrectly. Net Command Output: Incorrect permissions were displayed by "net perms" when a file or directory name consisted of mixed case characters. This information is now displayed correctly. ACL Creation and Management: Various fixes have been included that relate to the creation and management of Access Control Lists (ACLs) in the ACL database. The fixes address the following problems: 1. ACL erroneously created for all files when renaming a directory. 2. ACL erroneously created when renaming a file. 3. Usage message for lsacl is incomplete. 4. The rmacl command may fail but still reports success. 5. The acladm -C command removes items without informing user. 6. The acladm -O command creates default ACLs for non-existent directories. 7. The acladm -O command hangs if no ACL database exists. 8. The lsacl -E command does not identify which object belongs to which ACL. Also, no tool exists to truncate an ACL database file that has been emptied of dead ACL entries using the "acladm -P" command. To address this requirement, a new version of blobadm has been provided. The command "blobadm -A -q" will truncate an ACL database file that has been emptied of dead ACL records. Note: It is necessary to stop the server before running the blobadm command. File System Operations: Fixes to the following file system related problems have been included: 1. Moving files that are under a symbolic link may fail. 2. Setting of file attributes may fail due to incorrect current directory. 3. Moving files between UNIX file system may not delete the original copy. 4. Failure to report error when moving a file and the destination file exists. 5. Moving file between UNIX file systems does not retain original date/time. 6. Moving directory between UNIX file systems may fail from NT workstation. 7. Renaming directory in read-only parent directory may change it to a file. Browser Service: The master browser service may fail if there are more than a total of 150 servers and NT workstations in a single domain. This limitation has been removed. Printing to Networked Printers: Under heavy load conditions, printing to remote UNIX printers (or network printers that support the LPD protocol) from NT workstations via the AFPS server may result in the failure of an AFPS server process. The symptoms are that a small number of users will simultaneously lose their connections to the AFPS server. The server will otherwise continue to function normally and the displaced users will be able to reconnect to their resources. The remote printer has been set up correctly, following the instructions in the AFPS Administrator's Handbook. This problem has been resolved. Software Notes and Recommendations ---------------------------------- SLS APP606A is only intended for use on: SCO Advanced File and Print Server Release 3.5.2n This SLS will not install on top of any previously released patches for AFPS Release 3.5.2n. Use the Software Manager to check which patches are currently installed on the system. If an SLS (patch) for AFPS 3.5.2n is already installed, "rollback" and "unload" the earlier patch before installing SLS APP606A. I. INSTALLING SLS APP606A 1. Prepare the files for installation. Download the APP606A VOL files from the SLS/app606a directory on SCO's ftp site. Place the files in the /tmp directory on the local server. The files should include: VOL.000.000 VOL.001.000 app606a.ltr 2. Log onto the local server as root and run the Software Manager with the command: # scoadmin software or double-click on the Software Manager icon in the desktop. 3. For SCO OpenServer 5.0.4, pull down the "Software" menu and select "Install New". For Internet FastStart 1.x, and SCO OpenServer 5.0.0 or 5.0.2, pull down the "Software" menu and select "Patch Management --> Apply Patch". 4. When prompted for the host from which to install, choose the local machine and then "Continue". 5. When prompted to select the media device: If you are installing this SLS from media images, select "Media Images", then "Continue". When prompted for the "Image Directory", enter "/tmp" (or the directory where you placed the VOL files in step 1) and then select "OK". 6. For SCO OpenServer 5.0.4, when prompted to select software to install, ensure that the "APP606A" entry is highlighted. Choose "Install". For Internet FastStart 1.x, SCO OpenServer 5.0.0 or 5.0.2, when prompted to select installation type, choose "Full". 7. Once the installation finishes, quit the Software Manager. Installation of SLS APP606A is now complete. 8. During the installation of SLS APP606A, the kernel will be relinked. To make use of the patch, the system must be shut down and rebooted. II. REMOVING SLS APP606A Note: Patches must be rolled back in the reverse order in which they were installed on a per-component basis. Hence, if the SLS APP606A patch is not the most recent patch applied to the UNIX component of the product, you will have to roll back all patches applied after the SLS APP606A patch prior to rollback of the SLS APP606A patch. If you ever want to remove the patch, take these steps: IIa. Removing SLS APP606A from SCO OpenServer 5.0.4 1. Log in as root. 2. Execute the command: # scoadmin software or double-click on the Software Manager icon in the desktop. 3. Highlight SCO Advanced Server 3.5.2 Supplement APP606A. 4. Pull down the "Software" menu and select "Remove Software". 5. Once the removal finishes, quit the Software Manager. Removal of SLS APP606A is now complete. 6. Removing the patch will cause a kernel relink. To discontinue use of the patch, the system must be shut down and rebooted. IIb. Removing SLS APP606A from SCO OpenServer 5.0.0, 5.0.2 and Internet FastStart 1.0, 1.1 1. Log in as root. 2. Execute the command: # scoadmin software or double-click on the Software Manager icon in the desktop. 3. Pull down the "Software" menu and select "Patch Management-->Rollback Patch". 4. You will see the "Begin Rollback Patch" menu, and be asked to select patched software to roll back. Select "File and Print Services" and choose "Continue". 5. You will see the "Patch Selection" window. Make sure that the "File and Print Services Supplement (APP606A)" is selected, and choose "Continue". 6. You will see the "Confirm Selected Patches" window. Choose "Rollback" to confirm removal of the "File and Print Services Supplement (APP606A)". 7. You will see the "Rollback Progress" window, as the system performs the rollback of the patch. 8. Pull down the "Software" menu and select "Patch Management-->Rollback Patch". 9. You will see the "Begin Rollback Patch" menu, and be asked to select patched software to roll back. Select "NetBEUI Protocol" and choose "Continue". 10. You will see the "Patch Selection" window. Make sure that the "NetBEUI Supplement (APP606A)" is selected, and choose "Continue". 11. You will see the "Confirm Selected Patches" window. Choose "Rollback" to confirm removal of the "NetBEUI Supplement (APP606A)". 12. You will see the "Rollback Progress" window, as the system performs the rollback of the patch. 13. You will see this message: NOTE: Application or rollback of this patch requires a kernel relink. If you are applying or rolling back several patches at this time, you may choose to defer the relink until the last patch application or rollback. Do you want to relink the kernel now? (y/n) Enter "y" or "n" based on this message. Note that complete rollback of this patch requires a relink of the kernel to be complete, hence it is suggested that you answer "y" to this question, unless you are installing or removing other patches. 14. If you chose "y" in step 13, the kernel will be relinked. In either case, you will then see: Press to continue After pressing the key, you will see the "Rollback Progress" window, after which a "Message" window stating "Rollback Patch Complete". Choose "OK" and you will be returned to the Software Manager's main menu. Exit the Software Manager by choosing "Exit" from the "Host" menu. 15. Log in as root on tty01, and shut down the system: # shutdown -g0 -y After shutting down and rebooting the machine, rollback of the patch is complete. 16. To also unload the patch, making it no longer available to be applied, follow the steps in this section. In step 3, choose: "Patch Management-->Unload Patch" instead of: "Patch Management-->Rollback Patch" If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier.