NetWare NFS v1.20b Patch for NetWare 4.01 Release Document README.TXT Copyright (c) 1993 Novell, Inc. All Rights Reserved. THIS WORK IS SUBJECT TO U.S. AND INTERNATIONAL COPYRIGHT LAWS AND TREATIES. NO PART OF THIS WORK MAY BE USED, PRACTICED, PERFORMED, COPIED, DISTRIBUTED, REVISED, MODIFIED, TRANSLATED, ABRIDGED, CONDENSED, EXPANDED, COLLECTED, COMPILED, LINKED, RECAST, TRANSFORMED, OR ADAPTED WITHOUT THE PRIOR WRITTEN CONSENT OF NOVELL, INC. ANY USE OR EXPLOITATION OF THIS WORK WITHOUT AUTHORIZATION COULD SUBJECT THE PERPETRATOR TO CRIMINAL AND CIVIL LIABILITY. DISCLAIMER Novell, Inc. makes no representations or warranties with respect to this software patch, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Novell's intentions for this software patch is to provide a temporary work-around to the anomalies described in this file. Such work-arounds are typically addressed in future releases of NetWare. Distribution of this patch is forbidden without the express written consent of Novell, Inc. Novell reserves the right to discontinue distribution of this software patch. Novell will not be responsible for any data loss that might result from implementing this patch. Novell strongly recommends a backup be made before any patch is applied. Technical support for this patch is provided at the discretion of Novell. *************************************************************************** CAUTION *************************************************************************** ALWAYS backup your system before implementing any program/utility revision involving the low-level functions of NetWare including re-linking of operating system .OBJ files, Bindery utilities, and drive and volume operation. This document includes the following sections: PURPOSE OF THIS PATCH UPDATES TO NETWARE NFS v1.20b USING THIS PATCH WITH NETWARE 4.01 CONFIGURING THE SOFTWARE TO RUN WITH NETWARE 4.01 USING THE DIFFERENT MODES OF PCONSOLE CONFIGURING UNIX TO NETWARE PRINTING (PLPD) CONFIGURING NETWARE TO UNIX PRINTING (LPR_GWY) CONTROLLING JOBS CONFIGURING DEVICES AND FORMS USING PLPDDEF INSTALLING THE PATCH ====================== PURPOSE OF THIS PATCH ====================== This patch allows the NFS v1.20b product to run on a NetWare 4.01 server. Although this patch allows the NFS v1.20b product to run correctly on a NetWare 4.01 Server, it does not allow NFS v1.20b to take advantage of all of the new features in NetWare 4.01, such as NetWare Directory Services (NDS) and enabling. This patch also includes updates to existing problems. ============================== UPDATES TO NETWARE NFS v1.20b ============================== CREATING THE USER NOBODY -------------------------- In previous versions of NetWare NFS, the NFS server would create the group NOGROUP if it did not exist. The NFS server will now create both the group NOGROUP and the user NOBODY if either does not exist. FILES LOCKED BY DOS CLIENTS ---------------------------- In previous versions of NetWare NFS, the NFS server failed to return an error when an NFS user tried to read a file locked by a DOS client. The NFS server now returns an error to the NFS user in this case. NFS WRITE OPERATIONS TO A FILE OPENED BY A DOS CLIENT ------------------------------------------------------ In previous versions of NetWare NFS, any NFS write operation to a file that is open by a DOS client caused the DOS client to receive an access error message. This no longer happens. FILE TIME STAMPS ----------------- In previous versions of NetWare NFS, files created by UNIX clients on the 1st or 31st of the month received an invalid time stamp. These files now receive the correct time stamp. NFS WRITE OPERATIONS TO A FILE LOCKED BY A UNIX CLIENT ------------------------------------------------------ In previous versions of NetWare NFS, some NFS write operation to a file that is locked by a UNIX client may result in an access error message. This no longer happens. FTP APPEND OPERATION TO A NON-EXISTING FILE ------------------------------------------- In previous versions of NetWare NFS, the FTP operation of appending to a non-existing file resulted in an error message. Now the file is created and transferred with the append command. USING XCONSOLE --------------- In previous versions of NetWare NFS, it was possible for an XConsole user to bypass a file server lock after the console screen was locked using the MONITOR utility. The user could unlock the screen by typing , which displayed the "Select Screen" menu. From this menu the user could access the Console Screen and unload monitor NLM. This patch fixes this problem by disabling when a file server lock is set from the MONITOR utility. When an XConsole session is terminated from Host Presenter "File Menu" or from TNVT220 by switching back to the terminal and then exiting the session (q), an error message appears in the audit log. The following error message is reported in the audit log whenever a Telnet connection to XConsole is terminated without using : Xconsole-Error: :Telnetd failed writing to client, reason - an asynchronous event has occurred You should ignore this error message. USING UNIX TO NETWARE PRINTING (PLPD) -------------------------------------- In previous versions of NetWare NFS, you could not print a banner from a line printer if you selected the "None" filter option from within the PLPDCFG utility. A banner will now print in this case, unless you remove the banner using the "-J/nb" option of the LPR command. ================================== USING THIS PATCH WITH NETWARE 4.01 ================================== The following sections describe important information that you should know before using NetWare v1.20b on a NetWare 4.01 server. ================================================= CONFIGURING THE SOFTWARE TO RUN WITH NETWARE 4.01 ================================================= The Bindery Context must be set on this server for this patch to work correctly. For more information on bindery emulation and setting your bindery context, refer to the June 1993 NetWare Application Notes. You must set the Bindery Context to the position in the directory tree where the server's volumes are located. For example, if the server volumes are located in OU=Department.O=Company you would add the following lines to the AUTOEXEC.NCF file (if the lines do not already exist): SET BINDERY CONTEXT = OU=Department.O=Company Use the following procedure at the server console prompt to set the bindery context: 1. To view the server's current bindery emulation context, type SET BINDERY CONTEXT This command displays the server's current bindery emulation context. 2. If you need to change the context that displays, type SET BINDERY CONTEXT = You should also add the correct "SET BINDERY CONTEXT" line to the AUTOEXEC.NCF file. For example, SET BINDERY CONTEXT = OU=Department.O=Company ========================= USING THE GROUP EVERYONE ========================= In NetWare 4.01, the group EVERYONE is not automatically created and updated as it is in NetWare 3.11. If you upgraded from a NetWare 3.11 server, then the group EVERYONE was updated during installation. If you installed NetWare 4.01 on a clean server, and the group EVERYONE does not exist, this patch will create it. Most NetWare 4.01 utilities update the group EVERYONE, but some do not. Whenever you add a new queue, print server, or any object where the group EVERYONE is a user, you must check that all users are members of the group EVERYONE. For example, if you use the PLPD and LPR_GWY NLMs, and you set users to the group EVERYONE, it is your responsibility to make sure that all users are included in the group EVERYONE. In this case, any user trying to print that is not in the group EVERYONE will be denied queue access. ====================================== USING THE DIFFERENT MODES OF PCONSOLE ====================================== The new PCONSOLE utility has two modes of operation. When you run PCONSOLE on a NetWare 4.01 server, it starts in Directory Services mode. If you press the key from within PCONSOLE, it enters Bindery mode. When you are in Bindery mode, you can view queues, printers, and print servers created from NFSADMIN and queues created from PLPDCFG. Both NFSADMIN and PLPDCFG create bindery objects. Some bindery objects can also be accessed from the Directory Services mode, but remember that Directory Services replaces all underscores in bindery names with spaces. For example, if you create a print server named "ps_for_lab" from NFSADMIN, its name would appear as "ps for lab" from within PCONSOLE. The key allows you to switch between the two modes of operation (Bindery mode and Directory Services mode). Before you use the Bindery mode you must be logged into the current server as a user in the Bindery Context. IMPORTANT: Admin can only use Bindery mode if Admin is in the current Bindery context. ============================================ CONFIGURING UNIX TO NetWare PRINTING (PLPD) ============================================ You use the NetWare 4.01 PCONSOLE utility and the PLPDCFG.NLM to configure UNIX to NetWare printing. You use PCONSOLE to create and associate queues, printers, and print servers and the PLPDCFG to select queues for use by UNIX printing, trusted hosts, and user account mapping. The following sections describe the configuration procedure. IMPORTANT: You also have the ability to create queues using the PLPDCFG NLM, but Novell strongly suggests that you do not create queues using this method. If you create a queue using PLPDCFG, the queue will provide UNIX to NetWare printing, but your ability to control and view jobs through PCONSOLE will be limited. CONFIGURING USING PCONSOLE --------------------------- The following configuration can be done from either mode of PCONSOLE. 1. From a NetWare 4.01 client, log into the NetWare 4.01 Directory and run the PCONSOLE utility. 2. Create queues, printers, and print servers from within PCONSOLE. Remember that you need to associate each queue with a printer, and then specify which printers are serviced by each print queue. The NetWare 4.01 Print Services Manual describes how to use the new PCONSOLE utility in detail. >From within the "Queue Information" and "Print Server Information" menus, the administrator also needs to specify users for the queues and print servers used by PLPD. If you use the group named EVERYONE, it is important that you check to make sure that all users are included in the group EVERYONE (see the section titled "Using the Group Everyone" at the beginning of this document.) IMPORTANT: When you create a queue from within PCONSOLE, PCONSOLE prompts you for the "Print Queue's Volume." The print queue can be created on any volume, but the queue must be created on the same server where the NFS product is installed. The print queue's volume must also be located within the Bindery Context. CONFIGURING USING PLPDCFG -------------------------- The configuration procedure for the PLPDCFG NLM has not changed for this patch. When mapping users, it is important to know that the user named GUEST might not exist in NetWare 4.01. If you upgraded your server from a NetWare 3.11 server to a NetWare 4.01 server, the user named GUEST was created, but if you installed on a clean server, the user named GUEST does not exist. If you cannot find the user named GUEST, you can create the user named GUEST from the NETADMIN utility, or you can map UNIX users to a different NetWare account. ============================================== CONFIGURING NETWARE TO UNIX PRINTING (LPR_GWY) ============================================== You configure NetWare to UNIX Printing using the NFSADMIN utility The configuration procedure for NFSADMIN has not changed for this patch. The following sections describe the relationship between PCONSOLE objects (queues, printers, and print servers) and NFSADMIN. PRINTERS --------- Printers created from NFSADMIN are only visible from the Bindery mode of PCONSOLE. QUEUES & PRINT SERVERS ----------------------- Queues and Print Server are visible from both modes in PCONSOLE. OBJECT NAMES ------------- PCONSOLE replaces all underscores in object names with spaces. For example, if you create a print server named "ps_for_lab" from NFSADMIN, its name appears as "ps for lab" from within PCONSOLE. IMPORTANT: When you create queues using NFSADMIN, the group named EVERYONE is assigned as the only queue user. It is important to check that the group named EVERYONE includes all users that need to print from NetWare to UNIX using the this queue. PCONSOLE can be used to add users to the group EVERYONE, or to restrict access to the queue. New queue users can be assigned from within PCONSOLE. ================== CONTROLLING JOBS ================== You can use the PCONSOLE utility to control jobs for both PLPD and LPR_GWY. UNIX TO NETWARE PRINTING: ------------------------- You can remove pending jobs from queues and control printers by using the Directory Services mode of PCONSOLE. NETWARE TO UNIX PRINTING: ------------------------- You can remove queued jobs from a specific queue using the Directory Services mode of PCONSOLE. If you want to control printers created by NFSADMIN, you must enter the Bindery mode of PCONSOLE by pressing the key. (Printers created from NFSADMIN display only under Bindery mode.) You must be a Print Server operator to enter Bindery mode and change the status of the printer. If you need to create a print server operator within the bindery context, log in as ADMIN and create an operator using the Directory services mode of PCONSOLE. After you add the new operator, you must unload and then reload the LPR_GWY and LPR_SRV so that the changes take effect. ====================================================== CONFIGURING DEVICES AND FORMS FOR PLPD USING PLPDDEF ====================================================== PLPD does not work with the new PRINTDEF utility supplied with NetWare 4.01. A new DOS client utility named PLPDDEF.EXE is supplied with this patch to allow users to configure print devices and forms for PLPD. This new utility has the same user interface as the PRINTDEF.EXE utility distributed with NetWare 3.11. PLPDDEF allows PLPD users to configure forms and print devices (printers and plotters), which are used by PLPD. In most cases, PLPDDEF operates similarly to the NetWare 4.01 PRINTDEF utility. There are two main differences between the two utilities. The first is that the PRINTDEF utility requires a context setting because it stores information in the NetWare 4.01 Directory, while PLPDDEF does not have a context. The second difference is that PLPDDEF stores information in SYS:PUBLIC/NET$PRN.DAT. This database cannot be shared by PRINTDEF in NetWare 4.01 or by multiple servers. In general, the documentation on PRINTDEF supplied with NetWare 3.11 or NetWare 4.01 can be used with PLPDDEF except for any NetWare 4.01 references to setting a Context. USING PLPDDEF: -------------------- After logging into the NFS Server, change directories to SYS:PUBLIC and run the PLPDDEF.EXE program. Warning: You must be logged into the server as a user located within the Bindery Context. If you are logged in as user1 and your Bindery Context is set to OU=department.O=company, then user1 must be located within the Directory OU=department.O=company. ============================================================================== INSTALLING THE PATCH ============================================================================== This patch updates the NetWare NFS (v1.20B) product. This patch incorporates extended features to run on NetWare 4.01. It is divided into two parts: 1. Patch to PLPD.NLM, PKERNEL.NLM, XCONSOLE.NLM, FTPSERV.NLM and NFSSERV.NLM 2. Patch to NFS.NAM (For NetWare 4.01 only.) FILES FOR THIS PATCH --------------------- UNPACKR.EXE YESNO.EXE PLPDDEF.EXE PRINTDEF.HLP READ40.TXT PTF-F153.RTP PATCH.EXE The procedure for applying the update to the NLMs for NetWare NFS v1.2b will be to transfer the files from the SYS:SYSTEM and PUBLIC directories to a client workstation, apply the patch, and then transfer the patched files back to the NetWare server. The new version of the files after the patch is applied will be 1.27b. PREPARING TO INSTALL -------------------- Before you start the PATCH procedure, make sure you have the following: NetWare NFS v1.20b installed on your server. Before you begin this procedure, you must login to the server from a DOS workstation as SUPERVISOR. During this procedure: Drive C: is assumed for all activities on the workstation. Drive A: is assumed for all activities related to the floppy drive. Drive F: is assumed for all activities related to the NetWare server. You need to create a temporary directory for this procedure named TEMP1. If this name is already used on this workstation, use another name for the temporary directory where TEMP1 is specified in this procedure. PATCHING THE NLMS FROM A DOS WORKSTATION ------------------------------------------ 1. Create a temporary directory on the workstation. This directory will contain the PATCH files and the NLMs. (This procedure assumes the temporary directory is created on drive C:. Substitute the actual drive letter to be used for C:) C:> MKDIR \TEMP1 2. Transfer the PATCH files to the directory TEMP1. (This procedure assumes the files are on a floppy diskette. Substitute the actual location of the files for A:.) C:> CD \TEMP1 C:> COPY A:*.* 3. Run the installation for NetWare 4.01 by typing C:> INSTALL 40 F: 4. Remove the patch floppy diskette from the A: drive and then insert a new floppy diskette. 5. Copy the NFS name space onto the floppy diskette by typing F:> C: C:> COPY NFS.NAM A: 6. Remove the floppy from drive A: and take it with you to the server console. UPDATING THE NFS NAME SPACE ON THE SERVER ------------------------------------------ You should make sure that all users are logged out before you down the server. This entire procedure is done at the server. 1. Down the server from the console prompt by typing : down : exit 2. Insert the new floppy containing the NFS name space into the A: drive. 3. Copy the new NFS.NAM file to C:\NETWARE (boot drive) by typing C:> COPY A:NFS.NAM C:\NETWARE 4. Restart the server. The NLMs and NFS name space are now updated to include the patch.