PATHWORKS V6.0 for OpenVMS (Advanced Server), ECO2__________________________________________ Release Notes The PATHWORKS V6.0 for OpenVMS (Advanced Server), ECO2 Release Notes include information about the distribution kit, software features and usage guidelines, the latest problem fixes, known problems, and restrictions. These Release Notes supplement the product documentation. Always read the Release Notes before you start the product installation. Revision/Update Information: This document replaces the PATHWORKS V6.0 for OpenVMS (Advanced Server) Release Notes. Operating System: OpenVMS Alpha, Version 7.1 Software Version: PATHWORKS V6.0 for OpenVMS (Advanced Server), ECO2 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ First Published, August 1997 Revised, February 1998 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. DIGITAL conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Digital Equipment Corporation 1997, 1998. All rights reserved. The following are trademarks of Digital Equipment Corporation: DEC, DECnet-Plus, DECprint, DIGITAL, OpenVMS, PATHWORKS, and the DIGITAL logo. The following are third-party trademarks: AT&T is a registered trademark of American Telephone and Telegraph Corporation. Apple, LaserWriter, AppleShare, Macintosh, and TRUETYPE are registered trademarks of Apple Computer, Inc. DEC Rdb is a trademark of Oracle Corporation. Hewlett-Packard, HP, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company. IBM and OS/2 are registered trademarks of International Business Machines, Inc. Microsoft, MS-DOS, Windows, and Windows 95 are registered trademarks, and Windows NT is a trademark of Microsoft Corporation. MultiNet and TCPWare are registered trademarks of Process Software Corporation. Novell and NetWare are registered trademarks of Novell, Inc. PostScript is a registered trademark of Adobe Systems, Inc. All other trademarks and registered trademarks are the property of their respective holders. The PATHWORKS for OpenVMS (Advanced Server) documentation set is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. v 1 Distribution Kit 2 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2.1 PATHWORKS V6.0 for OpenVMS (Advanced Server) Features..................................... 2-1 2.1.1 Windows NT Domain Services............... 2-2 2.1.2 Installation and Configuration........... 2-2 2.1.2.1 Upgrade Utility........................ 2-3 2.1.2.2 Initial Server Configuration Procedure.............................. 2-3 2.1.2.3 Configuring Server Parameters.......... 2-3 2.1.3 File and Print Services.................. 2-4 2.1.4 Client Support........................... 2-4 2.1.5 Transport Support........................ 2-4 2.1.5.1 DECnet Support......................... 2-4 2.1.5.2 TCP/IP Support......................... 2-5 2.1.5.3 WINS Server Support.................... 2-5 2.1.6 PostScript Printing Support.............. 2-5 2.1.7 Management Interfaces.................... 2-5 2.1.7.1 ADMINISTER Command Line Interface...... 2-5 2.1.7.2 Windows NT Server Administration Tools.................................. 2-6 2.1.8 PATHWORKS Advanced Server Licensing...... 2-6 2.1.8.1 License Enforcement.................... 2-7 2.1.9 External Authentication Support.......... 2-7 iii 2.2 Differences Between PATHWORKS V5 for OpenVMS (LAN Manager) and PATHWORKS V6 for OpenVMS (Advanced Server)............................ 2-8 2.3 Unsupported PATHWORKS V5 for OpenVMS (LAN Manager) Features............................ 2-9 3 Guidelines for Using the PATHWORKS Advanced Server Software 3.1 Server Configuration......................... 3-1 3.1.1 Configuring Physical Memory for Running Both PATHWORKS Advanced Server and the NetWare Server........................... 3-1 3.1.2 Allocating Sufficient Resources to Support Clients.......................... 3-1 3.1.3 Monitoring Data Cache Use by the File Server................................... 3-2 3.2 External Authentication Logon Information.... 3-3 3.2.1 Avoiding User Name Conflicts............. 3-4 3.2.2 Setting Up External Authentication by a Trusted Domain........................... 3-5 3.2.3 Implicit Host Mapping.................... 3-6 3.3 Netlogon Service for a Client................ 3-7 3.4 Administering Shares from a Windows NT Server....................................... 3-7 3.4.1 Adding a Share From a Windows NT Server................................... 3-8 3.4.2 Enumerating Shares or Modifying Shares From a Windows NT Server................. 3-9 3.5 Removing PATHWORKS Advanced Server ACEs From a File....................................... 3-9 3.6 Managing Licenses and Licensing Software..... 3-9 3.6.1 Server-Based Licensing................... 3-10 3.6.2 Client-Based Licensing................... 3-10 3.6.3 Upgrading Client-Based Licenses.......... 3-11 3.6.4 License Server Information............... 3-11 3.6.5 License Server Startup and Shutdown...... 3-12 3.6.5.1 Integrated License Server Startup...... 3-13 3.6.5.2 Integrated License Server Shutdown..... 3-14 3.6.5.3 Joint PATHWORKS Advanced Server and NetWare Startup........................ 3-14 3.6.5.4 Joint PATHWORKS Advanced Server and NetWare Shutdown....................... 3-14 iv 3.6.5.5 Standalone License Server Startup and Shutdown............................... 3-15 3.6.6 License Server Configuration Parameters............................... 3-15 3.6.7 Determining Configuration Parameter Values................................... 3-15 3.6.8 Dynamic Configuration Parameters......... 3-16 3.6.9 Controlling License Registrar Logging.... 3-16 3.6.10 License Registrar Messages............... 3-17 3.6.11 Setting the PWRK$LICENSE_SERVER_INHIBIT Parameter................................ 3-18 3.7 Defining Communications Devices.............. 3-19 3.8 Using TCP/IP Products With PATHWORKS Advanced Server....................................... 3-20 3.9 Time Zone Setup.............................. 3-21 4 Problems Corrected in ECO2 4.1 Windows 95 Cannot Enumerate All Shares on the Server....................................... 4-1 4.2 Unable to Complete PWRK$CONFIG After Upgrade...................................... 4-1 4.3 MS ACCESS Unable to Open a File Read/Write... 4-2 4.4 Fatal Exception Results on Windows 95 Explorer..................................... 4-2 4.5 Unable to Log On to Any Domain on a Different Subnet....................................... 4-2 4.6 ADMINISTER Command Hangs..................... 4-2 4.7 TCP/IP Stops Responding to Requests.......... 4-3 4.8 XCOPY From MS-DOS Command Fails to Create Subdirectory................................. 4-3 4.9 File Server Crashes When Enumerating Open Files........................................ 4-3 4.10 Incorrect Error Status Returned.............. 4-4 4.11 Server Cannot Validate Connection Requests in a Trust...................................... 4-4 4.12 File Server Becomes 100% CPU-Bound When Validating Connection Requests............... 4-4 4.13 Windows 95 and Windows NT Clients Time Out When Copying Large Files to the PATHWORKS Advanced Server.............................. 4-5 4.14 Nonpaged Pool Leak When Running With TCP/IP Services for OpenVMS V4.1, ECO6.............. 4-5 v 4.15 File Modification Date Is Not Preserved When the File Is Copied From a Workstation........ 4-6 4.16 Upgrade Utility Fails to Translate User Logon Hours Using GMT.............................. 4-6 4.17 License Server Crashes at Restart............ 4-6 4.18 Loss of Server-Based License Units........... 4-6 4.19 Memory Leak in Print Function................ 4-7 4.20 Unable to Print to OpenVMS V6.2 Print Queue........................................ 4-7 4.21 Memory Leak in PWRK$LMDMN Process............ 4-8 4.22 Session Limit Is Incorrectly Set to 99....... 4-8 4.23 Unable to Access File Name That Has a Period at Position 40............................... 4-8 4.24 PWVER Command Displays an Obsolete Image..... 4-8 4.25 PWRK$DELETEACE Is Not Accessible After Rollback or Deinstallation................... 4-9 5 Known Problems in PATHWORKS for OpenVMS (Advanced Server) 5.1 Domain Management Problems................... 5-1 5.1.1 A Computer Cannot Be Removed From the Domain If It Has Been Promoted to Be a PDC in Another Domain.................... 5-1 5.2 User Interface Problems...................... 5-1 5.2.1 SET PASSWORD Command Does Not Always Set the Password Correctly................... 5-1 5.2.2 The /TYPE=NO* Qualifier Does Not Function with the ADMINISTER Command SHOW CONNECTIONS.............................. 5-2 5.2.3 Unable to Change an Expired Password When Using the ADMINISTER Command LOGON....... 5-2 5.2.4 SEND/USERS Command Reports an Error...... 5-3 5.2.5 Misleading Error Message with ADMINISTER Commands for Managing User Account Host Mapping.................................. 5-3 5.2.6 REMOVE PRINT QUEUE Command Fails to Remove the Queue If the Print Queue Is Not Stopped.............................. 5-4 5.2.7 SHOW FILE Command Fails to List Subdirectories........................... 5-4 5.2.8 Incorrect Count of Active Links Displayed After a Forced Disconnect................ 5-4 vi 5.3 Windows NT Interoperability Problems......... 5-5 5.3.1 Upgrade Utility Does Not Upgrade Locked-Out Users......................... 5-5 5.3.2 Nonstandard Domain Guest Group on Windows NT Servers Causes Replication to Fail.... 5-5 5.4 Host Mapping Problems........................ 5-6 5.4.1 A Host Map Setting From a Trusted Domain Cannot Be Removed After the Trust Relationship Has Been Removed............ 5-6 5.5 File Server Problems......................... 5-6 5.5.1 PATHWORKS Advanced Server Fails to Properly Handle Corrupted ACEs........... 5-6 5.5.2 Moving a Subdirectory May Not Preserve Security Settings........................ 5-7 5.5.3 PATHWORKS Advanced Server Cannot Support More Than 32,767 Shares.................. 5-7 5.5.4 File Permissions Are Not Displayed on Initial Connect.......................... 5-7 5.5.5 File Server May Issue Incorrect BlobCache Warning Messages......................... 5-8 5.6 Event Logging Problems....................... 5-8 5.6.1 SHOW EVENTS/FULL Command Fails to Display Messages with ID 6033.................... 5-8 5.6.2 Incorrect Audit Type When Password Change Failure Event Occurs..................... 5-9 5.6.3 Incorrect Syntax in SHOW EVENTS Backup File Causes the Server to Fail........... 5-9 5.7 Licensing Problems........................... 5-9 5.7.1 License Manager Always Reports Zero Usage of PWLMXXXCA06.00 Licenses Allocated to the Server-Based Group................... 5-9 5.7.2 License Registrar Interval Parameters Do Not Immediately Use New Values When a Change to the Parameter Value Is Noticed.................................. 5-10 5.8 Upgrade Problems............................. 5-10 5.8.1 Rollback Fails to Delete All PATHWORKS Advanced Server Data Files............... 5-10 5.8.2 Upgrade May Fail to Start Selected Transports............................... 5-11 5.9 Documentation Corrections.................... 5-11 5.9.1 Corrections to the Server Administrator's Guide.................................... 5-11 vii 6 Restrictions of PATHWORKS for OpenVMS (Advanced Server) 6.1 Installation and Configuration Restrictions................................. 6-1 6.1.1 PATHWORKS Advanced Server Cannot Coexist with PATHWORKS V5.0C for OpenVMS (LAN Manager) Server.......................... 6-1 6.1.2 OpenVMS Version 7.1 Requires a Patch..... 6-1 6.1.3 PATHWORKS Advanced Server May Fail at Startup Time If SYLOGIN.COM Executes with Errors................................... 6-2 6.1.4 PATHWORKS Advanced Server Fails to Start on Non-English Language Versions of OpenVMS.................................. 6-2 6.1.5 PWRK$CONFIG Fails to Move the PATHWORKS On-Disk Structure........................ 6-2 6.2 User Interface Restrictions.................. 6-2 6.2.1 Mouse Selection Highlights Entire Screen................................... 6-3 6.2.2 Windows NT Print Manager Fails to Display PATHWORKS Advanced Server Printers....... 6-3 6.2.3 File Server Unable to Resolve Job Logical Translation as Part of a File Specification............................ 6-3 6.2.4 Autoshares Are Not Enumerated by PATHWORKS Advanced Server................ 6-4 6.3 Event Logging Restrictions................... 6-4 6.3.1 Event Log Files Fail to Wrap When Full... 6-4 6.3.2 Unable to Set the Event Logging Setting.................................. 6-4 6.3.3 Displaying Application Event Log Files... 6-4 6.3.4 OpenVMS SET PASSWORD on an Externally Authenticated User Account Is Not Audited.................................. 6-5 6.4 File Server Restrictions..................... 6-5 6.4.1 Ownership of a Directory................. 6-5 6.4.2 DEFZA FDDI Controller Is Not Supported in PATHWORKS Advanced Server................ 6-5 6.4.3 Premature Disk Full Conditions........... 6-6 6.4.4 Server Does Not Enforce Disk Quotas by Default.................................. 6-6 6.4.5 DECram Performance Problem............... 6-7 viii 6.4.6 Access Denied to Files Restored From Backup of Another System................. 6-7 6.4.7 Intruder Flag's Relationship to PC Connections and Logons................... 6-7 6.4.8 XCCB Not in Use Errors in LMMCP Log File..................................... 6-8 6.5 PATHWORKS Advanced Server Interaction with Oracle Rdb................................... 6-8 Tables 3-1 Undefined Device Messages................ 3-19 ix ________________________________________________________________ Preface Purpose The PATHWORKS V6.0 for OpenVMS (Advanced Server), ECO2 Release Notes include information about the distribution kit, software features and usage guidelines, the latest problem fixes, known problems, and restrictions. These Release Notes supplement the product documentation. Always read the documentation as well as the product Release Notes. Audience These Release Notes are intended for the PATHWORKS for OpenVMS (Advanced Server) system administrator. It assumes you have: o A basic understanding of a PC LAN network o A basic understanding of OpenVMS system management o Access to the PATHWORKS for OpenVMS (Advanced Server) documentation v Related Documents The release notes supplement the following manuals: __________________________________________________________ Reference___________________Topic_________________________ DIGITAL PATHWORKS Explains how to install and for OpenVMS Server configure the components Installation and of PATHWORKS for OpenVMS Configuration Guide (Advanced Server) software including: o The Advanced Server o The NetWare server o The license server o The Upgrade utility DIGITAL PATHWORKS for Explains how to upgrade the OpenVMS (Advanced Server) PATHWORKS for OpenVMS (LAN Server Migration Guide Manager) software to PATHWORKS V6.0 for OpenVMS (Advanced Server) software. DIGITAL PATHWORKS for Explains how to manage and OpenVMS (Advanced Server) customize the PATHWORKS for Server Administrator's OpenVMS (Advanced Server) Guide software. DIGITAL PATHWORKS for Provides an overview and OpenVMS (Advanced Server) introduction to the PATHWORKS Concepts and Planning for OpenVMS (Advanced Server) Guide software and associated networking concepts for system administrators and operators. DIGITAL PATHWORKS for Describes the license server OpenVMS Guide to Managing software and how to manage DIGITAL PATHWORKS Licenses PATHWORKS licenses. vi __________________________________________________________ Reference___________________Topic_________________________ DIGITAL PATHWORKS for Lists the PATHWORKS for OpenVMS (Advanced Server) OpenVMS Advanced Server Commands Reference Manual ADMINISTER commands, describing and showing examples for each. Lists the LAN Manager Net commands and the equivalent ADMINISTER ____________________________commands._____________________ vii 1 ________________________________________________________________ Distribution Kit The PATHWORKS V6.0 for OpenVMS (Advanced Server), ECO2 software media includes support for Alpha systems, and consists of the following BACKUP savesets: __________________________________________________________ Saveset_Name________OpenVMS_System________________________ PWRKV60_E02060.A Alpha PWRKV60_E02060.C Alpha PWRKV60_E02060.E Alpha PWRKV60_E02060.G Alpha PWRKV60_E02060.H____Alpha_________________________________ Distribution Kit 1-1 2 ________________________________________________________________ Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) The PATHWORKS V6.0 for OpenVMS (Advanced Server), ECO2 software is based on the PATHWORKS V6.0 for OpenVMS (Advanced Server) software. An ECO1 software kit was released to a limited set of customers. This ECO2 kit includes all the software corrections in the ECO1 release. The PATHWORKS for OpenVMS Advanced Server (known as the PATHWORKS Advanced Server) is the next generation of LAN Manager server software. This chapter includes the following information: __________________________________________________________ Section Topic_______________________________________________Number PATHWORKS V6.0 for OpenVMS (Advanced Server) 2.1 Features Differences Between PATHWORKS V5 for OpenVMS (LAN 2.2 Manager) and PATHWORKS V6 for OpenVMS (Advanced Server) Unsupported PATHWORKS V5 for OpenVMS (LAN Manager) 2.3 Features__________________________________________________ 2.1 PATHWORKS V6.0 for OpenVMS (Advanced Server) Features Some of the features provided by PATHWORKS V6.0 for OpenVMS (Advanced Server) are described in the following sections. Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-1 2.1.1 Windows NT Domain Services PATHWORKS Advanced Server allows you to run the server as the primary domain controller (PDC) or the backup domain controller (BDC) in a Windows NT-compatible domain. PATHWORKS Advanced Server can participate in the domain as a Master Browser or Backup Browser. The PATHWORKS Advanced Server supports the ability to be managed remotely from: o Windows NT Server o PATHWORKS Advanced Server o Clients running Windows NT Server administration tools. For information about remote server management, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. 2.1.2 Installation and Configuration PATHWORKS for OpenVMS provides a single installation procedure that allows you to install any of the following: o PATHWORKS Advanced Server software (includes the Upgrade utility and the license server) o NetWare server software (includes the license server) o Upgrade utility only o License server only ________________________Note ________________________ The configuration procedure gives you the option of not running the license server. Only one license server is required for each LAN. _____________________________________________________ 2-2 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2.1.2.1 Upgrade Utility PATHWORKS Advanced Server provides a separately in- stallable Upgrade utility. Use this Upgrade utility to upgrade the server's user, group, and share information from PATHWORKS Version 5 for OpenVMS (LAN Manager) to PATHWORKS V6.0 for OpenVMS (Advanced Server) while the server continues to run. This allows you to plan and upgrade shares, user accounts, and security in preparation for the PATHWORKS Advanced Server installation, without interrupting file and print services. For more information about how to use this new Upgrade utility, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. 2.1.2.2 Initial Server Configuration Procedure A one-time configuration procedure (PWRK$CONFIG.COM) allows you to perform basic on-disk structure setup and configuration modification, as well as allowing you to start the PATHWORKS Advanced Server processes. For more information about installing and configuring the PATHWORKS Advanced Server software, refer to the DIGITAL PATHWORKS for OpenVMS Server Installation and Configuration Guide. 2.1.2.3 Configuring Server Parameters The PATHWORKS Advanced Server provides a new Configuration Manager tool. Use the Configuration Manager to modify server parameters and to enable and disable transport types. Use the following command to start the Configuration Manager: $ ADMINISTER/CONFIGURATION Refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide for more information about using the Configuration Manager. Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-3 2.1.3 File and Print Services PATHWORKS Advanced Server supports the Windows NT- compatible Server Message Block (SMB) V3.0 file and print protocols. 2.1.4 Client Support PATHWORKS Advanced Server supports connections from the following types of clients: o Windows NT o Windows 95 o Windows for Workgroups o PATHWORKS for DOS and Windows o PATHWORKS for Windows 95 o PATHWORKS 32 2.1.5 Transport Support PATHWORKS Advanced Server supports the same types of transports as does PATHWORKS V5 for OpenVMS (LAN Manager), but selects them in the following order, which differs from the order used by the PATHWORKS V5 for OpenVMS (LAN Manager) server: 1. TCP/IP 2. NetBEUI 3. DECnet-Plus (or DECnet Phase IV) 2.1.5.1 DECnet Support PATHWORKS Advanced Server supports DECnet and DECnet-Plus as supported by the OpenVMS Operating System Version 7.1. ________________________Note ________________________ The PATHWORKS mail server works only if DECnet is running on both of the following: o The PATHWORKS server o The client that wants to use the mail server _____________________________________________________ 2-4 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2.1.5.2 TCP/IP Support PATHWORKS Advanced Server provides transparent support for the following TCP/IP network transport products: o TCP/IP Services for OpenVMS, Version 4.1 o MultiNet Version 4.0, Rev. B o TCPware for OpenVMS, Version 5.1 For information about using TCP/IP products with PATHWORKS Advanced Server, refer to Section 3.8. 2.1.5.3 WINS Server Support The PATHWORKS Advanced Server can act as a client to Windows Internet Naming Services (WINS) servers, allowing the PATHWORKS Advanced Server to use a WINS server to resolve NETBIOS names in a Wide Area Network (WAN) configuration. 2.1.6 PostScript Printing Support The PATHWORKS Advanced Server distribution media includes two kits for the DECprint Supervisor for OpenVMS (DCPS) family of layered products, which runs on OpenVMS VAX and Alpha to provide access through the OpenVMS queuing system to selected PostScript printers. To use DCPS, you must install the kit for either VAX or Alpha accordingly. You do not need a separate license to use DCPS with PATHWORKS Advanced Server. 2.1.7 Management Interfaces The following sections describe the management interfaces provided with the PATHWORKS Advanced Server. 2.1.7.1 ADMINISTER Command Line Interface PATHWORKS Advanced Server includes the PATHWORKS Advanced Server command line interface (ADMINISTER commands). These commands are designed to replace the LAN Manager server Net commands on OpenVMS. ADMINISTER commands can be used to remotely manage a Windows NT Server or a PATHWORKS Advanced Server. For more information about how to use the new command line interface, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Commands Reference Manual, or enter Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-5 the ADMINISTER command HELP to get online Help for each command. For example, to get information about the ADMINISTER command ADD USER, enter the following command: $ ADMINISTER HELP ADD USER 2.1.7.2 Windows NT Server Administration Tools As any other domain controller in a Windows NT domain, the PATHWORKS Advanced Server can be managed from a Windows NT Server or from a client running Windows NT Server administration tools. The PATHWORKS Advanced Server software kit includes the Windows NT Server administration tools, which can be installed on computers running any of the following operating systems: o Windows for Workgroups o Windows 95 o Windows NT Workstation These tools are available in the PWUTIL share after you install, configure, and start the PATHWORKS Advanced Server. The SRVTOOLS directory contains a subdirectory for each type of client computer. Refer to the README.TXT file in the subdirectory for instructions on installing the software on the client computer. Refer to the Windows NT Server documentation or use online Help for more information about how to use Windows NT Server administration tools. 2.1.8 PATHWORKS Advanced Server Licensing The PATHWORKS Advanced Server provides a simplified license management model and a new License Manager tool for managing PATHWORKS Advanced Server licenses. Both the license server and License Registrar are installed with the PATHWORKS Advanced Server software. 2-6 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) PATHWORKS Advanced Server requires all clients to be appropriately licensed to access resources on the server. See Section 2.1.8.1 for more information about setting up client-based licensing. For additional information about PATHWORKS licensing, refer to the DIGITAL PATHWORKS for OpenVMS Guide to Managing DIGITAL PATHWORKS Licenses. 2.1.8.1 License Enforcement PATHWORKS Advanced Server requires that clients accessing server resources be appropriately licensed. To conform to this requirement, one of the following must be true: o The client must have acquired a client-based license before connecting to a PATHWORKS Advanced Server. o The PATHWORKS Advanced Server must have a server-based license available to assign to an unlicensed client attempting to use services of the PATHWORKS Advanced Server. In both cases, the license required to access PATHWORKS Advanced Server services is the PATHWORKS Client-Access license: PWLMXXXCA06.00. This license can be used as either a client-based license or a server-based license. For more information, refer to Section 3.6. Clients currently using client-based licenses to access PATHWORKS LAN Manager servers must upgrade their licenses to access PATHWORKS Advanced Server resources. 2.1.9 External Authentication Support OpenVMS Version 7.1 includes support for external authentication. This feature allows the OpenVMS system manager to set up a user account for which login authentication is based on a security mechanism other than OpenVMS security. PATHWORKS Advanced Server software takes advantage of this feature by providing the ability to use the PATHWORKS Advanced Server or Windows NT-compatible user authentication mechanism to authenticate OpenVMS user logons. This allows users to log in at the OpenVMS login prompt using the PATHWORKS Advanced Server user name and Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-7 password. In addition, it provides automatic password synchronization for user accounts. For more information about implementing external authentication, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. See Section 3.2 in these Release Notes for additional details. 2.2 Differences Between PATHWORKS V5 for OpenVMS (LAN Manager) and PATHWORKS V6 for OpenVMS (Advanced Server) This section lists the general differences between the PATHWORKS Advanced Server product and the PATHWORKS LAN Manager product. o The PATHWORKS Advanced Server Administrator user account is similar to the PATHWORKS LAN Manager ADMIN user account. The Administrator user account is created automatically when you install and configure PATHWORKS Advanced Server. o The PATHWORKS LAN Manager server provides a single operator privilege level. The PATHWORKS Advanced Server provides several Operator groups. To designate a user account to be an operator, add the user account to one of the following PATHWORKS Advanced Server Operator groups: - Server Operator group (similar to LAN Manager Operator) - Print Operator group (similar to LAN Manager Operator) - Account Operator group (differs from the LAN Manager Operator in that members of this group cannot modify the Administrator user account or the Administrator or Server Operator group). o PATHWORKS Advanced Server supports domain trust relationships. This allows users to access resources in another domain without having an account there. The trust relationships must be established by administrators in both domains. 2-8 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) o PATHWORKS Advanced Server users are members of local groups and global groups. PATHWORKS LAN Manager users are members of global groups only. Local groups are used in the PATHWORKS Advanced Server to allow users from trusted domains to access resources in the local domain. o The PATHWORKS license management software and licensing subsystem have been improved in PATHWORKS V6 for OpenVMS. For more information, refer to Section 3.6.4. o PATHWORKS Advanced Server supports the same transports as does the PATHWORKS LAN Manager server, but selects them in a different order (refer to Section 2.1.5). Of course, there are many more differences between the PATHWORKS LAN Manager server software and the PATHWORKS Advanced Server software. Refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for information about upgrading from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS V6.0 for OpenVMS (Advanced Server). 2.3 Unsupported PATHWORKS V5 for OpenVMS (LAN Manager) Features The following features of PATHWORKS Version 5 for OpenVMS (LAN Manager) are not supported with PATHWORKS Advanced Server: o Share-Level Security PATHWORKS Advanced Server does not support share-level security. It manages access to all resources through user-level security. Therefore, share passwords are not required under PATHWORKS Advanced Server. User accounts are granted access to resources based on their user account information and group membership. o Member and Standalone Server Domain Roles PATHWORKS Advanced Server does not support the following domain roles: - Member server - Standalone server Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-9 A PATHWORKS Advanced Server must be either a primary domain controller or a backup domain controller in a Windows NT or Advanced Server domain. o FAT Volumes The FAT (File Access Table) file system is not supported by the PATHWORKS Advanced Server. To continue to provide FAT file access to clients, maintain the PATHWORKS V5 for OpenVMS (LAN Manager) server on a separate system. o Backward Compatibility The PATHWORKS for OpenVMS software does not support Backward Compatibility mode. This mode was used to ease the migration from PATHWORKS V4.x for VMS, to PATHWORKS V5 for OpenVMS (LAN Manager). o Net Commands The Net commands are not supported by PATHWORKS Advanced Server. They are replaced by the ADMINISTER commands. A Net command interpreter accepts and translates most Net commands to the equivalent ADMINISTER command. You can use the ADMINISTER command NET/TRANSLATE to see the ADMINISTER command that is supplied for each translated Net command. For more information about the translation of LAN Manager Net commands to PATHWORKS Advanced Server ADMINISTER commands, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Commands Reference Manual. o Remote Boot Service The PATHWORKS Advanced Server does not support the Remote Boot service. If clients depend on remote booting, you must maintain the PATHWORKS V5 for OpenVMS (LAN Manager) server on a separate system. 2-10 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 3 ________________________________________________________________ Guidelines for Using the PATHWORKS Advanced Server Software Always read the product documentation prior to using the software. This chapter describes additional guidelines for using the PATHWORKS Advanced Server software. 3.1 Server Configuration The following sections describe server configuration parameters you should modify to enhance performance in certain circumstances. 3.1.1 Configuring Physical Memory for Running Both PATHWORKS Advanced Server and the NetWare Server When you configure PATHWORKS Advanced Server on systems running both PATHWORKS Advanced Server and the NetWare server, DIGITAL recommends that you set the percent of physical memory used by PATHWORKS Advanced Server to 50 percent (or lower), rather than using the default of 80 percent. Use the Configuration Manager (ADMIN/CONFIG) to modify the physical memory allocation. 3.1.2 Allocating Sufficient Resources to Support Clients PATHWORKS Advanced Server requests the resources that it needs using the OpenVMS AUTOGEN utility. If AUTOGEN underestimates the resources required for use by processes other than PATHWORKS Advanced Server, and these resources have already been consumed when PATHWORKS Advanced Server is started, there may be insufficient resources left for PATHWORKS Advanced Server to support any clients. To ensure sufficient resource allocation to support clients, make sure that all software that will run concurrently with PATHWORKS Advanced Server is installed and started before you run the PATHWORKS Advanced Server Guidelines for Using the PATHWORKS Advanced Server Software 3-1 configuration procedure (PWRK$CONFIG.COM), especially if you run TCP/IP or PATHWORKS for OpenVMS (NetWare). After you successfully configure PATHWORKS Advanced Server, it may not start, reporting that there are insufficient resources to support any clients. In this case, examine the following file to determine the system resource that needs to be increased: PWRK$LOGS:PWRK$CONFIG_ERROR_node.LOG To increase the resource, make the appropriate modifica- tions to the MODPARAMS.DAT file and then run AUTOGEN. 3.1.3 Monitoring Data Cache Use by the File Server PATHWORKS Advanced Server uses its data cache for caching the security databases, in addition to client file data. To ensure a balance of cache usage, the file server periodically monitors its use of the data cache, as follows: o Total security databases utilization The file server monitors the total utilization of the data cache by the security databases. If the file server detects that the utilization of the data cache for these files exceeds thirty-five percent (35%), a warning message is posted to the file server log file indicating that the current cache configuration may not be adequate for the current load imposed on the file server. For example: BlobCache Warning: Sum of Blob file control areas is 950272 bytes (45% of data cache). The condition reported by this warning message will not prevent the file server from being able to properly process requests associated with the security databases. The message indicates that you should increase the size of the data cache (see below). o Individual security database utilization 3-2 Guidelines for Using the PATHWORKS Advanced Server Software The file server monitors utilization of the data cache by individual security database files. When the database expands in size, more cache resources are required to continue operating. If the file server detects that an operation will cause a database file expansion, and that expanding the database file will cause it to utilize more than fifty percent (50%) of the data cache, error messages are recorded in the file server log, as in the following example: BlobCache Error: The largest single Blob file control area is 1187840 bytes (57% of data cache). BlobCache Error: The largest single Blob file control area is PWRK$LMROOT:[LANMAN.DOMAINS]DOMAIN1. In addition to recording the problem in the file server log, the software generates an operator message and raises a server alert. These messages indicate that the operation will prevent the file server from completing the current and future operations. In this case, you should use the Configuration Manager (ADMIN/CONFIG) to increase the size of the data cache so that utilization of the data cache by a single database file remains under 50%. The change to the data cache size takes effect the next time you start the server. You can use the ADMIN/ANALYZE command to monitor these warning messages and error messages. 3.2 External Authentication Logon Information OpenVMS accepts the user name in one of the following formats for user accounts set for external authentication: o ASusername (PATHWORKS Advanced Server user name) o Domainname\ASusername o ASusername@Domainname The format of the user name string determines the order in which OpenVMS verifies the logon: o If ASusername is used, this name is first interpreted as an OpenVMS user name. If the user name exists and Guidelines for Using the PATHWORKS Advanced Server Software 3-3 that user is not set for external authentication, the authentication is done as a standard OpenVMS login. PATHWORKS Advanced Server authentication does not take place. o If the domain name is included in the user name, OpenVMS activates external authentication of the user, using the name of the domain supplied: - If the domain name is the same as that of the local server, the local server will proceed to authenticate this request. - If the domain name is different from that of the local server, the software checks the value of the HOSTMAPDOMAINS keyword in the LANMAN.INI file to verify whether the specified domain is in the list of those that the server's domain trusts. If the domain is listed there, the authentication request is forwarded to the specified domain for authentication. 3.2.1 Avoiding User Name Conflicts If you have a name space conflict, where the same user name exists in PATHWORKS Advanced Server and OpenVMS, but they are not the same user, external authentication may not work as you expect. In the following examples, you have PATHWORKS running on OpenVMS node VMS1 in the domain SaleOffice, with PATHWORKS Advanced Server users Smith and J_Smith, and OpenVMS users Smith and V_Smith. Example 1: You enable external authentication for both of the OpenVMS users, and then specify the user host mapping as follow: $ADMINISTER ADD HOSTMAP SMITH V_SMITH $ADMINISTER ADD HOSTMAP J_SMITH SMITH When OpenVMS user Smith uses his PATHWORKS Advanced Server user name J_Smith and password to logon to VMS1, this logon will be successful, providing the password is correct. 3-4 Guidelines for Using the PATHWORKS Advanced Server Software However, when OpenVMS user V_Smith uses her PATHWORKS Advanced Server user name Smith and password to logon to VMS1, this logon will fail because of the name space conflict between PATHWORKS Advanced Server and OpenVMS. To logon, OpenVMS user V_Smith must specify her PATHWORKS Advanced Server user name specifying the domain (for example, either Smith@SaleOffice or SaleOffice\Smith). Example 2: You enable external authentication only for OpenVMS user V_Smith, specifying the following command: $ ADMINISTER ADD HOSTMAP SMITH V_SMITH When OpenVMS user V_Smith uses her PATHWORKS Advanced Server user name Smith to logon to VMS1, the logon will fail, because Smith will first be interpreted as an OpenVMS user name. Because the OpenVMS user name exists, and it is not enabled for external authentication, the OpenVMS authentication mechanism is used to verify the password. To log on, the OpenVMS user V_Smith must specify the domain name with her PATHWORKS Advanced Server user name (for example, either Smith@SaleOffice or SaleOffice\Smith). 3.2.2 Setting Up External Authentication by a Trusted Domain You can set up an OpenVMS account to be externally authenticated by a trusted domain in your network. To enable this feature, you must include the trusted domain name as a value to the HOSTMAPDOMAINS keyword in the LANMAN.INI file. For example, if your OpenVMS system is in the SaleOffice domain, and this domain trusts the Marketing domain, set up OpenVMS user Jones to be externally authenticated by the Marketing domain as follows: 1. Edit the LANMAN.INI file to include the following in the VMSSERVER section: [vmserver] HOSTMAPDOMAINS = Marketing Guidelines for Using the PATHWORKS Advanced Server Software 3-5 2. Ensure that a PATHWORKS Advanced Server user account with user name Jones exists in the Marketing Domain. 3. Enable external authentication for OpenVMS user account Jones. 4. To log on, specify the user name in one of the following formats: Jones@Marketing Marketing\Jones 3.2.3 Implicit Host Mapping External authentication supports both explicit and implicit user host mapping between OpenVMS and PATHWORKS Advanced Server. You can explicitly map a PATHWORKS Advanced Server user name to an OpenVMS user name using the ADMINISTER command ADD HOSTMAP. Implicit host mapping is established when: o An OpenVMS user name matches a PATHWORKS Advanced Server user name exactly. o The PATHWORKS Advanced Server user name is one of the following: - Administrator (implicitly mapped to the SYSTEM account) - Guest (implicitly mapped to PWRK$GUEST) - PWRK$DEFAULT (used when no match is found) Host mapping is used to determine the OpenVMS user name when logging on to OpenVMS using external authentication. For external authentication, the PATHWORKS Advanced Server user account Administrator is implicitly mapped to the OpenVMS user account SYSTEM. Therefore, if you enabled the OpenVMS user account SYSTEM for external authentication, you can log in to the SYSTEM account using the PATHWORKS Advanced Server Administrator user name and password, without explicitly defining the hostmap information. 3-6 Guidelines for Using the PATHWORKS Advanced Server Software If you renamed the Administrator account, the implicit mapping is not preserved. You must explicitly map the newly renamed account name to the OpenVMS SYSTEM account using the ADMINISTER command ADD HOSTMAP. The same is true with the PATHWORKS Advanced Server user account Guest. 3.3 Netlogon Service for a Client The LANMAN.INI file on a PATHWORKS client contains the WRKNETS keyword in the WORKSTATION section. This keyword specifies the network transports that the client can use and the order in which they are used. On Enhanced Redirector clients, these network transports are represented by local area network adapter (LANA) numbers. The NET LOGON command works over LANA0 only, regardless of how many transports are loaded on the client. This may affect your ability to log on to a domain. For example, if a client runs both NetBEUI and DECnet, and WRKNETS associates NetBEUI with LANA0, NET LOGON fails if NetBEUI is not running on the server. If the domain logon fails, you can still connect to servers, but you must provide a password for each session established. To avoid this problem, run all transports on the server. Alternatively, you can change the WRKNETS parameter to load a common server-client transport on LANA0. 3.4 Administering Shares from a Windows NT Server The Windows NT Server administration tool Server Manager attempts to verify the share path locally, before passing the server operation request to the OpenVMS server. Any share path that does not conform to the device:\directory convention, where device: is a single letter drive letter, fails the share path check. Therefore, you cannot manage this type of OpenVMS share from the Windows NT Server. ________________________Note ________________________ If you are using server-based licensing, a license is consumed when you administer PATHWORKS Advanced Server from a Windows NT Server. _____________________________________________________ Guidelines for Using the PATHWORKS Advanced Server Software 3-7 The following sections describe ways to manage an OpenVMS share from the Windows NT Server. 3.4.1 Adding a Share From a Windows NT Server To add an OpenVMS share using a Windows NT Server, use one of the following procedures: Procedure 1: Define the OpenVMS device using the AUTOSHARE keyword in the VMSSERVER section of the LANMAN.INI file. This keyword allows you to map the OpenVMS device to a single letter DOS device. When a device is defined as an autoshare this way, you can add the share using the Windows NT Server by specifying the share path as device:\directory, where device is the mapped device letter. For example, to share the directory DUA1:[SHARE1] using the device letter d, include the following in the LANMAN.INI file: [VMSSERVER] AUTOSHARE= DUA1=D To add this share using the Windows NT Server Manager, specify the share path as follows: d:\share1 Procedure 2: Convert the share path input string from the OpenVMS directory path by adding C:\ to the beginning of the path specification, and instead of specifing device:[share], enter a backslash (\). For example, if the OpenVMS directory that you want to share is DUA1:[SHARE1], specify the share path as follows: C:\dua1\share1 ________________________Note ________________________ If you intend to use the default C: device, which is defined as PWRK$LMROOT:[000000], add the share using the following path name: 3-8 Guidelines for Using the PATHWORKS Advanced Server Software C:\share1 PATHWORKS Advanced Server is designed to interpret C: correctly. In this case, the actual OpenVMS specification is PWRK$LMROOT:[SHARE1]. _____________________________________________________ 3.4.2 Enumerating Shares or Modifying Shares From a Windows NT Server To enumerate or modify the OpenVMS share from a Windows NT Server, use the following share path: c:\vmsdevicename\directorypath For example, if you added a share using the ADMINISTER command ADD SHARE, and you specified $1$DUA2:[SHARE.LEVEL2] as the share path for share LEVEL2, when enumerating this share from the Windows NT Server Manager, the share path is displayed in the following format: C:\$1$DUA2\SHARE\LEVEL2 3.5 Removing PATHWORKS Advanced Server ACEs From a File PATHWORKS Advanced Server supplies an unsupported utility, PWRK$DELETEACE.EXE, which is used to remove PATHWORKS ACEs (Access Control Entries) from any file on OpenVMS. Please note that removing PATHWORKS ACEs will alter the DOS attributes and security settings of a file. To remove the PATHWORKS ACE from a file, use the following command and respond to the prompts appropriately: $ MCR PWRK$DELETEACE 3.6 Managing Licenses and Licensing Software The following sections describe the way to allocate licenses for server-based and client-based licensing, as well as management guidelines for the license server, which is used to allocate licenses. Guidelines for Using the PATHWORKS Advanced Server Software 3-9 3.6.1 Server-Based Licensing To configure your PATHWORKS for OpenVMS system to use only server-based licenses: 1. Acquire a PWLMXXXCA06.00 license PAK. 2. Register and load the PWLMXXXCA06.00 license PAK on the system where you plan to install the PATHWORKS Advanced Server software. 3. Install the PATHWORKS Advanced Server software. 4. When you run the initial configuration procedure (PWRK$CONFIG.COM), do not configure PATHWORKS to run the PATHWORKS license server. When the PATHWORKS license server is not configured on your system, the PATHWORKS Advanced Server assumes that any PWLMXXXCA06.00 licenses found on the system are to be used as server-based licenses for licensing client access. 3.6.2 Client-Based Licensing If you decide to configure the system to run the PATHWORKS license server, all PWLMXXXCA06.00 licenses on the system are by default allocated as client-based licenses. You have the option of configuring the license server to share the available PWLMXXXCA06.00 licenses, allocating some as server-based licenses. The remaining licenses can be allocated as client-based licenses. 1. Configure your system to run the license server when you run the initial configuration procedure (PWRK$CONFIG.COM). 2. Start the PATHWORKS Advanced Server to start the license server. 3. Invoke the new License Manager user interface using the following command: $ ADMINISTER/LICENSE 4. Go to the "Product allocation for group Server-Based" screen as follows: a. From the Products screen, choose View- > Groups. b. Select the predefined license group "Server-Based." 3-10 Guidelines for Using the PATHWORKS Advanced Server Software c. Choose Actions- > Modify to go to the "Product allocation for group Server-Based" screen. 5. Allocate the number of PWLMXXXCA06.00 licenses you want to use as server-based licenses to the Server-Based group. This reserves the specified number of licenses for use by the PATHWORKS Advanced Server as server- based licenses. The number you have allocated to the Server-Based license group will not be available as client-based licenses. 3.6.3 Upgrading Client-Based Licenses If client-based licensing is being used, you can configure the license server to automatically upgrade and assign PWLMXXXCA06.00 client-based licenses to clients requesting or verifying a license that is valid for accessing PATHWORKS Version 5 file and print services. To enable this feature, define the following system logical before you start the PATHWORKS server: $ DEFINE/SYSTEM PWRK$LS_V6_ACCESS_UPGRADE 1 ________________________Note ________________________ The PWLMXXXCA06.00 license is recognized by PATHWORKS Version 5.0F for OpenVMS (LAN Manager) servers and later versions of Version 5. Clients presenting this license to an earlier version of PATHWORKS for OpenVMS (LAN Manager) will be denied access. _____________________________________________________ For more information, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. 3.6.4 License Server Information The following sections provide license server management information that is not documented in the DIGITAL PATHWORKS for OpenVMS Guide to Managing DIGITAL PATHWORKS Licenses and the other PATHWORKS for OpenVMS documenta- tion. Guidelines for Using the PATHWORKS Advanced Server Software 3-11 3.6.5 License Server Startup and Shutdown PATHWORKS for OpenVMS supports running both the PATHWORKS Advanced Server and the NetWare server. The PATHWORKS license server can provide license verification for both PATHWORKS Advanced Server and NetWare clients. The PATHWORKS Advanced Server clients can connect to the file server using any of the following types of transports: o DECnet o TCP/IP o NetBEUI NetWare clients connect to the file server using the IPX transport. Because the license server supports all these types of transports, the startup and shutdown procedures have been carefully designed to prevent unexpected interruptions in service. The license server is started up and shut down using the file server command procedures. The integrated PATHWORKS license server runs with the file servers. For information about integrated license server startup and shutdown, refer to Section 3.6.5.1. The standalone license server is installed on a system without the file servers. For information about the standalone license server, refer to Section 3.6.5.5. For more information about the installation and config- uration of file servers and the license server, refer to the DIGITAL PATHWORKS for OpenVMS Installation and Configuration Guide. For more information about the PATHWORKS license server and using the License Manager, refer to the DIGITAL PATHWORKS for OpenVMS Guide to Managing DIGITAL PATHWORKS Licenses. 3-12 Guidelines for Using the PATHWORKS Advanced Server Software 3.6.5.1 Integrated License Server Startup The integrated license server runs with one or both of the file servers, if it was included in the configuration with the appropriate configuration procedure. The license server is started by the same command procedures that start the file servers. PWRK$STARTUP.COM Starts the PATHWORKS Advanced Server file server and license server components PWVN$STARTUP.COM Starts the NetWare file server and license server components The following table shows how the two startup command procedures differ: __________________________________________________________ If the Command following is Then the following is Procedure________configured_______started_________________ PWRK$STARTUP.COM DECnet DECnet transport NetBEUI NetBEUI transport TCP/IP TCP/IP transport license server IPX tunnel and IPX DECnet DECnet transport for PATHWORKS mail notification license server license server component and License Registrar component PWVN$STARTUP.COM IPX IPX transport and IPX tunnel license server DECnet transport and DECnet license server NetBEUI transport and NetBEUI license server TCP/IP transport _________________and_TCP/IP_______________________________ Guidelines for Using the PATHWORKS Advanced Server Software 3-13 3.6.5.2 Integrated License Server Shutdown To shut down the license server, use the same command procedures that shut down the file servers. The shutdown command procedures are: PWRK$SHUTDOWN.COM Shuts down PATHWORKS Advanced Server and license server components PWVN$SHUTDOWN.COM Shuts down the NetWare file server and license server components Both procedures shut down the license server, license registrar and all the PATHWORKS transports, including IPX and the IPX tunnel. 3.6.5.3 Joint PATHWORKS Advanced Server and NetWare Startup When both PATHWORKS Advanced Server and the NetWare server are installed, and the integrated license server is configured, run both PWRK$STARTUP.COM and PWVN$STARTUP.COM. These command procedures cannot run at the same time. One must complete before the other can run. If the license server, license registrar, or any of the PATHWORKS transports are already running, those processes are not started. 3.6.5.4 Joint PATHWORKS Advanced Server and NetWare Shutdown If you use both PWRK$STARTUP.COM and PWVN$STARTUP.COM to start the servers, then use both procedures to shut down the file servers and license server. In this type of configuration, the following components are shut down only when you run both shutdown procedures: o License server o License Registrar o All the PATHWORKS transports When both shutdown procedures are executed, the second procedure to execute shuts down the license server, License Registrar, and all PATHWORKS for OpenVMS transports, including IPX and the IPX tunnel. 3-14 Guidelines for Using the PATHWORKS Advanced Server Software 3.6.5.5 Standalone License Server Startup and Shutdown The standalone license server runs on a system without the file servers. However, the transports are configured for supporting license services to the appropriate clients. Therefore, the standalone license server startup and shutdown is similar to that described for the integrated license server (Sections 3.6.5.1 and 3.6.5.2). Either PWRK$STARTUP.COM or PWVN$STARTUP.COM will start the license server and the transports it requires, but you should run both PWRK$STARTUP.COM and PWVN$STARTUP.COM if the license server serves both PATHWORKS Advanced Server and NetWare clients. Similarly, you should run both PWRK$SHUTDOWN.COM and PWVN$SHUTDOWN.COM when shutting down the license server if the license server serves both PATHWORKS Advanced Server and NetWare clients. 3.6.6 License Server Configuration Parameters When PATHWORKS Advanced Server is started, the license server and the License Registrar are started using the following command procedures: o SYS$STARTUP:PWRK$LICENSE_S_START.COM o SYS$STARTUP:PWRK$LICENSE_R_START.COM These command procedures contain complete descriptions of the configuration parameters used by each process when it runs. 3.6.7 Determining Configuration Parameter Values As part of their startup sequence and announcement, the license server and License Registrar place tables of their configuration parameters in their respective log files related to license processing: o PWRK$LOGS:PWRK$LICENSE_SERVER_servername.LOG o PWRK$LOGS:PWRK$LICENSE_REGISTRAR_nodename.LOG For each parameter in the table, the following information is recorded: o Parameter name Guidelines for Using the PATHWORKS Advanced Server Software 3-15 o Parameter type o Whether the parameter is dynamic o The current value being used o Whether that value is the default value for the parameter 3.6.8 Dynamic Configuration Parameters Dynamic configuration parameters allow the value of the parameter to be changed using a system logical, without having to restart PATHWORKS Advanced Server. The license component that uses the parameter obtains the changed value while the component is running. When the value of a dynamic configuration parameter is changed by redefining the control logical associated with the configuration parameter, the change may not take effect immediately. The license components periodically check the values of their dynamic configuration parameters to see if the value of any parameter has changed. When the license component detects a change to the value of a dynamic configuration parameter, a message is recorded in the component's log file when the new value is put into use. By default, the components check the parameter values every ten minutes. 3.6.9 Controlling License Registrar Logging The License Registrar provided with PATHWORKS Advanced Server provides extra control of the messages recorded in its log file. Under PATHWORKS V5 for OpenVMS, the License Registrar provides two options: normal logging and verbose logging. This is controlled by the PWRK$LRLOGVERBOSE parameter. PATHWORKS V6.0 for OpenVMS (Advanced Server), ECO2 provides four additional logging control parameters that control the logging of different types of activity: o PWRK$LR_LOG_SERVERBASED_ACTIVITY o PWRK$LR_LOG_CLIENTBASED_ACTIVITY o PWRK$LR_LOG_CLIENTBASED_SUCCESSES 3-16 Guidelines for Using the PATHWORKS Advanced Server Software o PWRK$LR_LOG_CLIENTBASED_FAILURES These parameters are described in the License Registrar startup command procedure, SYS$STARTUP:PWRK$LICENSE_R_ START.COM. All License Registrar logging control parameters are dynamic configuration parameters, so that you can change the License Registrar's logging behavior without restarting PATHWORKS. 3.6.10 License Registrar Messages The License Registrar provides diagnostic messages in the License Registrar log file when a license presented to the License Registrar by a client is not appropriate for accessing the PATHWORKS Advanced Server. For example, the following message results when the License Registrar is presented with a license that is not valid for accessing the file server: 10-JUL-1997 13:18:36.00 CLIENT_LICENSE_INVALID: Client Id = 08002B29D2CC, Client Addr = "PC1234 ", Transport = NetBEUI, Product = PWXXWINAT07.00, Group = default, Reason = License Invalid for File Server The License Registrar records a message similar to the following for any license that is insufficient for accessing the PATHWORKS Advanced Server: 10-JUL-1997 13:18:36.00 CLIENT_LICENSE_INVALID: Client Id = 08002B29D2CC, Client Addr = "PC1234 ", Transport = NetBEUI, Product = PWLMDOSCC06.00, Group = default, Reason = Insuficient License for File Server After recording this message, the License Registrar checks for the availability of a server-based license for the client. If no server-based licenses are available, a message similar to the following is logged: Guidelines for Using the PATHWORKS Advanced Server Software 3-17 10-JUL-1997 13:18:36.00 CLIENT_NOT_LICENSED: Client Id = 08002B29D2CC, Client Addr = "PC1234 ", Transport = NetBEUI, Reason = No Server-Based Licenses Available These messages are controlled by the License Registrar's logging-related configuration parameters. Read the License Registrar's startup commmand procedure, SYS$STARTUP:PWRK$LICENSE_ R_START.COM, for more information about these parameters. 3.6.11 Setting the PWRK$LICENSE_SERVER_INHIBIT Parameter The way the PATHWORKS Advanced Server license server interprets the value associated with the PWRK$LICENSE_ SERVER_INHIBIT configuration parameter is different from the way PATHWORKS V5 for OpenVMS interprets it. Under PATHWORKS V5 for OpenVMS, a value of zero for this parameter indicates that the license server will be prevented from running on the local node. With PATHWORKS V6.0 for OpenVMS (Advanced Server), ECO2, the configuration parameter value is interpreted as follows: o A value of one means TRUE, which prevents the license server from running o A value of zero means FALSE, which allows the license server to run When you upgrade from PATHWORKS V5 for OpenVMS to PATHWORKS V6.0 for OpenVMS (Advanced Server), ECO2, and you use the PWRK$LICENSE_SERVER_INHIBIT configuration pa- rameter, change the value of the PWRK$LICENSE_SERVER_INHIBIT parameter, or use the PWRK$LS_LICENSE_NODES license server configuration parameter instead. For more information about configuring the license server, refer to the DIGITAL PATHWORKS for OpenVMS Guide to Managing DIGITAL PATHWORKS Licenses. 3-18 Guidelines for Using the PATHWORKS Advanced Server Software 3.7 Defining Communications Devices This section describes how to add new communications devices that are not automatically recognized by the PATHWORKS Advanced Server, as well as restrictions and limitations on communications devices. The PWRK$KNBDAEMON, NETBIOS, and PWRK$NBDAEMON processes require the communications device to be defined in an internal device table. New communications devices can be released before updated PATHWORKS images are available to customers. Therefore, this section describes how to define the communications device you want the PATHWORKS server to use. If the communications device is not recognized by PATHWORKS Advanced Server, each failing process writes an error message to its log file. The following table shows each process, the log file that records the error message from the process, and examples of the text of the error message. In the following examples, the server node name is MYNODE. Table_3-1_Undefined_Device_Messages_____________________________ Process__________Log_File_Name__________________________________ PWRK$KNBDAEMON PWRK$LOGS:PWRK$KNBDAEMON_MYNODE.LOG Message: Tue May 31 13:13:50 1997 get_phys_addr: Failed to get Ethernet device_characteristics__________________________________________ PWRK$NBDAEMON PWRK$LOGS:PWRK$NBDAEMON_MYNODE.LOG Message: Tue_May_31_13:13:50_1997_Failed_to_open_datalink________________ NETBIOS PWRK$LOGS:NETBIOS_MYNODE.LOG (continued on next page) Guidelines for Using the PATHWORKS Advanced Server Software 3-19 Table_3-1_(Cont.)_Undefined_Device_Messages_____________________ Process__________Log_File_Name__________________________________ Message: %NB-W-ERRSIGNAL, exceptional conditional detected at 31-May- 1997 13:13:50.00 -SYSTEM-W-NOSUCHDEV,_no_such_device_available___________________ The device tables include all known communications devices. However, if you are running the latest release and you find any of the messages listed in Table 3-1, you can explicitly specify the communications device for all three processes, using the following procedure: 1. Define the physical communications device type for the PWRK$KNBDAEMON, NETBIOS, and PWRK$NBDAEMON processes. For example, if EWA0 was an unknown physical communications device type, you would enter the following commands: $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE EWA0: $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0: $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE EWA0: 2. Restart the server: $ @SYS$STARTUP:PWRK$STARTUP 3.8 Using TCP/IP Products With PATHWORKS Advanced Server PATHWORKS Advanced Server provides transparent support for the following TCP/IP network transport products: o DIGITAL TCP/IP Services for OpenVMS, Version 4.1 o MultiNet Version 4.0, Rev. B o TCPWare for OpenVMS, Version 5.1 To use PATHWORKS Advanced Server with TCP/IP, do the following: 1. Install and, if necessary, configure the TCP/IP product. 3-20 Guidelines for Using the PATHWORKS Advanced Server Software 2. Start the TCP/IP transport and the PATHWORKS IP driver. The procedure depends on which TCP/IP product you use: o For MultiNet V4.0, enter the following OpenVMS commands, or add them to the system startup procedure: $ @SYS$SPECIFIC:[MULTINET]START_MULTINET This starts the MultiNet TCP/IP transport and loads the PATHWORKS IP driver. o For DIGITAL TCP/IP Services for OpenVMS, enter the following OpenVMS command, or add it to the system startup procedure: $ @SYS$STARTUP:UCX$STARTUP $ @SYS$STARTUP:UCX$PWIP_STARTUP For more information, refer to the documentation that comes with your TCP/IP product. 3. Start the PATHWORKS Advanced Server. Enter the following OpenVMS command, or add it to the system startup procedure: $ @SYS$STARTUP:PWRK$STARTUP 3.9 Time Zone Setup PATHWORKS Advanced Server's internal time management uses Greenwich Mean Time (GMT). To properly represent the time in your local environment, the time zone information must be set up before the server is started. To set the time zone on your OpenVMS system, execute the following command procedure: @ SYS$MANAGER:UTC$TIMEZONE_SETUP.COM To set up the time zone differential factor for your OpenVMS system, execute the following command procedure: @ SYS$MANAGER:UTC$CONFIGURE_TDF.COM If you change any time zone information, such as the daylight savings time setting, you must restart the server for the time to be properly represented. Guidelines for Using the PATHWORKS Advanced Server Software 3-21 4 ________________________________________________________________ Problems Corrected in ECO2 This section lists software changes made in the PATHWORKS V6.0 for OpenVMS (Advanced Server), ECO2 software to correct problems found in PATHWORKS V6.0 for OpenVMS (Advanced Server). 4.1 Windows 95 Cannot Enumerate All Shares on the Server Problem: If a Windows 95 PC browses the PATHWORKS Advanced Server using the Explorer or NET VIEW \\server, it may get an incomplete listing of the shares. The same problem is exhibited using a DOS PC with PATHWORKS for DOS V6.0 and the enhanced Redirector. This problem occurs because the return buffer is not of sufficient size to contain all the information needed to be returned to the client. Solution: This is resolved in ECO2. When this situation is encountered, the server removes the comment information for these shares from the return buffer in order to accommodate the total share name information. 4.2 Unable to Complete PWRK$CONFIG After Upgrade Problem: When the Upgrade utility creates the SAM database, the resulting database file is not accessable by the configuration utility. As a result, PWRK$CONFIG fails. Solution: This problem is resolved in ECO2. Problems Corrected in ECO2 4-1 4.3 MS ACCESS Unable to Open a File Read/Write Problem: Using MS ACCESS 97 on Windows 95, if the user opens a database file on a PATHWORKS Advanced Server share, the user gets the following message: The database "name" is read-only. Solution: This is resolved in ECO2. 4.4 Fatal Exception Results on Windows 95 Explorer Problem: Using Windows 95 Explorer, when selecting a folder with a long file name, the following error occurs: A fatal exception 0E has occurred at 0028:C0231810 in VXD VMM (0D) + 00001810. Solution: This problem is resolved in ECO2 4.5 Unable to Log On to Any Domain on a Different Subnet Problem: When issuing a logon request to another domain where the other domain controller is located on a different TCP/IP subnet, PATHWORKS Advanced Server fails to locate the Primary Domain Controller. Solution: This problem is resolved in ECO2. 4.6 ADMINISTER Command Hangs Problem: To execute the ADMINISTER command without first logging on to the network, the OpenVMS process must have SYSPRV, OPER, and SYSLCK privileges enabled. If the process has only the SYSPRV and OPER privileges enabled, the ADMINISTER command hangs. When you enter Ctrl/Y, the 4-2 Problems Corrected in ECO2 software returns the command prompt. This causes the following side-effects: o The NetLogon service hangs, failing to authenticate user logons. o The ADMINISTER command line interface hangs. Solution: This problem is resolved in ECO2. 4.7 TCP/IP Stops Responding to Requests Problem: A timing problem in the TCP/IP communication path causes the file server to become unable to communicate with clients using the TCP/IP transport. Solution: This problem is resolved in ECO2. 4.8 XCOPY From MS-DOS Command Fails to Create Subdirectory Problem: When a client running Windows NT V4.0 executes the XCOPY command with the /s option in the MS-DOS command window, and the destination is a PATHWORKS Advanced Server, the command fails to create the associated subdirectory. Solution: This problem is resolved in ECO2. 4.9 File Server Crashes When Enumerating Open Files Problem: Under some conditions, the file server will crash when responding to a request to enumerate all open files in the server. Solution: This problem is resolved in ECO2. Problems Corrected in ECO2 4-3 4.10 Incorrect Error Status Returned Problem: The file server returns an error code of "access denied" when responding to a directory create command, if the directory already exists. This is not the correct error code. The correct error code is "file already exists." If auditing is enabled, this error condition causes an unnecessary and incorrect audit trail of NET3004 errors. Solution: This problem is resolved in ECO2. 4.11 Server Cannot Validate Connection Requests in a Trust Problem: When running in a OpenVMS cluster, the file server fails to authenticate a trust connect. This occurs because the inactive NetLogon server in the cluster fails to process the request. Solution: This problem is resolved in ECO2. 4.12 File Server Becomes 100% CPU-Bound When Validating Connection Requests Problem: There is a timing problem in the file server while authenticating a trust connect. When this problem occurs, the server process consumes 100% of the CPU resources and fails to respond to other activities. Solution: This problem is resolved in ECO2. 4-4 Problems Corrected in ECO2 4.13 Windows 95 and Windows NT Clients Time Out When Copying Large Files to the PATHWORKS Advanced Server Problem: When a Windows 95 or Windows NT client attempts to create a large file on PATHWORKS Advanced Server by copying it from the client to the server, the client times out the operation before the file server's create operation is complete. The client reports a failure status of "network resource no longer available." This problem occurs because the file server is waiting for the disk device to complete creation of the large target file. After a timeout occurs, the client may be able to see the target file on the file server; however if the client attempts to access the target file while the file server is still creating the file, the client is denied access. DOS and Windows clients do not experience this session timeout problem when copying large files. Solution: This problem is resolved in ECO2. 4.14 Nonpaged Pool Leak When Running With TCP/IP Services for OpenVMS V4.1, ECO6 Problem: TCP/IP Services for OpenVMS versions prior to V4.1, ECO6, exhibit a nonpaged pool leak when running with PATHWORKS Advanced Server. Solution: The previous version of these Release Notes (PATHWORKS V6.0 for OpenVMS (Advanced Server)) indicated that this problem is resolved in TCP/IP Services for OpenVMS V4.1, ECO6. This is incorrect. The resolution to this memory leak problem has not been released in any available ECOs for TCP/IP Services for OpenVMS product. Contact your Digital support representative to obtain the patch for this problem. Problems Corrected in ECO2 4-5 4.15 File Modification Date Is Not Preserved When the File Is Copied From a Workstation Problem: The file server fails to preserve the modification date of a file during the copy operation; instead, it uses the current date and time as the modification date. Solution: This problem is resolved in ECO2. 4.16 Upgrade Utility Fails to Translate User Logon Hours Using GMT Problem: If a user account is set up to have logon hours restric- tions, the Upgrade utility incorrectly translates these logon hours restrictions using Eastern Standard Time (EST) rather than Greenwich Mean Time (GMT). Solution: This problem is resolved in ECO2. 4.17 License Server Crashes at Restart Problem: If the license PAK for the Client Access license (PWLMXXXCA06.00) is removed using the License Management Facility (LMF) while the license server is shutting down, the license server will crash when restarted. Solution: This problem is resolved in ECO2. 4.18 Loss of Server-Based License Units Problem: If the license PAK for the Client Access license (PWLMXXXCA06.00) is removed while some of its license units are in use by the Server-Based license group, those units will not be recovered. Solution: 4-6 Problems Corrected in ECO2 This problem is resolved in ECO2. 4.19 Memory Leak in Print Function Problem: When there is no information to be retrieved on a print queue, the server fails to return allocated memory resources, causing a memory leak in the file server process. The file server eventually crashes with an %EXQUOTA error. Solution: This problem is resolved in ECO2. 4.20 Unable to Print to OpenVMS V6.2 Print Queue Problem: If you are running PATHWORKS Advanced Server in an OpenVMS cluster with members running different versions of OpenVMS, you will be unable to print to a print queues on a member running OpenVMS V6.2. PATHWORKS Advanced Server uses print switches that are not supported by the OpenVMS V6.2 print queue manager. As a result, the submission of the print job fails. When this problem is encountered, the PC receives no error, but the print job is not submitted. The ADMIN /ANALYZE Event log file contains the following error message: ================= EVENT #32758 ================== Event Time: 17-DEC-1997 23:55:49.56 Node: DSSHW1 Process Id: 28C00185 Event: Unexpected System Error Encountered Event Source: Print Services (PPS) Event Class: Error Status: %JBC-F-INVITMCOD, invalid item code or option code Text: submit (2) Solution: This problem is resolved in ECO2. Problems Corrected in ECO2 4-7 4.21 Memory Leak in PWRK$LMDMN Process Problem: A small memory leak occurs in the PWRK$LMDMN process when it is processing account information. Solution: This problem is resolved in ECO2. 4.22 Session Limit Is Incorrectly Set to 99 Problem: The file server incorrectly uses an obsolete LANMAN.INI parameter (maxvcperproc) and sets the total sessions limit to the default of 99. This limitation prevents connections from the 100th client regardless of the number of clients that the server is configured to support. Solution: This problem is resolved in ECO2. As a result of this correction, the maxvcperproc parameter will no longer have any effect on the file server. 4.23 Unable to Access File Name That Has a Period at Position 40 Problem: The server fails to locate a PATHWORKS encoded file name with a period in position 40. The client will not be able to see these files. Solution: This problem is resolved in ECO2. 4.24 PWVER Command Displays an Obsolete Image Problem: PATHWORKS Advanced Server displays old image data when you run it on a system that has been upgraded from PATHWORKS V5 for OpenVMS (LAN Manager). The PWRK$VERSIONS.COM command procedure displays the following obsolete image: PWRK$STREAMSOS_V6.EXE. The procedure displays an error 4-8 Problems Corrected in ECO2 when you run it on a system that did not have PATHWORKS V5 for OpenVMS (LAN Manager) installed previously. Solution: This problem is resolved in ECO2. 4.25 PWRK$DELETEACE Is Not Accessible After Rollback or Deinstallation Problem: As part of the deinstallation of PATHWORKS Advanced Server, or with rollback to PATHWORKS V5 for OpenVMS (LAN Manager), the PWRK$DELETEACE.EXE utility is removed from the system. However, the PWRK$DELETEACE utility is required in order to remove PATHWORKS Advanced Server Access Control Entries (ACEs) that may have been added to files on the disk. Solution: This problem is resolved in ECO2. The PWRK$DELETEACE utility is not removed when you deinstall or roll back from PATHWORKS Advanced Server. Problems Corrected in ECO2 4-9 5 ________________________________________________________________ Known Problems in PATHWORKS for OpenVMS (Advanced Server) The following sections describe known problems in PATHWORKS for OpenVMS and their solutions. 5.1 Domain Management Problems The following section describes problems in managing domains and servers in domains. 5.1.1 A Computer Cannot Be Removed From the Domain If It Has Been Promoted to Be a PDC in Another Domain Problem: If you reconfigure a Backup Domain Controller (BDC) from one domain to become a Primary Domain Controller (PDC) of another domain, you cannot remove the computer name from the original domain. Solution: Delete the computer name in the original domain database during scheduled down time of the new PDC. 5.2 User Interface Problems The following sections describe problems in the ADMINISTER command line interface. 5.2.1 SET PASSWORD Command Does Not Always Set the Password Correctly Problem: If you use the ADMINISTER command SET PASSWORD to set a password to lowercase letters, and the primary domain controller is a Windows NT Server, the command will complete successfully but the password will not be set correctly. Known Problems in PATHWORKS for OpenVMS (Advanced Server) 5-1 Solution: Change the password from a client workstation, as follows: o From a Windows NT system, press the Ctrl + Alt + Delete key sequence and select the Change Password option. o From a Windows 95 system, select Passwords from the Control Panel. 5.2.2 The /TYPE=NO* Qualifier Does Not Function with the ADMINISTER Command SHOW CONNECTIONS Problem: The ADMINISTER command SHOW CONNECTIONS supports the use of NO as a prefix to a value for the /TYPE qualifier. But this prefix is not properly implemented. Solution: Specify the type of connections you want to display, instead of using the /TYPE=NOconnection_type qualifier to filter out connections you do not want to display. 5.2.3 Unable to Change an Expired Password When Using the ADMINISTER Command LOGON Problem: You will encounter a failure if you use the ADMINISTER command LOGON to log on to the network if your account password has expired, and you are being authenticated by a BDC. Solution: Change your password from a client workstation, or retry the command. If the PDC is the authentication server, the command will execute successfully. To change the password from a Windows NT system, press the Ctrl + Alt + Delete key sequence and select the Change Password option. From a Windows 95 system, select Passwords from the Control Panel. 5-2 Known Problems in PATHWORKS for OpenVMS (Advanced Server) 5.2.4 SEND/USERS Command Reports an Error Problem: The ADMINISTER command SEND/USERS generates an error message under the following conditions. To receive these messages, computers must support WinPopup services. o If you use the SEND/USERS command from an OpenVMS cluster to send a message to all connected users, the command successfully sends the message but the software reports an error to your cluster member. The error occurs because the software fails to recognize the cluster member node as a PATHWORKS Advanced Server, which does not support WinPopup services. o If you use the /SERVER qualifier to send a message to all connected users, the command successfully sends the message but the software reports an error to the specified server. The software fails to recognize the remote server as a PATHWORKS Advanced Server, which does not support WinPopup services. The following error message appears. %PWRK-E-ERRSENMSG, error sending message for computer "TINMAN_B5" -LM-E-NERR_NAMENOTFOU, the message alias could not be found on the network Solution: You can disregard the error message. 5.2.5 Misleading Error Message with ADMINISTER Commands for Managing User Account Host Mapping If you provide a user name that does not exist as a parameter to the ADD HOSTMAP, SHOW HOSTMAP, or REMOVE HOSTMAP command, you will get the following error message: -LM-E-NERR_GROUPNOTFO, the group could not be found This message should say that the user could not be found. Known Problems in PATHWORKS for OpenVMS (Advanced Server) 5-3 5.2.6 REMOVE PRINT QUEUE Command Fails to Remove the Queue If the Print Queue Is Not Stopped Problem: If you use the ADMINISTER command REMOVE PRINT QUEUE to remove a queue that is not in Stopped state, the command will fail. Solution: Stop the queue using the OpenVMS command STOP/QUEUE before you use the ADMINISTER command REMOVE PRINT QUEUE. 5.2.7 SHOW FILE Command Fails to List Subdirectories Problem: When you use the ADMINISTER command SHOW FILE with the /SUBDIRECTORY qualifier, and there is a subdirectory name that is the same as a file name without any extension, the command will fail to list the subdirectory. Solution: To list all the files and subdirectories in a share, include a wildcard file specification (*.*) after the subdirectory file specification. For example: $ ADMINISTER SHOW FILE \test\*.* /SUBDIRECTORY 5.2.8 Incorrect Count of Active Links Displayed After a Forced Disconnect Problem: If you force a disconnect on a share using the Windows NT server administration tools, the display will continue to show the old connection data even though the connection has been terminated. Solution: If you select the share, the updated data will be displayed. 5-4 Known Problems in PATHWORKS for OpenVMS (Advanced Server) 5.3 Windows NT Interoperability Problems The following sections describe problems with running PATHWORKS Advanced Server in a domain with Windows NT Server. 5.3.1 Upgrade Utility Does Not Upgrade Locked-Out Users Problem: The Upgrade utility, which is used to upgrade server information from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS V6 for OpenVMS (Advanced Server) does not upgrade users whose accounts are locked out. Solution: Ensure that no user accounts are locked out when you start the user upgrade portion of the Upgrade procedure. Refer to the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for more information. 5.3.2 Nonstandard Domain Guest Group on Windows NT Servers Causes Replication to Fail Problem: In rare situations, the Domain Guest group on a Windows NT Server may have been created in a nonstandard manner. If the Windows NT Server is the Primary Domain Controller (PDC) in a domain, a PATHWORKS Advanced Server backup domain controller (BDC) will not replicate the security databases from the PDC. The error displayed in the PATHWORKS Advanced Server event log is similar to the following: T Date Time Source Category Event User Computer - -------- ----------- --------- --------- ------ ---------- -------- E 08/20/97 01:41:02 PM NETLOGON None 5730 N/A MATATA NET5730: Replication of the SAM Global Group "Domain Guests" from primary domain controller \\PCROOM_ALIAS failed with the following error: The user cannot be removed from a group because the group is currently the user's primary group. Solution: Known Problems in PATHWORKS for OpenVMS (Advanced Server) 5-5 If this occurs, contact your DIGITAL support representa- tive for further instructions. 5.4 Host Mapping Problems The following section describes problems in setting up host mapping for PATHWORKS Advanced Server users. 5.4.1 A Host Map Setting From a Trusted Domain Cannot Be Removed After the Trust Relationship Has Been Removed Problem: If you have established a host mapping setting for a local OpenVMS user to a PATHWORKS Advanced Server user name in a trusted domain, and the trust relationship is removed before you remove the host mapping setting, the ADMINISTER command REMOVE HOSTMAP/HOST will fail because the mapped PATHWORKS Advanced Server user name is now represented by its security identifier (SID, a unique number) instead of by its alphabetical string identifier. Solution: Before you remove the trust relationship, perform one of the following procedures: o Remove all explicit host mapping to user accounts in the trusted domain. o Use the REMOVE HOSTMAP/HOST command to remove the host mappings. 5.5 File Server Problems The following sections describe problems with the file server. 5.5.1 PATHWORKS Advanced Server Fails to Properly Handle Corrupted ACEs When the file server fails unexpectedly, some security information may be corrupted. When PATHWORKS Advanced Server encounters a corrupted security ACE (access control entry), it will remove the ACE and log a message in the common service event log. As a result, these log files may not be protected. 5-6 Known Problems in PATHWORKS for OpenVMS (Advanced Server) Solution: Review the common service event log using the the ADMIN /ANALYZE command to determine whether this situation has occurred. If it has, evaluate the file protection on the file to ensure the security setting is correct. 5.5.2 Moving a Subdirectory May Not Preserve Security Settings Problem: When you move from one location to another a subdirectory that does not have explicit permissions set on it, the subdirectory's security settings are not preserved. For example, directory \OPEN has explicit security set for Everyone to have full access while directory \RESTRICTED has explicit security set for only Administrators to have full access. The subdirectory \OPEN\TEST in share \OPEN, without explicit access permissions, inherits the Everyone:Full security setting. However, if it is moved to \RESTRICTED\TEST, the Everyone Full setting will not be preserved. Instead, the subdirectory will inherit the security setting of the \RESTRICTED share. Solution: After you move a subdirectory, make sure the permission is explicitly set to the desired value. 5.5.3 PATHWORKS Advanced Server Cannot Support More Than 32,767 Shares The PATHWORKS Advanced Server will fail to add the 32768th share entry to the share database. 5.5.4 File Permissions Are Not Displayed on Initial Connect Problem: If you use a Window NT 4.0 client to connect to a PATHWORKS Advanced Server, and you select the property menu to display security information immediately after you connect, you will not see a Security tab in the Permissions dialog box. Solution: Known Problems in PATHWORKS for OpenVMS (Advanced Server) 5-7 If you double-click on the window, this information will become available to you. 5.5.5 File Server May Issue Incorrect BlobCache Warning Messages Problem: Sometimes the PATHWORKS file server will incorrectly report that the sum of the databases has exceeded the recommended maximum percentage of data cache size, indicating that the cache size should be increased, when the cache size may not need to be increased. Solution: The warning messages may be ignored if the percentage reported in the warning message does not exceed 100% and does not increase once the file server is running (that is, after server startup). Note that the solution applies only to "BlobCache Warning" messages. Do not ignore "BlobCache Error" messages. 5.6 Event Logging Problems The following sections describe problems in the event logging functions of the server. 5.6.1 SHOW EVENTS/FULL Command Fails to Display Messages with ID 6033 Problem: When you use the ADMINISTER command SHOW EVENTS/FULL, and the message number 6033 is in the event file, the software will fail to display the error message text associated with it. Solution: Use the Windows NT server administration tool Event Viewer to display the event log. 5-8 Known Problems in PATHWORKS for OpenVMS (Advanced Server) 5.6.2 Incorrect Audit Type When Password Change Failure Event Occurs The server incorrectly indicates a password change failure event as a success in the event log file. 5.6.3 Incorrect Syntax in SHOW EVENTS Backup File Causes the Server to Fail Problem: If you use the ADMINISTER command SHOW EVENTS to view a saved event file, and you incorrectly specify the file specification in DOS syntax in the form of c$:\filename.evt, the file server will crash. The $ sign after the autoshared device name is not properly handled by the server. Solution: Do not include the dollar sign ($) in the DOS device name. You can use c:\filename.evt or specify an autoshared device name that is mapped to an OpenVMS device. All valid file specification formats are handled. 5.7 Licensing Problems The following sections describe problems in the licensing software provided with PATHWORKS for OpenVMS. 5.7.1 License Manager Always Reports Zero Usage of PWLMXXXCA06.00 Licenses Allocated to the Server-Based Group Problem: The License Manager (ADMIN/LICENSE) reports zero usage for PWLMXXXCA06.00 licenses that are used as server- based licenses, even if some server-based PWLMXXXCA06.00 licenses have been assigned to clients. Solution: Use the PWLICENSE command to show the current usage and availability of PATHWORKS server-based licenses on the system. The PWLICENSE command is defined in the SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM command procedure. Known Problems in PATHWORKS for OpenVMS (Advanced Server) 5-9 The License Manager will correctly reflect the usage of PWLMXXXCA06.00 license from the Server-Based group in a future release. 5.7.2 License Registrar Interval Parameters Do Not Immediately Use New Values When a Change to the Parameter Value Is Noticed Problem: When you change the value of the License Registrar's PWRK$LR_LICENSE_REPORT_INTERVAL or PWRK$LRLMFSYNCHINTERVAL parameters, the License Registrar will not use the new value of this parameter until the time interval for checking the parameter values has passed. For example, if license reporting is initially set to generate a report every six hours, and you change that parameter value to ten minutes while the License Registrar continues to run, the License Registrar will begin to use the new interval only after the current six-hour interval has passed. When the current interval has passed, the License Registrar begins to use the new interval value. 5.8 Upgrade Problems The following sections describe problems in upgrading a server from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS for OpenVMS. 5.8.1 Rollback Fails to Delete All PATHWORKS Advanced Server Data Files Problem: If you select installation of only the PATHWORKS Upgrade utility, install PATHWORKS Advanced Server on your system later, and then execute the Rollback procedure to revert the system back to PATHWORKS LAN Manager, the Rollback utility will fail to delete the ACL. and Sharedb. data files from the PWRK$LMROOT:[LANMAN.DATAFILES] directory. This does not introduce any problem to the running PATHWORKS LAN Manager environment. However if you choose to reinstall PATHWORKS Advanced Server, you may have problems with printing security. 5-10 Known Problems in PATHWORKS for OpenVMS (Advanced Server) Solution: Delete these files before installing PATHWORKS Advanced Server again. 5.8.2 Upgrade May Fail to Start Selected Transports Problem: The following steps will cause the Upgrade utility to fail to start the selected transports: 1. Install PATHWORKS Advanced Server. 2. Run the Upgrade utility to upgrade your server as a BDC without completing the initial configuration of the server (PWRK$CONFIG). Solution: Define the following OpenVMS logical before you run the Upgrade utility: $ DEFINE/SYSTEM/EXECUTIVE/NOLOG PWRK$VERSION V6.0 5.9 Documentation Corrections The following sections provide corrections to the PATHWORKS V6 for OpenVMS manuals. 5.9.1 Corrections to the Server Administrator's Guide Problem: The following LANMAN.INI parameters are incorrectly described in the Server Administrator's Guide: o maxapplog o maxauditlog o maxerrlog The manual shows incorrect defaults and measurement units for these parameters. Also, the maxapplog parameter is said to be part of the [SERVER] section, which is incorrect. Solution: Known Problems in PATHWORKS for OpenVMS (Advanced Server) 5-11 The maxapplog parameter should be included in the [VMSSERVER] section of the LANMAN.INI file. The correct default values for these parameters are: __________________________________________________________ Parameter__________________Default________________________ maxapplog 512 Kbytes maxauditlog 512 Kbytes maxerrlog__________________512_Kbytes_____________________ To modify the values of these parameters, enter the number of bytes. For example, to set the maximum size of the application event log to 512 Kbytes (1024 blocks), include the following line in the [VMSSERVER) section of the LANMAN.INI: maxapplog = 524288 5-12 Known Problems in PATHWORKS for OpenVMS (Advanced Server) 6 ________________________________________________________________ Restrictions of PATHWORKS for OpenVMS (Advanced Server) This chapter describes restrictions in the PATHWORKS Advanced Server software. 6.1 Installation and Configuration Restrictions The following sections describe restrictions in the installation and configuration of the PATHWORKS for OpenVMS software. 6.1.1 PATHWORKS Advanced Server Cannot Coexist with PATHWORKS V5.0C for OpenVMS (LAN Manager) Server Problem: The PATHWORKS Advanced Server cannot share a domain with a server running PATHWORKS V5.0C for OpenVMS (LAN Manager). The V5.0C server incorrectly generates a name conflict when the PATHWORKS Advanced Server claims a group name that is used by both servers. Solution: To correct this problem, upgrade the PATHWORKS V5.0C server to PATHWORKS V5.0C ECO1, or a later version of PATHWORKS V5 for OpenVMS (LAN Manager). 6.1.2 OpenVMS Version 7.1 Requires a Patch If the system is running OpenVMS Version 7.1, DIGITAL's DEC C RTL patch ALPACRT02 or higher must be installed. Restrictions of PATHWORKS for OpenVMS (Advanced Server) 6-1 6.1.3 PATHWORKS Advanced Server May Fail at Startup Time If SYLOGIN.COM Executes with Errors PATHWORKS Advanced Server process startup depends on successful execution of OpenVMS logins and logouts. If your sites make use of SYLOGIN.COM to achieve cluster- member specific logon setup, and SYLOGIN.COM encounters errors, PATHWORKS Advanced Server startup hangs. When this problem occurs, process startup either fails to generate log file messages, or fails to complete. 6.1.4 PATHWORKS Advanced Server Fails to Start on Non-English Language Versions of OpenVMS The PATHWORKS Advanced Server fails to start on any non- English version of the OpenVMS operating system, because PATHWORKS Advanced Server relies on the English language output of the OpenVMS command SHOW MEMORY. 6.1.5 PWRK$CONFIG Fails to Move the PATHWORKS On-Disk Structure Problem: If the PATHWORKS on-disk structure contains directories more than eight levels deep, the PWRK$CONFIG procedure cannot move the on-disk structure to another disk because of an OpenVMS RMS restriction. Solution: Before running the PWRK$CONFIG procedure to move the PATHWORKS on-disk structure, either delete files and directories that are greater than eight levels deep, or rename them so that the standard OpenVMS BACKUP command can move them correctly. 6.2 User Interface Restrictions The following sections describe restrictions in the management interfaces. 6-2 Restrictions of PATHWORKS for OpenVMS (Advanced Server) 6.2.1 Mouse Selection Highlights Entire Screen Problem: Under certain circumstances, the entire screen is highlighted when you select a button using the mouse input device. Solution: When this occurs, press Ctrl/W to clear the screen, then select the button again. 6.2.2 Windows NT Print Manager Fails to Display PATHWORKS Advanced Server Printers Problem: When you attempt to display the printers on the PATHWORKS Advanced Server from the Windows NT server administration Print Manager, using the Server Viewer, you will not see the printers offered by the PATHWORKS Advanced Server. Solution: Display the list of printers using the PATHWORKS Advanced Server ADMINISTER command SHOW PRINTERS. 6.2.3 File Server Unable to Resolve Job Logical Translation as Part of a File Specification If you use a job logical as part of a file specification for any ADMINISTER command, the operation will fail. The file server does not support using a job logical as part of a file specification. Using a job logical as part of a file specification to an ADMINISTER command results in an error, where the error message may not be explicit about the cause of the problem. For example, the following command will fail with an "insufficient privileges" error message. $ ADMIN SAVE EVENT SYS$LOGIN:EVT_BACKUP.EVT The source of the problem, however, is not the privilege level of the user; rather, it is the use of the SYS$LOGIN job logical. Therefore, you cannot use job logicals in file specifications in the ADMINISTER command line. Restrictions of PATHWORKS for OpenVMS (Advanced Server) 6-3 6.2.4 Autoshares Are Not Enumerated by PATHWORKS Advanced Server PATHWORKS V5 for OpenVMS (LAN Manager) supports the enumeration of "autoshared" devices as part of the share enumeration displayed by the NET SHARE command. PATHWORKS for OpenVMS does not enumerate any autoshared device; however, a user with Administrator privileges can connect to these devices. 6.3 Event Logging Restrictions The following sections describe restrictions in the event logging and auditing functions of the PATHWORKS Advanced Server. 6.3.1 Event Log Files Fail to Wrap When Full Problem: The server does not support overwriting event messages when the Event log files become full. However, the server generates an Alert message indicating the log file is full. Solution: You must manually clear the event log files using the ADMINISTER command CLEAR. 6.3.2 Unable to Set the Event Logging Setting When you use Windows NT Administration tools to alter the event logging setting, and you choose the option "do not overwrite," the server incorrectly reflects the setting as "overwrite events older than 365 days." 6.3.3 Displaying Application Event Log Files The ADMINISTER command SHOW EVENTS does not display the Application event log file in detailed format. When you supply the /FULL qualifier to display the detailed event information, only the summary information is displayed. 6-4 Restrictions of PATHWORKS for OpenVMS (Advanced Server) 6.3.4 OpenVMS SET PASSWORD on an Externally Authenticated User Account Is Not Audited Problem: The password change event that results from executing the OpenVMS SET PASSWORD command from an OpenVMS account that is enabled for external authentication is not audited in the PATHWORKS Advanced Server Security event log file. However, the password change activity is audited in the OpenVMS audit file. Solution: If this capability is crucial to your environment, advise users to use the ADMINISTER command SET PASSWORD to change the password. 6.4 File Server Restrictions The following sections describe restrictions in the file server. 6.4.1 Ownership of a Directory Directory ownership is inherited from its parent directory instead of the creator of that directory, unless the creator has explicit host mapping set up on the system. PATHWORKS Advanced Server is different from Windows NT Server in this way. On a Windows NT Server, the ownership of a directory and a file are set to the user who created them. 6.4.2 DEFZA FDDI Controller Is Not Supported in PATHWORKS Advanced Server Problem: The DEFZA FDDI controller is not supported with PATHWORKS Advanced Server. Solution: Use the newer DEFTA controller, which is supported and provides better performance. Restrictions of PATHWORKS for OpenVMS (Advanced Server) 6-5 6.4.3 Premature Disk Full Conditions Problem: The file server may receive a disk full message when thousands of free blocks remain on the device, because the file server's open file cache holds newly created or extended files open for about five seconds after the client closes them. Because files are allocated in extent-size chunks, that space is unavailable for other operations until the files are actually closed. Solution: To avoid these messages, make sure that at least 1 MB of free space is available on the device or the container file at all times. If this does not work, add the following to the PWRK$COMMON:PWRK.INI file to lower the default file extent quantity. Create this file if necessary. Note, however, that this will significantly affect the performance of file uploading. [ODS2] create_quantity = 1 extend_quantity = 1 6.4.4 Server Does Not Enforce Disk Quotas by Default Problem: By default, the file server uses the EXQUOTA privilege, which means that quotas on OpenVMS system disk volumes are not enforced. Solution: To disable the EXQUOTA privilege and use disk quotas, include the following line in the [LMSRV] section of the file PWRK$COMMON:PWRK.INI. Create the section, if necessary: [LMSRV] START_WITH_EXQUOTA=NO 6-6 Restrictions of PATHWORKS for OpenVMS (Advanced Server) 6.4.5 DECram Performance Problem Problem: DECram performance is inadequate when the disk is mounted using the /NOCACHE qualifier. Solution: Do not use the /NOCACHE qualifier when mounting a RAM disk that PATHWORKS accesses. If you omit the /NOCACHE qualifier from the MOUNT command, the XQP+ cache is enabled for the RAM disk, allowing the PATHWORKS internal caches to operate effectively. 6.4.6 Access Denied to Files Restored From Backup of Another System Problem: When a directory is backed up from one system and restored on another, stale group ACEs may still be attached to the files that are restored. These ACEs cause the file server to deny access to users even though they have access to the parent directory. Solution: To correct the problem, delete the ACLs on the files after they are restored, using the following DCL command: $ SET ACL/DELETE filename 6.4.7 Intruder Flag's Relationship to PC Connections and Logons Problem: When a PC user does not provide a correct password with a logon request, the file server logs an OpenVMS intrusion record, which indicates a possible break-in attempt. Solution: The file server also sets the intruder flag. This flag may be safely ignored; it does not affect any PC connections or logons. To delete the intrusion record, use the DELETE/INTRUSION_RECORD command. Restrictions of PATHWORKS for OpenVMS (Advanced Server) 6-7 6.4.8 XCCB Not in Use Errors in LMMCP Log File Problem: When an attempt is made to exceed the maximum number of sessions that the server is configured for, the operation fails (as expected) and the following error message appears in the PWRK$LMMCP_nodename.LOG file: ...specified XCCB not in use! Solution: You can ignore this error message. 6.5 PATHWORKS Advanced Server Interaction with Oracle Rdb Problem: PATHWORKS Advanced Server fails to start correctly on systems that are also configured to run Oracle Rdb (Relational Database) software, because of the way that Rdb uses the system-wide login command procedure SYLOGIN.COM and the way that PATHWORKS Advanced Server creates processes. Solution: To correct this problem, replace the following line in the system login procedure SYLOGIN.COM: $ @DECRDB$SETVER.COM with the following lines: $ SET NOON $ @DECRDB$SETVER.COM $ SET ON 6-8 Restrictions of PATHWORKS for OpenVMS (Advanced Server)