NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NFS202.EXE; Patch for NFS 2.1 & 2.12 README FOR: NFS202.EXE NOVELL PRODUCTS and VERSIONS: NetWare NFS Services - NetWare 4 Edition 2.1 NFS Gateway 2.12 - NFS212 ABSTRACT: NFS202.EXE corrects more than 20 problems not addressed by NFS199, in addition it adds additional configuration parameters and makes NetWare NFS generally more robust. NFS202.EXE is exclusively for sites with NFS 2.1, 2.11 or NFS 2.12. NFS202 supersedes NFS197, NFS198, NFS199, NFS200 and NFS201. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- SYMPTOM: Many of the following symptoms occour only in some enviroments and under some conditions. PLPD Symptoms ------------- 1. In PLPD, options specified in "Print Job Configuration" using Unicon, associated with a queue, did not work. (see "solution" below") 2. Changes made in a "Print Job Configuration" did not take effect unless PLPD was unloaded and reloaded. Example: User had a queue "Novell_Q1" and a print job configuration "PRT1" associated with it and an option for number of copies of 2. If changed to 7 copies, PLPD still printed only 2 copies, unless a unistop and unistart was done. The same was true with other options. The old configuration values were used to print a job even though the screen showed the new values. 3. The banner page information was incorrect. ie File Name - Printed the complete pathname appended to the filename, but truncated after 12 characters. Directory - Field was left empty. Description - Information displayed was incomplete. 4. The postscript filter did not work correctly when the user did not specify a title, causing a server abend. 5. Binary jobs printing as a series of strange characters. 6. If there was heavy network traffic, PLPD timed out while receiving a job. (see "solution" below") 7. With non-ASCII hosts, LPR command line options only worked if entered in lower case. 8. Wrong error messages on the PKERNEL screen if the default queue configuration was modified. Example "PLPD-ERROR 370" Unable to update the PLPD Job configuration". 9. PLPD did not allow a new print job to be sent by a LPR client to a port, unless 4 minutes had passed since the prior print job to the port. 10. PLPD would not load if NETDB did not successfully log into NDS. NFSSERV Symptoms ---------------- 11. In NFS modes #1 and #2, the NFS server modified the Netware Inherited Rights Mask in such a way that Netware users did not have proper access to files. LPRGWY Symptoms --------------- 12. When LPR_GW_DIRECT_MODE was set to OFF and a print job was sent to a LPD server (OS2 Box etc) the server abended. 13. When connected to a printer via Jet Direct (or a similar product), if the printer showed out of paper while printing a job, if paper was not quickly added, the job started all over again. 14. The server abended when a print job was sent from the NetWare server to an IBM LAN Server host running LPD. 15. If a NetWare user, had "-" in their login name, and the "-" was followed by {"c", "d", "f", "g", "n", "t", "v", "1", "2", "3", or "4"} and printed to a print queue serviced by a LPR Gateway, the LPR Gateway interpreted the '-X' (X is any of those characters) to be a filter option (eg. -c in the name was interpreted as a PLOT CIF file). 16. With a multiport Lexmark box, if a job failed to complete on a printer connected to one port, jobs did not go to printers connected to other ports. NFS Gateway Symptoms --------------- 17. NFSGW had Abends under load conditions and some timing problems showed up in large complex environments where the same files and directories were being accessed from DOS and UNIX in parallel. 18. In systems with a large number of files and directories, while accessing a volume, an inconsistent view of the file system could occur. 19. NFS Gateway could not work with NFS Servers which disable root access. If root access was disabled, NetWare mode of operation for a volume would not work as the NFS Gateway tried doing all operations with UID 0, which was not allowed. 20. If a file was created on the NFSGW volume from the NetWare server side and updated from the UNIX side it did not show the correct file size when seen from the NetWare side. FTP Server Symptoms ------------------- 21. If the default name space was for NFS and the users home directory had capital letters, the user was not able to start an FTP session. 22. The "cd .." command at NetWare volume level (/sys/) caused "PWD" and "DIR" to behave inconsistently. Note :- 1,2 and 3 are the commands which exhibited the inconsistency . ftp> cd /sys /* SYS is a netware volume */ ftp> pwd /sys/ 1--> ftp> cd .. 2--> ftp> dir {Shows the contents of /sys/ instead of list of volumes) 3--> ftp> cd etc /* ETC is a directory under SYS */ (SAYS no such directory) 23. A DIR of files created before the current year, only showed the DATE and TIME fields. The YEAR was not shown. Correct Behavior is to show the year of the file in place of TIME if the file is not of the CURRENT year. 24. A DIR at the root level (/) did not show the list of volumes available. 25. A "CD" command returned code #257 on success. Return code #250 should have been shown. 26. When the user ANONYMOUS through NETADMIN was deleted, a user could still login to the FTP Server as ANONYMOUS and could execute one command successfully before being informed that user ANONYMOUS did not exist. 27. When multiple options in RESTRICT.FTP were separated by commas "," only the first option was effective. e.g. * ACCESS=GUEST,READONLY would be only ACCESS=GUEST. READONLY was ignored. 28. A FTP server user could not login, if the NDS home directory was on a remote server that was down. 29. Users logging in with guest restriction ACCESS=GUEST) were able to access the parent directory of their home directory by doing a "cd ..". although their home directory should be their root directory (/). TELNETD Related Symptoms ------------------------- 30. TN3270 did not work if XCONSOLE was loaded first. 31. XCONSSRV not releasing resources. NOTE: XCONSSRV may still fail to release a file handle with the CLIB.NLM in LIBUPC, but the error may safely be ignored. 32. Unable to TELNET into a XCONSOLE session from a SUN workstation. Carried Over from NFS199 ------------------------ 33. When reading files, the NFS server would occasionally abend due to a page fault. 34. When accessing files on a NetWare NFS server, file ownership and access permissions randomly changed. 35. During install, after all of the files were copied to the server and UNICON was loading, if the installer tried to log in, the error message "Remote TCP/IP administration not running" was received. 36. The FTP server would not allow users to log in after the administrator had modified FTP access through the FTP Administration option in UNICON. 37. The FTP server returned a generic code of 200 upon successful completion of a directory change. Some clients expected a specific return code of 250. 38. The FTP server did not allow multiple anonymous users to access the same file at the same time. 39. When users were at the root level of a volume on a NetWare FTP server, they could not change to a subdirectory without using an absolute path name. 40. When a user logged in as an anonymous user, the FTP server required a password (even if a password had not been assigned). 41. The FTP server did not support the STORE UNIQUE (STOU; SUNIQUE) command. 42. The DNS server did not properly handle a primary domain name suffixed with anything other than .COM. 43. UNICON failed to save the DNS database to text files. The error "NIS and DNS services not configured to run on this machine" was displayed. 44. The DNS server did not properly resolve a MX (mail exchange) query. 45. The DNS Server abended while doing a zone dump from a secondary server when the size of the reply was larger than the buffer allocated by the DNS server. 46.. SUN's NIS+ server, when running in YP emulation (NIS emulation) mode, did not support YPPROC_ORDER remote procedure call. This resulted in a situation where YPXFR.NLM could not get the NIS maps order numbers and would abort the transfer of maps. 47. The NFS gateway failed to mount DEC VMS file systems. 48. The NFS gateway did not support the SGID bit on remote directories. 49. The NFS gateway server abended when it tried to mount more than 64 volumes. 50. OS/2 sessions hung while copying a file to a NFS Gateway volume. 51. Even though the NetWare user was mapped, the NFS Gateway displayed the message: "Login user xxx does not have NFS UID and GID". 52. When the UNIX server had a hard disk larger than two Gigabytes, incorrect volume information was displayed and write-through was unnecessarily turned on. 53. A NetWare client could not see changes made from UNIX to a NetWare NFS gateway directory, until a file scan (DIR or other NetWare command that performs a scan) was done. 54. When NetWare NFS print services was loaded while NDS was unloaded, the NetWare server abended with the message: "NLM unloaded without deleting all its semaphore." 55. PLPD used too much server memory when several jobs were sent from UNIX hosts. 56. After applying the FORTRAN filter, FORTRAN print jobs would not print. 57. When UNIX to NetWare printing was configured with UNICON, the NetWare server would occasionally abend. 58. LPR clients were unable to submit print jobs to NetWare queues when the queue names were longer than eight characters. 59. LPR Gateway jobs were printed twice if the printer ran out of paper. When more paper was added, the printer finished the interrupted print job and then printed the job again. 60. PLPD refused LPR requests from port numbers less than 1024. 61. When using the LPR Gateway, PSERVER showed "PRINTER MAY NEED ATTENTION" status and had to be restarted. 62. When using the LPR Gateway, PSERVER showed the XRP printer state changing between "Ready for New Job" and "Error at remote Unix host." PKERNEL displayed the error message: "No sequence numbers available for the remote host." 63. When the LPR Gateway was unloaded and reloaded, the Gateway displayed the error: "No configured UNIX printers." CAUSE Symptom #8. An error occurred while updating Queues, Trusted hosts or Default User. Symptom #18. This error occurred at run-time because we ran out of contiguous memory to grow the directory tables to take care of new entries. SOLUTION: The general solution is to install NFS202. However, some of the symptoms require specific solutions AFTER applying NFS202. Symptom #1 The Word Perfect file PLPD.WP describes how the options under "Print Job Configuration" should work. Symptom # 6 Set the poll time value through NWPARAMS as follows: In the NWPARAMS file - under the "PRINT_ADMIN" section add the entry: PLPD_POLL_TIME " where the value is in seconds. The lower limit is 30 seconds and upper limit is for 1000 seconds. Symptom #11 Specific Solution Add the following parameter to the NWPARAMS file under the section "NFSSERV" and set it ON STRICT_NFS_MAPPING ON This sets the NETWARE IRM to the rights of Others (World objects rights) for Netware users. The trustee rights are generated with a one-one correspondence of rwx access mode to NetWare rights. Symptom #13. Add a new nwparams parameter LPR_GWY_MAX_PRT_TIME under the section "PRINT ADMIN", which can have valid value between 30 seconds and 7200 seconds (2 hours). Any value outside this range will result in the default value of 300 seconds. LPR_GWY_MAX_PRT_TIME is the time, that a connection will wait without a response from the remote Unix side, before causing a logical time out. Typically for low buffer printers, if the printer is out of paper, the LPR_GWY can wait for THIS amount of time before assuming that the connection is lost and starts spooling the job all over again. Symptom #18 Specific Solution Preallocate these tables using the Initial number of Directory Blocks field associated with each volume while configuring. A rough formula for this value is: Number of Directories on the Unix(NFS) exported file system / 256 + Number of Files on the Unix(NFS) exported file system / (32*256) + around 20% of the above as buffer for future growth e.g if there 20,000 directories and 100,000 files the value would be 20,000/256 + 100,000 / (32*256) = 79 + 13 = 92 20% of 92 = 18 Value to set = 92+18 = 110 Symptom #19 solution Setting the following option in the NWPARAMS file under "NFSGW" section allows directories owned by root to be listed using the mount id. USE_MOUNT_ID_FOR_ROOT 1 Symptom #21 solution Upper and lower case must be used consistently. That is, if when viewed from the NFS Client or the UNIXHOST, Environment Information in NETADMIN shows the path to be UpandDown, the Home Directory must be entered as UpandDown. Not: UPANDOWN or upanddown or UPanddown Self-Extracting File Name: NFS202.EXE Files Included Size Date Time ..\ NFS202.TXT (This file) PLPD.WP 6965 4-3-97 10:02:08 pm ..\NFS200\ NFSICMD.NLM 16524 7-2-96 4:36:08 pm PINSTALL.IPS 577 3-14-97 11:32:12 pm PINSTALL.NLM 156506 3-31-97 8:56:02 pm README.TXT 30440 11-19-96 9:11:08 pm SPACE.DAT 14 4-1-97 10:21:02 pm ..\NFS200\ETC\ DOMAIN.IDX 25 6-14-94 8:57:56 pm DOS2UNIX.C 2934 8-1-96 5:50:42 pm ENSCRIPT.PRO 719 6-25-92 8:23:50 pm FILTERS 150 11-24-93 9:58:42 pm FILTTYPE 206 12-16-93 11:35:52 pm HOSTS 28 6-24-92 10:22:56 pm INETD.CFG 288 7-11-94 5:31:46 pm NFS20.MIB 25591 12-1-94 3:06:48 am NFSGROUP 35 6-16-94 6:04:12 pm NFSUSERS 33 6-16-94 6:04:08 pm NISMAKE 508 8-9-94 5:18:10 pm NWPARAMS 733 3-14-97 10:50:10 pm POSTSCPT.PRO 2044 6-25-92 8:24:04 pm RESTRICT.FTP 2262 12-22-94 1:43:30 am ROOT.DB 2052 12-9-94 5:16:20 pm RPCNET.CFG 185 8-4-94 7:37:36 pm SERVICES 1712 11-1-96 6:28:54 am UNIX2DOS.C 2515 8-1-96 5:50:46 pm XFONTEUR 92 2-4-95 12:38:58 am ..\NFS200\ETC\NET\ ..\NFS200\ETC\NET\NETWARE\ SERVICES 140 7-31-92 10:39:50 pm ..\NFS200\PUBLIC\ CHGRP.EXE 45317 3-30-97 6:26:54 am CHMOD.EXE 46031 3-30-97 6:27:18 am CHOWN.EXE 45349 3-30-97 6:26:40 am DOS2UNIX.EXE 10477 6-23-92 1:25:28 am LS.EXE 56229 3-30-97 6:26:26 am UNIX2DOS.EXE 10335 6-26-92 12:42:32 am ..\NFS200\PUBLIC\NLS\ ..\NFS200\PUBLIC\NLS\ENGLISH\ CHGRP.MSG 1140 3-30-97 4:55:42 am CHMOD.MSG 1141 3-30-97 4:55:40 am CHOWN.MSG 1140 3-30-97 4:55:40 am LS.MSG 2567 3-30-97 4:55:38 am ..\NFS200\SYSTEM\ CONFADDR.NLM 27576 9-19-96 10:00:06 pm DISPATCH.NLM 41980 3-30-97 5:08:42 am DLLINFO.NLM 6029 3-30-97 6:58:22 am DNSADMIN.NLM 43827 9-19-96 10:18:12 pm DNSAGENT.NLM 32828 9-19-96 10:13:54 pm DNSCONV.NLM 3674 9-19-96 10:11:08 pm DNSDBGEN.NLM 12992 9-19-96 10:18:42 pm DNSUTIL.NLM 2459 9-19-96 10:18:56 pm FTPADMIN.NLM 43010 3-30-97 6:31:48 am FTPAGT.NLM 18204 3-30-97 6:32:28 am FTPSERV.NLM 130009 5-14-97 7:01:36 pm GWADMIN.NLM 59158 3-30-97 6:24:08 am GWAGENT.NLM 37225 3-30-97 6:25:00 am GWREPAIR.NLM 58928 3-30-97 6:22:22 am HOSTG.NLM 10726 9-19-96 9:56:22 pm HOSTGADM.NLM 7073 9-19-96 9:56:46 pm HOSTGAGT.NLM 3764 9-19-96 9:57:02 pm INETD.NLM 15782 4-10-97 12:11:48 am IOTADJST.NLM 8681 3-30-97 6:59:06 am IOXCSTUB.NLM 4771 9-19-96 10:10:54 pm LOCAL_ND.NLM 8320 7-11-94 12:48:04 am LOCKD.NLM 164763 3-30-97 5:46:26 am LPRLOAD.NLM 3870 3-30-97 6:50:44 am LPR_GWY.NLM 47742 4-11-97 10:21:34 pm MSTADJST.NLM 6522 3-30-97 6:59:32 am MSXCSTUB.NLM 3558 9-19-96 10:10:28 pm NAMED.NLM 34693 9-19-96 9:54:22 pm NETDB.NLM 107438 2-19-97 6:57:56 pm NETDIR.NLM 13439 9-22-94 9:11:02 pm NFSCA.NLM 87430 3-30-97 5:57:08 am NFSDISP.NLM 4459 3-30-97 5:57:30 am NFSGWSA.NLM 14257 3-30-97 6:19:38 am NFSGWVS.NLM 227458 5-6-97 12:04:06 am NFSSERV.NLM 209578 3-30-97 5:42:28 am NFSUNINS.NLM 96047 3-31-97 8:58:34 pm NFSUSER.NLM 113138 3-30-97 5:23:10 am NFS_41X.NAM 33184 3-30-97 5:06:12 am NFS_GR.NAM 34604 3-30-97 5:06:34 am NISADMM.NLM 54567 3-30-97 5:37:52 am NISBIND.NLM 51090 3-30-97 5:32:18 am NISDMAG.NLM 131563 3-30-97 5:30:34 am NISGO.NLM 70208 3-30-97 5:32:50 am NISSERV.NLM 53879 3-30-97 5:34:12 am NISSWDD.NLM 27523 3-30-97 5:37:10 am NWCCSS.NLM 3676 9-19-96 10:20:00 pm NWNFS.NLM 35546 3-30-97 5:10:04 am NWPCNFSD.NLM 71349 3-30-97 6:54:26 am PCONFIG.NLM 21394 3-30-97 4:56:50 am PKERNEL.NLM 172894 4-17-97 1:51:20 am PLPD.NLM 79845 3-30-97 6:39:58 am PRADM.NLM 118349 3-30-97 6:45:02 am PRADM_SA.NLM 23003 3-30-97 6:45:40 am PRLIB.NLM 63468 3-30-97 6:36:18 am RARPSERV.NLM 8176 9-19-96 10:21:40 pm RPCBSTUB.NLM 665 3-30-97 5:04:50 am SA_ADMN.NLM 28810 3-30-97 5:52:34 am SA_LOCK.NLM 16128 3-30-97 5:49:44 am SA_STAT.NLM 23214 3-30-97 5:51:08 am SPX_ND.NLM 9367 7-11-94 12:47:44 am SRVAGT.NLM 57457 3-30-97 5:25:32 am STATD.NLM 24446 3-30-97 5:47:46 am TADJST.NLM 3894 3-30-97 6:58:40 am TCP_ND.NLM 12213 7-11-94 12:38:14 am TELNETD.NLM 23910 2-12-97 8:56:30 pm TFTPSERV.NLM 5824 9-19-96 10:20:40 pm TIMCHK.NLM 3750 3-30-97 6:57:42 am TIRPC.NLM 52630 9-20-96 6:08:04 pm TUI.NLM 43415 10-19-94 7:13:56 pm UNICON.NLM 278972 3-30-97 5:18:46 am UNICRYPT.NLM 4027 3-30-97 5:04:40 am UNIDLL.NLM 7360 3-30-97 6:58:10 am UNISTART.NCF 4 8-6-96 9:18:06 pm UNISTART.NEW 3 11-14-96 8:43:10 pm UNIXLIB.NLM 72794 4-30-97 3:34:10 pm USRAGT.NLM 40069 3-30-97 5:26:34 am V_NFS.NLM 9567 3-30-97 6:51:14 am XCONSOLE.NLM 4078 9-19-96 10:20:20 pm XCONSSRV.NLM 132441 1-8-97 1:29:50 am YPCAT.NLM 25690 3-30-97 5:35:38 am YPMATCH.NLM 24513 3-30-97 5:36:06 am YPPUSH.NLM 35208 3-30-97 5:35:12 am YPSET.NLM 23098 3-30-97 5:36:32 am YPXFR.NLM 85904 3-30-97 5:34:42 am ..\NFS200\SYSTEM\NLS\ ..\NFS200\SYSTEM\NLS\1\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm ..\NFS200\SYSTEM\NLS\10\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm ..\NFS200\SYSTEM\NLS\12\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm ..\NFS200\SYSTEM\NLS\13\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm ..\NFS200\SYSTEM\NLS\14\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm ..\NFS200\SYSTEM\NLS\16\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm ..\NFS200\SYSTEM\NLS\4\ CONFADDR.MSG 2201 9-19-96 10:00:02 pm DISPATCH.MSG 3594 3-30-97 5:08:40 am DNSADMIN.HLP 6167 5-31-95 11:25:56 pm DNSADMIN.MSG 5213 9-19-96 10:18:08 pm DNSAGENT.MSG 2028 9-19-96 10:13:52 pm DNSCONV.MSG 474 9-19-96 10:11:08 pm FTPADMIN.HLP 9833 1-9-95 4:38:30 pm FTPADMIN.MSG 4758 3-30-97 6:31:46 am FTPAGT.MSG 533 3-30-97 6:32:26 am FTPSERV.MSG 13662 3-30-97 6:30:14 am GWADMIN.HLP 29618 8-9-95 12:56:12 am GWADMIN.MSG 11085 3-30-97 6:24:58 am GWREPAIR.MSG 15105 3-30-97 6:22:20 am HOSTG.MSG 474 9-19-96 9:56:20 pm HOSTGADM.HLP 1170 1-8-95 12:04:08 am HOSTGADM.MSG 968 9-19-96 9:56:44 pm HOSTGAGT.MSG 225 9-19-96 9:57:02 pm INETD.MSG 1189 4-10-97 12:11:46 am IOTADJST.MSG 1431 3-30-97 6:59:04 am IOXCSTUB.MSG 747 9-19-96 10:10:54 pm IPADDR.HLP 9939 1-9-95 4:45:06 pm LOCKD.MSG 14661 3-30-97 5:46:22 am LPRLOAD.MSG 419 3-30-97 6:50:42 am LPR_GWY.MSG 10095 3-30-97 6:50:18 am MSTADJST.MSG 859 3-30-97 6:59:28 am MSXCSTUB.MSG 527 9-19-96 10:10:28 pm NAMED.MSG 4803 9-19-96 9:54:18 pm NETDB.MSG 3941 2-19-97 6:57:52 pm NFSCA.MSG 10854 3-30-97 5:57:04 am NFSCAHLP.HLP 40574 1-20-95 5:27:20 pm NFSGWSA.MSG 990 3-30-97 6:19:36 am NFSGWVS.MSG 84096 3-30-97 6:18:12 am NFSSERV.MSG 10817 3-30-97 5:42:24 am NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm NFSUSER.MSG 13029 3-30-97 5:23:06 am NFS_41X.MSG 5562 3-30-97 5:06:10 am NFS_GR.MSG 5896 3-30-97 5:06:32 am NIS.MSG 18669 3-30-97 5:37:08 am NISADMM.HLP 9907 10-20-94 8:17:20 pm NISADMM.MSG 6054 3-30-97 5:37:50 am NWNFS.HLP 142 1-31-95 7:01:04 pm NWNFS.MSG 6832 3-30-97 5:10:00 am NWPCNFSD.MSG 10936 3-30-97 6:54:22 am PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm PKERNEL.MSG 8944 3-30-97 5:04:14 am PLPD.MSG 19261 3-30-97 6:39:56 am PRADM.HLP 27933 3-2-95 11:45:48 pm PRADM.MSG 9986 3-30-97 6:44:58 am PRLIB.MSG 2930 3-30-97 6:36:14 am SAADMN.MSG 3493 3-30-97 5:52:30 am SALOCK.MSG 1321 3-30-97 5:49:42 am SASTAT.MSG 2808 3-30-97 5:51:04 am SRVAGT.MSG 3043 3-30-97 5:25:28 am STATD.MSG 5000 3-30-97 5:47:42 am TADJST.MSG 220 3-30-97 6:58:38 am TELNETD.MSG 1822 9-19-96 10:19:46 pm TFTPSERV.MSG 992 9-19-96 10:20:40 pm TIMCHK.MSG 415 3-30-97 6:57:40 am TUI.MSG 2304 11-16-93 4:57:40 am UNICON.HLP 57792 5-31-95 3:12:20 pm UNICON.MSG 24449 3-30-97 5:18:38 am UNIXLIB.MSG 5295 3-30-97 6:57:20 am USER.HLP 56938 8-4-95 5:17:44 pm USRAGT.MSG 1756 3-30-97 5:26:32 am V_NFS.MSG 2178 3-30-97 6:51:12 am XCONSOLE.MSG 799 9-19-96 10:20:20 pm XCONSSRV.MSG 10274 1-8-97 1:29:46 am ..\NFS200\SYSTEM\NLS\6\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm ..\NFS200\SYSTEM\NLS\7\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm ..\NFS200\SYSTEM\NLS\8\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm ..\NFS200\SYSTEM\NLS\9\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 3-31-97 8:58:30 pm PCONFIG.DAT 15196 3-27-97 7:00:58 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 3-30-97 4:56:48 am PFILES.DAT 83092 4-16-97 7:41:06 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12472 3-31-97 8:55:56 pm Installation Instructions: 1. Make sure that NFS 2.1 or NFS 2.12 is already installed. 2. From a workstation, login as the server's administrator and have supervisory rights to the SYS volume. 3. Backup your current SYS:SYSTEM and SYS:ETC subdirectories as a precaution. 4. Put NFS202.EXE into an empty directory at the root of the servers' SYS volume. 5. At the workstation prompt, "explode" NFS202. NFS202 A directory named NFS200 will be created, and all the binary files will be extracted in that directory. The following steps may be done at the server console or with RCONSOLE. 6. From the server console, run UNISTOP.NCF as a general precaution. UNISTOP 7. LOAD INSTALL 8. Select "Product options." 9. Select the "View/Configure/Remove Installed Product" option from the "Other Installation Actions" menu. The "Currently Installed Products" menu will appear and should include one of the following: NFS 2.1 NFS 2.1 OR NFS 2.12 IntranetWare NFS Services 2.12 If this entry is not present, installation for this patch will not proceed. Install NFS2.1 or NFS2.12 and then try installing this patch. 10. If you have installed any of the earlier patches (NFS197, NFS198, NFS199, NFS200, or NFS201) they will also be visible in the list. Remove the installed patch by. A. Pressing the DEL key B. Selecting YES when prompted to remove. If an earlier installed patch is not removed, installation of NFS202 will fail. 11. Press the key to install a new patch. 12. Press the key to install NFS202. The "Specify Directory Path" dialogue box will appear. 13. Enter the path to the NFS200 subdirectory to which the NFS202 files extracted. After the installation program installs the files, the "Currently Installed Products" menu should list the following additional entry. NFSPAT 2.12 Update for IntranetWare NFS Services 2.12 (If you have NFS 2.1, do not worry, this patch will also work for you.) 14. Exit INSTALL or press + to return to the console prompt. 15. From the server console, run UNISTART.NCF to restart NFS Services 2.12 (and other products if installed). UNISTART 16. PLPD.WPD contains a Word Perfect document which specifies how the options specified in the "Print Job Configuration" using Unicon, associated with a queue, should work. 17. If you have not read the readme for NFS 2.12, you may wish to do so. It is in README.TXT. 18. Instructions for the following are below: - To tune the NFS 2.1 server - To implement a large block of memory for mounting - To configure the FTP server for web clients - To implement lock compatibility between the NFS Gateway and Sun's PCNFS - To print to devices that emulate UNIX host LPR In addition, configuration information for several important LPR Gateway parameters follow. To Tune the NFS Server ---------------------- Many normal activities such as users logging into the server or backing up the server can cause NetWare 4.1 servers to reach 100% utilization. Peaking to 100% utilization is not bad, but if utilization is consistently high, some low priority threads may cause your server to hang when they run. The server has normal tasks that are very CPU intensive, and these tasks are scheduled to run as low priority tasks when the server is not busy. Some of these tasks are related to the health of NetWare volumes, such as sub-block allocation and disk compression. While these volume tasks are run, other threads that need to access the volume block on the volume semaphore. If your system is not properly tuned and NFS is consuming large time slices, then the low priority threads are not run. The server can then lock up when one of the sub-allocation pools runs out. The server then schedules the sub-allocation thread even though the server is busy, and all the server threads can end up blocked on the volume semaphore. The server requires a thread to restart the sub-allocation thread, but all available threads are in use. When this happens, MONITOR shows that the current number of server threads equals the maximum number of server threads. Follow the steps below to increase the performance and decrease the utilization of the server. 1. Make sure that the NetWare server and the drivers are at the current patch level. 2. Determine if the applications running on the server create a lot of temporary files. If this is the case, enable Immediate Purge of deleted files on the volumes that store the temporary files. The purging frees up directory entries and lowers CPU utilization. 3. Tune the Number of Packet Receive Buffers to ensure that there are enough Packet Receive Buffers. Set the minimum number of packet receive buffers to two times the number of licensed connections and the maximum number of packet receive buffers to four times the number of licensed connections. 4. Disable File Compression and Packet Burst in order to lower CPU utilization. 5. After applying NFS202, monitor the performance of the NFS server to see if adjusting the number of NFS server threads is required. If performance is consistently high, increase the number of NFS server threads. a. Starting at the UNICON main menu, select the following options: Manage Services--> NFS Server--> Set Parameters. b. Increase the Number of NFS Threads from its current level to 10 more. Monitor performance and gradually increase the threads by increments of 10 to find the right number for the server. NFS202 changes the upper limit for threads from 20 to 150. The NFS server uses the threads to handle all the NFS server traffic. Increasing the number of threads allows more concurrent operations on the NetWare server. NOTE: After installing NFS202 and then loading PKERNEL, the initial TCP/IP Receive Buffers count may quickly climb but should drop off and remain low. To Implement a Large Block of Memory for Mounting ------------------------------------------------- The NFS gateway supports the allocation of a large block of memory when initially mounting an NFS gateway volume. The size of the initial block of memory is set with UNICON in the NFS Gateway Volume Information form. Select the volume that needs a larger block of memory and enter the block allocation number. The valid range is from 1 to 256 (each block contains 256KB of memory). To implement a large block of memory for mounting a volume, complete the following steps after installing NFS202. 1. Set error logging to INFORMATIONAL and clear the audit log. 2. At the server console, run the UNISTOP script. 3. At the server console, run the UNISTART script. 4. Load UNICON. 5. Configure each gateway volume to the number of blocks to be allocated. This is set in the NFS Gateway Volume Information form. To display the form, select the following options starting at the main menu: NFS Gateway Administration --> Configure Volumes --> volume. 6. Mount the NFS Gateway volumes. 7. Monitor the audit log to determine how many 256KB blocks are needed for each volume. To Configure the Netware FTP Server for Web Clients --------------------------------------------------- 1. Verify that the Anonymous user is enabled and the home directory is set. a. Starting at the UNICON main menu,Services--> FTP Server--> Set Parameters. b. On the FTP Server Parameters form, check that the "Anonymous User's Home Directory" is configured. 2. Verify that the Anonymous user is mapped. a. Starting at the UNICON main menu, Objects--> Manage Users. b. Select a method to view the mapping for the Anonymous user. By default the UID is set to 32000. 3.Verify that the volume where the Anonymous user's home directory resides supports the NFS name space. The console command, VOLUME, will display whether the volume supports the NFS name space. If not, enter the following console command: ADD NAME SPACE NFS TO Replace with the name of the volume that needs the NFS name space. 4.Verify that the Anonymous user owns its home directory and has file access rights to the directory. a. Starting at the UNICON main menu, select the following options: Perform File Operations--> View/Set File Permissions. b. Select the Anonymous user's home directory. c. Set the owner to Anonymous and give the owner NFS access rights. To Implement Lock Compatibility between the NFS Gateway and Sun's PCNFS ----------------------------------------------------------------------- 1. Edit SYS:ETC\NWPARAMS. 2. Set PCNFS_COMPATIBILITY to 1 in the [NFSGW] section. The PCNFS_COMPATIBILITY parameter makes NFS gateway locking compatible with Sun's PCNFS locking. To Implement Immediate File Access on NFS Gateway Volume -------------------------------------------------------- To make files created from UNIX immediately visible to NetWare users accessing the NFS Gateway volume, complete the following steps: 1. Edit the SYS:ETC\NWPARAMS file. 2. Add the following parameters to the [NFSGW] section: DIR_COMP_TIME 0 GW_EXHAUSTIVE_SEARCH 1 The DIR_COMP_TIME parameter forces a frequent directory compare between the NetWare information and the UNIX information so that changes from UNIX are immediately visible from NetWare. The GW_EXHAUSTIVE_SEARCH parameter allows UNIX filenames with capital letters to be immediately visible. To Print to Devices That Emulate UNIX Host LPR ---------------------------------------------- The LPR Gateway was originally designed to interface only with actual UNIX hosts. Thus, the gateway's function was to transfer a print job to the host and optionally monitor the progress of the job at the host. However, with the advent of hardware that allows printers to emulate the LPR protocol, many customers wanted to eliminate the UNIX host for printing purposes and transfer directly to the printer. The following devices have been tested and performed well with LPR gateway: HP JetDirect Card LANTRONICS MPS1 Other devices that emulate the LPR protocol may work with the LPR Gateway, but they have not been tested. This release of the LPR Gateway uses a set of parameters that are defined in the file "SYS:ETC/NWPARAMS" in the [PRINT_ADMIN] section. The file is case sensitive, so enter the parameter names in all capitals. The parameters are as follows: LPR_GWY_DIRECT_MODE ON ------------------------ Specifies when the job is sent to the printer by setting the LPR Gateway in direct or indirect mode. If set to "ON" the LPR Gateway is set to Direct Mode, and the next print job is immediately sent without waiting for the previous job to print. In this mode, once the print job has been spooled to the remote printer, the job cannot be aborted or its status checked from the NetWare side. That is, LPR_GWY does not check the status of the job after its spooled to the Unix side, after submitting the job to UNIX side (queue), LPR_GWY does not check for any further status of that job (i.e. whether is getting printed, or has actually completed printing!), and services the next job to be spooled. If set to "OFF" the LPR Gateway is set to Indirect Mode and status checking will be done until the job is printed, and the next job is not sent until the previous job is finished. In this mode, the NetWare user can check the status and abort the job after it is spooled to the remote printer. For printers connected via HP JetDirect Card, this parameter has no effect. The default is "ON." LPR_GWY_POLLING_TIME 2 ------------------------ How long the LPR Gateway waits after submitting a print job to interact with the remote printer. For direct mode, this is the time before sending the next print job. For indirect mode, it is the time interval between status checks of the printer. Can have a value between 2 seconds and 10 seconds. The default value is 2 seconds. Example: if this PARAMETER is given a value 5 seconds, then in the worst case, a downed unix printer status will be displayed on the LPRGWY side five seconds after the unix printer is actually down. LPR_GWY_WRT_CHK_TIME 15 ------------------------- Specifies, in seconds, how long the LPR Gateway waits (while polling the socket) for a response after sending a write request, while queuing a job. If the time expires, a check is made to see if the LPR Gateway is going down or the job is being aborted. If not, a secondary status is displayed of "BUSY/Printing." Default is 15 seconds. Can have value between 10 and 30 seconds. LPR_GWY_CHK_PRT_TIME 90 ------------------------- Specifies, in seconds, how long the "BUSY/Printing" message is displayed before the message "May Need Attention" is displayed. That is, this is the time for which the gateway assumes the printer is working, if there is no response within this time from the printer, action is taken to see if the printer might be down. The value can be between 30 and 300 seconds. The default is 120 seconds. LPR_GWY_IR_TIME 10 -------------------- Specifies, in seconds, how long the LPR Gateway waits to check on printers that are in an error condition state. The default is 10 seconds, can have a value between 2 and 10 seconds. Other NWPARAMS entries under PRINT ADMIN, for LPR_GWY module ------------------------------------------------------------ 1. HIGH_WATER_MARK This is the maximum number of jobs in the Unix queue, for which LPR_GWY waits, and then initializes the JOB IDs for the Jobs to be spooled next. Default is 900. Can have value between 100 and 990. 2. SPOOL_CFILE_FIRST If ON, spools Control file first while submitting to Unix side. If OFF, datafile is sent first then control file. The Default is ON. 3. IDC_OVERRIDE If ON, and if ID collision detection is ON, then for a printer, the generation of a new sequence number is done forcibly. 4. SKIP_NETDB_MAPPING If this is ON, the gateway does not authenticate to NDS. (done through NETDB) The default is OFF. To Use an Alias to Export a Queue in a Different Context -------------------------------------------------------- 1. Use UNICON to create a print queue in the NDS context of the NetWare server that has NFS 2.1 or 2.12 installed. The queue will be displayed as its common name if it resides in the server's NDS context (in this case ). Since servers running NetWare 4.1 and above, can support multiple NDS contexts, the queue can be created in any context for which the server is configured. 2. Use UNICON to export this queue . 3. Use NWADMIN to create the queue in the desired context. 4. Use NWADMIN to delete queue from the context where NFS/PRTS 2.1 or 2.12 is installed. 5. Use NWADMIN to create an alias queue in the context where NFS/PRTS 2.1 or 2.12 is installed, and point the alias to the new queue in the desired context. The alias queue will now be set up to be used as one of the exported NetWare queues. NOTE With some UNIX hosts, if the administrator selects the following options, from the UNICON menu (Manage Services-> NFS Gateway->Configure Volumes) and then presses , incorrect resource information may be displayed. (this problem was solved by an earlier patch but has reappeared). ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------