FarPRINT LPD/LPR NLM for Netware (c) 1994 Network Instruments, LLC P.O. Box 581156 Minneapolis, MN 55458-1156 USA (612) 822-2025 FAX (612) 825-5647 BBS (612) 822-0902 Internet: info@netinst.com TABLE OF CONTENTS TABLE OF CONTENTS 1 INTRODUCTION TO FARPRINT 3 Functional Overview 4 Local Print (LPD) 5 Remote Print (LPR) 6 Who Should use FarPRINT 8 Limited Warranty 8 Copyright and License 9 How to License 10 System Requirements 11 Technical Support 11 INSTALLATION 13 Netware TCP/IP Requirements 13 Installing FarPRINT on the Netware Server 13 Configuring FarPRINT 15 Configuring Local Print (LPD) 15 Configuring Remote Print (LPR) 20 USING FARPRINT 27 APPENDIX 29 Debug Option 29 Sample AUTOEXEC.NCF 31 Program Descriptions 31 Overview of Line Printer Daemon Protocol (LPD) 32 INTRODUCTION TO FARPRINT Welcome to FarPRINT - Network Instrument’s LPD/LPR Print Server NLM for Netware. Network Instruments Print Server for Netware is a leader in a new generation of high performance LPD/LPR based NLM print utilities for Netware Servers. FarPRINT employs the industry standard LPD/LPR protocol to transfer print jobs to and from remote hosts and Netware servers. Using LPD/LPR protocol makes FarPRINT inherently compatible with the vast majority of UNIX and other systems that implement LPD services. FarPRINT allows direct cross-mapping of UNIX and Netware print queues. FarPRINT enriches any UNIX/Netware installation, providing immediate, high speed, reliable, bi-directional server-to-server printing With FarPRINT you no longer need to use an intermediate PC when printing from Novell to UNIX or UNIX to Novell. Server-to-server print queue mapping enhances both end user usability and overall reliability when printing from one environment to another. The need for server-to-server printing has been either overlooked or poorly implemented on most sites. Why reconfigure print queues just because you are adding a UNIX system? FarPRINT transparently moves UNIX print jobs to Netware queues (or visa-versa). FarPRINT provides high flexibility without sacrificing performance. For UNIX-to-Netware printing (LPD), FarPRINT can be configured for up to 48 UNIX queues to be mapped to Netware queues. For Netware-to-UNIX (LPR) printing, FarPRINT allows up to 48 Netware queues to be mapped to UNIX printers. FarPRINT seamlessly bridges the gap in Netware-to- UNIX printing. FarPRINT allows UNIX to take advantage of the installed Netware printer infrastructure (if you are adding a UNIX system to a Novell site). Or, FarPRINT allows Netware to take advantage of existing UNIX printers (if you are adding Netware to a UNIX site) - all completely transparent to the end user. Because FarPRINT directly cross-maps up to 48 Novell and UNIX print queues, users can print from either environment, as they always have, but now print jobs will be moved transparently to/from the Netware or UNIX spooler to the other environment. FUNCTIONAL OVERVIEW To use FarPRINT you will need to have a general understanding of how FarPRINT, Netware and LPD/LPR works. This section contains a discussion of the main features of remote and local network printing based on LPD/LPR. Every UNIX system and each Netware Server has the ability to collect, process, spool and eventually print jobs submitted by applications, workstations or by the operating system. These printing services are usually centered around a spooler. The spoolers function (for both UNIX and Netware) is to collect print jobs from various programs or stations and submit the print jobs to the various print devices in an orderly fashion. In UNIX, the spooler is called just that - "the spooler". For Netware, the spooler is called a "Print Server". In the Netware environment, each Print Server services any number of Print Queues. The Print Server for Netware is analogous to the UNIX spooler, Print Queues in Netware are analogous to UNIX Printers. Line Printer Daemon (LPD) is the server side of the network printing process (i.e. LPD receives and processes print jobs). Line Printer Remote (LPR) is the client side of the print process (i.e. it sends print jobs to LPD). Both UNIX and FarPRINT can function as either server or client or both. Both LPD and LPR work with a system’s spooler (UNIX or Netware) to submit or collect print jobs. Let’s look at what is happening for each direction of network printing from the perspective of the Netware Server. Local Print (LPD) Local Print: This is when a remote system (UNIX or another LPD/LPR system) sends via LPR a print job to the local Netware Server’s print server - LPD. FarPRINT’s LPD receives the print job from the remote host and stores it as it is received in a directory on the Netware Server. When the transfer is complete, FarPRINT makes any necessary conversions, and passes it to the specified Netware Print Queue (this Netware Queue then sends the print job to the appropriate Netware Print Server). Multiple UNIX print jobs can be sent and processed simultaneously by FarPRINT’s LPD print server. To use Local Print you will need to install and setup LPD/LPR on your remote UNIX or other LPD/LPR system. This will involve setting up the associated LPD/LPR print spooler on the remote system so that it will send print jobs to the IP address of the Netware Server where FarPRINT is installed. The name of the printer on the remote host must be the same name as the printer assigned by FarPRINT and Netware. (FarPRINT converts lower case UNIX names to uppercase Netware queue names) You will also need to (if it is not already done) have Netware configured with a Print Queue for FarPRINT to pass jobs to. Once this is complete, you are ready to print. For example, every time anyone prints to the printer called "nov_que1" on UNIX, print jobs will be transparently printed on the Netware Server’s Print Queue "NOV_QUE1". For detailed information how to configure Local Print see the section titled "Configuring Local Print" later in this manual. Remote Print (LPR) Remote Print: This is the opposite of Local Print. In this case, a Netware Print Server gives a print job via a Print Queue to FarPRINT. FarPRINT picks it from there, makes any necessary conversions, and passes the print job (via LPR) to the UNIX (or another LPD/LPR system) server’s LPD. The UNIX or other LPD system is specified by its name and IP address in the Netware Servers HOSTS file. For example, if a user John wants to print to an Epson printer attached to a UNIX system called "epson1", he would print to the Netware queue "EPSON1" from his application (usually via Novell’s capture command). FarPRINT picks up the print job and transparently moves it to the UNIX spooled printer designated "epson1" (or "EPSON1"). For detailed information how to configure Remote Print see the section titled "Configuring Remote Print" later in this manual. FarPRINT can be configured to print a banner page that displays the name of the user who originated the print job. Printing the banner can be enabled or disabled by a user for both local and remote printers. When printing text files, FarPRINT can provide the proper conversion from DOS to UNIX format (or UNIX to DOS). This feature can be enabled permanently, or permanently disabled, or work in an auto-detect mode. In auto-detect mode FarPRINT tries to automatically determine if a print job is a pre-formatted print file, or a text file and convert the file if necessary. Note: Although auto detection works well in most cases, it is not always possible to recognize if the file is a formatted print job, or plain text. In such cases a user will have to select either the Always Convert or the Do Not Convert option in the options setup of the Local or Remote Print Configuration. All the capabilities described above apply equally when you are using FarPRINT with UNIX or with any other LPD/LPR compliant system (such as NIPrint - LPD/LPR for Winsock from Network Instruments, LLC). WHO SHOULD USE FARPRINT Any Netware LAN with a TCP/IP based UNIX (or other LPD/LPR host) that has the need to share printers in either direction will find FarPRINT useful. FarPRINT allows any UNIX user or application to share printers with Netware and any Netware user to print to a UNIX host. LIMITED WARRANTY Network Instruments, LLC will replace defective media or documentation for 90 days after the shipment of the product from Network Instruments, LLC. Should Network Instruments, LLC release a new version of FarPRINT within 60 days of shipment of the product, Network Instruments, LLC will update the copy of FarPRINT at no charge. This update may consist of disks or a manual or both, at the discretion of Network Instruments, LLC. Network Instruments, LLC shall not be liable for material, equipment, data or time loss, caused directly or indirectly by proper or improper use of the FarPRINT software. In cases of loss, destruction, or corruption of data, Network Instruments, LLC shall not be liable. Network Instruments, LLC does not take any other responsibility. Network Instruments, LLC makes no other warranty. COPYRIGHT AND LICENSE FarPRINT - Network Instruments LPD/LPR Print Server for Netware - is neither freeware nor shareware. This is a commercial software package that is subject to international copyright laws. Network Instruments, LLC reserves all rights on development and distribution of the FarPRINT package. FarPRINT is the property of Network Instruments, LLC and may not be copied for purposes other than backup. Proprietary Rights - This software and documentation are copyrighted by and proprietary to Network Instruments, LLC. You acknowledge that the Software and Documentation contain valuable trade secrets and other proprietary information belonging to Network Instruments, LLC. You agree to hold the software in confidence and to take reasonable steps to prevent disclosure to others. You may not install this software on more than one Netware Server. NO REVERSE COMPILATION IS ALLOWED - You may not modify, translate, disassemble, or decompile the software, or of any copy, in whole or in part. This software is licensed as stated above. The license does not constitute ownership of the software, only the right to use it. A single server FarPRINT is automatically licensed for use on one Netware Server. It can not be shared, passed or sold for commercial or any other use, and can be used on ONE Netware Server only. To purchase additional FarPRINT licenses contact Network Instruments, LLC at: Network Instruments, LLC P.O. Box 581156 Minneapolis, MN, 55458-1156 USA Voice (612) 822-2025 FAX (612) 825-5647 BBS (612) 822-0902 Internet: sales@netinst.com You may use the product called "FarPRINT", or "Network Instruments LPD/LPR Print Server for Netware" only if you agree with the above stated license agreement. How to License If you have obtained a DEMO copy of FarPRINT you do not need to license the software to use it for 21 days. It will function on one Netware Server only, for 21 days. If you would like to use FarPRINT after the 21 day evaluation period, you must purchase a copy of FarPRINT. To purchase contact Network Instruments, LLC or your software dealer or distributor. If you purchased a complete version of FarPRINT you will be asked to license FarPRINT during installation. Your FarPRINT package contains a Right To Use (RTU) document with Identification and License numbers. You will be asked for these numbers during installation. Keep this RTU in a safe place - this is your only proof of purchase. If you would like to run more than one FarPRINT server on your network you will need to purchase additional FarPRINT licenses. SYSTEM REQUIREMENTS A Novell Netware 386 3.11 server or greater running on a 386DX/33 based PC with at least 6 MB RAM and the Netware TCPIP.NLM up and running. FarPRINT may run on servers with less power and RAM than those listed above, but Network Instruments does not support configurations with less than these stated requirements. TECHNICAL SUPPORT Network Instruments provides technical support from 9:00 AM to 5:00 PM Central Standard Time. Technical support is provided on the phone at (612) 822- 2025, by fax at (612) 825-5647, or by email at support@netinst.com. Suggestions are welcomed - submit detailed suggestions in writing to support@netinst.com or by FAX at (612) 825- 5647. INSTALLATION NETWARE TCP/IP REQUIREMENTS FarPRINT is designed to function with Novell Netware’s TCPIP.NLM. Prior to installing FarPRINT, verify that Netware’s TCPIP NLM is up and running. A sample AUTOEXEC.NCF that shows the TCP/IP NLM load procedure is included in the Appendix of this manual. For minimal Netware requirements see the "System Requirements" section in this manual. A good test to see if TCP/IP is loaded and running on your Netware Server would be to use ping on your UNIX system to "ping" the Netware server. If the Netware server replies, TCP/IP is PROBABLY set up correctly. If your Netware server does not respond to the ping, TCP/IP on your Netware server is DEFINITELY not set up correctly. INSTALLING FARPRINT ON THE NETWARE SERVER FarPRINT, FarCONF (the FarPRINT configuration program) and NINSTALL (the FarPRINT installation program) are Netware Server based NLMs (Netware Loadable Modules). All three of these programs run on the Netware Server in much the same way an "EXE" file runs on a DOS or Windows PC. To install the FarPRINT files on the server, run the FarPRINT installation program NINSTALL.NLM from the Netware Server’s console prompt (:) with the following command: :LOAD [drive]:\NINSTALL.NLM Where [drive] is the diskette drive where you have inserted the FarPRINT distribution disk. For example, if you are installing on a server that has the A: drive as its 3.5" floppy, insert the FarPRINT disk in the A: drive, and type: :LOAD A:\NINSTALL.NLM If you do not have an accessible drive on your Netware server, you can copy the FarPRINT files to a temporary directory on the server and run NINSTALL.NLM from this directory. For example, if you copy the FarPRINT files to a directory called TEMP in the \PUBLIC directory, the load line to run NINSTALL would be: : LOAD SYS:\PUBLIC\TEMP\NINSTALL.NLM NINSTALL will respond with a few initial explanatory screens, and - if you are NOT installing the DEMO version of FarPRINT, INSTALL will ask you to enter your Identification and License numbers. Once you tell FarPRINT’s INSTALL to continue, FarPRINT will be installed and ready to be configured on your server. Once FarPRINT is installed (and configured), you can run FarPRINT by loading the NLM FARPRINT.NLM at the Novell Server console. CONFIGURING FARPRINT FarPRINT needs to be configured prior to use. To configure FarPRINT, you will need to load FarPRINT’s configuration NLM - FARCONF.NLM. You can do this after installing FarPRINT by typing: :LOAD FARCONF.NLM at the Netware Server console. The FarCONF initial configuration screen will be displayed. Configuring Local Print (LPD) Local Print allows the FarPRINT LPD server to receive print jobs from remote UNIX hosts or other LPD/LPR systems. To use Local Print, you will need to configure the Local Print services in FarPRINT. In this mode FarPRINT is acting as a "LPD" server. The following is a list of steps to configure one local printer on FarPRINT. If you need to install more than one local printer, repeat the same steps for every printer. Note: This procedure expects that you have at least one Print Queue set up and one Print Server running on Netware. If you do not have any printers set up on your Netware Server, you will need to do so before you can configure FarPRINT’s Local Print. Step 1: Make sure that the "Enable Local Print" is set to "Yes" in the "General Settings" section of the main FarCONF menu. Highlighting the item and pressing return will display a selection box. From the "Selections" menu, choose "HOSTS file IP addresses". Press "Ins" to add the IP address and name of the UNIX system that will be sending print jobs to FarPRINT. This entry will be used when configuring a "Trusted HOST" on the Netware Server (explained below). Step 2: Select the "Local (UNIX to Netware) Setup " menu option from the main FarCONF menu. The "Local (UNIX to Netware) Server" dialog will appear. Step 3: Choose "Trusted Remote Hosts" and add the remote system that you will be printing from by pressing the "Ins" key. This dialog reads the Netware Server’s HOSTS file to get a list of remote hosts that you have entered into the HOSTS file. A "trusted" host is one that the Netware Server will give printing privileges to. This list is analogous to the hosts.equiv or hosts.lpd file on UNIX. [Note: You can edit the HOSTS file on the Netware Server by choosing "HOSTS file IP addresses" from the main FarCONF menu] Next choose the "Print Queues Serviced by LPD" selection to add a new printer. Pressing the "Ins" key will display the active print queues that you have on your Netware Server. Select the print queue that you would like to associate with a UNIX queue and press enter. You should now see the Netware print queue listed on the list of "Print Queues Serviced by LPD". If you would like to configure how FarPRINT will treat print jobs associated with that queue, select the queue (by highlighting it and pressing return). You can then configure various options for the queue. Your choices are: Print Banner Page: "Yes" will force FarPRINT to always print a banner page. "No" turns the banner page option off. Convert DOS-UNIX: Choices are: Autodetect: - this option forces FarPRINT to try to determine whether the print job is text or binary (formatted print stream). If it is text, FarPRINT will make the appropriate LF/CR conversions. If it is binary, FarPRINT will not do any conversions. Note: Autodetect works well in most cases, but for some type of printers it is difficult to determine the nature of the print job, in which case one of the options below should be selected. Always convert - this option should be used only when you are certain that all print jobs from the UNIX system will be text, and the printer interface on the target system does not handle line feeds without carriage returns (laser printers, for example). Do not use this option when printing from UNIX if the UNIX side sends print jobs formatted by the UNIX printer interface. Do not convert - select this option when printing formatted print jobs, or when the remote system is not a UNIX host. The default is "Do not convert". [HINT: If you have print jobs of both types, it is possible to setup more than one queue that prints to the same printer.] Step 4: Once you have made your configuration choices, the FarPRINT queue is ready to use. Exit FARCONF (Esc backs you up in the menu system), and load FarPRINT by running FARPRINT.NLM from the Netware Server console by typing: :LOAD FARPRINT.NLM The main FarPRINT screen will be displayed with your configured Local Print queue. Local Print configuration is now complete. Repeat the previous steps for additional Local Printers. If it was not done previously, you will now need to configure the remote side (the UNIX side) of the connection. For the UNIX host - follow the instructions on installing Remote Line Print Services (LPD/LPR) for remote printing in your UNIX system’s administrator manual. Below we provide a few general checkpoints: 1. Make sure that Line Print Services (LPD) are enabled on your UNIX system. One of the indications that LPD is functioning can be that "lpd" is running in process table. If you are not sure whether Remote Line Print services are installed - just try to install them again. It usually can not hurt. 2. Create a remote printer with the name that was chosen when configuring Local Print on the Netware Server. The length of the name should not be longer then 39 letters. It is recommended that the name be 8 letters or shorter. It should contain only alphanumeric characters. 3. Configure the remote printer entry for the IP address of the Netware Server where you have installed FarPRINT. For more details on configuring UNIX’s LPD/LPR refer to your UNIX manual. Configuring Remote Print (LPR) Remote Print allows FarPRINT to send print jobs from a Netware Server’s print queue to a remote UNIX host or other LPD/LPR system. To use Remote Print, you will need to configure the Remote Print services in FarPRINT. In this mode, FarPRINT is acting as a "LPR" client. The following is a list of steps to configure one remote printer on FarPRINT. If you need to install more than one remote printer, repeat these steps for each printer. Note: This procedure expects that you have at least one Print Queue set up and one Print Server running on Netware. If you do not have any printers set up on your Netware Server, you will need to do so before you can configure FarPRINT Local Print. Step 1: Make sure that the "Enable Remote Print" is set to "Yes" in the "General Settings" section of the main FarCONF menu. Highlighting the item and pressing return will popup a selection box. Step 2: Select the "Remote (Netware to UNIX) Setup " menu option from the main FarCONF menu. The "Remote Printers Serviced by FarPRINT" dialog will appear. If this is the first Remote printer you are adding, no printers will be displayed in the "Remote Printers Serviced by FarPRINT" dialog. Press the "Ins" to display the "REMOTE Printer Configuration" dialog. REMOTE Printer Name: this is the name that you have specified for the UNIX queue on the target host. REMOTE Host: this is the name of the UNIX host that is specified in the HOSTS file on the Netware Server. [Note: You can edit the HOSTS file on the Netware Server by choosing "HOSTS file IP addresses" from the main FarCONF menu]. Netware Queue: highlighting this choice and pressing return will display a list of Netware Queues that you can associate with a UNIX queue. Choose a queue by highlighting the queue entry and pressing return. This will add the Print Queue to the "Netware Queue" line. Print Banner Page: "Yes" will force FarPRINT to always print a banner page. "No" turns the banner page option off. Send Raw Print Jobs: Sets the "Raw" flag in the LPD/LPR command file. This tells the UNIX systems interface file to treat the file as raw and do not process it any further (ONLY if the interface file supports this option). If this is set to "Yes" the Convert DOS-UNIX flag is automatically set to "Do note convert". Convert DOS-UNIX: Choices are: Autodetect: - this option sets FarPRINT to try to determine whether the print job is text or binary (formatted print stream). If it is text, FarPRINT will make the appropriate LF/CR conversions. If it is binary, FarPRINT will not do any conversions. Note: Autodetect works well in most cases, but for some type of printers it is difficult to determine the nature of the print job, in which case one of the options below should be selected. Always convert - this option should be used only when you are certain that all print jobs from the UNIX system will be text, and the printer interface on the target system does not handle line feeds without carriage returns (laser printers, for example). Do not use this option if the print job is going to a UNIX system formatted for the current UNIX printer interface. Do not convert - select this option when printing formatted print jobs, or when the remote system is not a UNIX host. The default is "Do not convert". Step 3: Once you have made your configuration choices, Remote Print is ready to use. Exit FARCONF (Esc backs you up in the menu system), and load FarPRINT by running FARPRINT.NLM from the Netware Server console by typing: :LOAD FARPRINT.NLM The main FarPRINT screen will be displayed. Press "Esc" to switch to the LPR screen and your configured Remote Print queue will be displayed. This completes the Remote Printer configuration of FarPRINT. Now, if it was not done previously, you will have to configure the remote side of the connection. Make sure that you have entered the name of the Netware Server in the HOSTS file on your UNIX host. This should be entered in uppercase. For example, if your Novell systems name is MYSERVER, the HOSTS file entry on UNIX would be: 200.200.200.2 MYSERVER (Note: Your Netware servers IP address will be different.) If the remote side is a UNIX host - follow the instructions on how to install Line Print Services (LPD/LPR) for local printing in your UNIX system administrator’s manual. Below we provide a few general checkpoints: 1. Make sure that Line Print Services (LPD) are enabled on your UNIX system. One of the indications that the service is running can be that "lpd" is running in the process table. If you are not sure whether Remote Line Print services are installed - just try to install them again. It usually can not hurt. 2. Make sure that the printer you want to receive remote print jobs on is printing correctly from the UNIX command prompt. If it does not, fix this problem first. 3. Create a printer entry on the remote system that will receive remote print jobs with the name that was chosen when configuring Remote Print on the FarPRINT server. The length of the name should not be longer then 39 letters, and is recommended to be 8 letters or shorter. It should contain only alphanumeric characters. 4. Make sure that the name of the Novell Server that has FarPRINT configured for remote printing is present in the files hosts.equiv, hosts.lpd, or other file specific to your UNIX system. For more details on LPD/LPR refer to your UNIX manual. USING FARPRINT Once FarPRINT is configured, there is very little required to print either from UNIX to Netware or Netware to UNIX. After loading FarPRINT at the Netware Server, it should service print jobs in both directions without any user intervention. Each process’s queues (LPD and LPR) are displayed on the Netware Server’s console. You can switch from LPD to LPR by pressing the "Esc" key. Each display shows 12 queues, and can show an additional 12 queues by pressing the 1,2,3, or 4 number keys on the console. The FarPRINT NLM can be unloaded by typing: :UNLOAD FARPRINT.NLM at the Netware Server’s console. APPENDIX DEBUG OPTION The FarPRINT has the following options for debug mode: LOAD FARPRINT.NLM -debug This turns on the debug output. In debug mode, FARPRINT generates two debug files. They are: LDEBUG - for local print RDEBUG - for remote print These files are placed in the SYS:/ETC/NI directory. The debug files will chronicle the complete negotiation and communication of FarPRINT and the remote system. Should you have problems with printing, this information may be useful for determining at what point the process breaks down. The sample files below show a SUCCESSFUL transfer of a print job - both for LPD (LDEBUG) and for LPR (RDEBUG). LDEBUG: Thu Dec 8 12:00:36 1994 Accepted connection from: 200.200.200.90 Thu Dec 8 12:02:28 1994 [03] Send Queue Status (short), printer: ROMAN13 Sent Queue status reply Accepted connection from: 200.200.200.90 Thu Dec 8 12:02:31 1994 [02] Receive Print Job, printer: ROMAN13 [2.02] Receive Control File Failed to open directory for read: \ETC\NI\IN\ROMAN13\I*.*, or no files found Created Info file: \ETC\NI\IN\ROMAN13\I0001151 Received file, closing it Sent positive ACK to REMOTE lpd [2.03] Receive Data File Opened DIR: \ETC\NI\IN\ROMAN13 Found file: I0001151 Found Info file: \ETC\NI\IN\ROMAN13\I0001151 Received file, closing it Sent positive ACK to REMOTE lpd Both Command and Data files present, closing connection Spoolled Data File for ROMAN13. [2.0X]: Closed connection RDEBUG: Queue: ROMAN13, jobs: 1. Thu Dec 8 12:02:34 1994 bound to local port 721 CheckPrintQueue: Connected to host: 200.200.200.2 CheckPrintQueue: Sent queue status request. CheckPrintQueue: Remote closed connection. ResetFD: Orderly, remote initialized CheckPrintQueue: Request completed, connection closed. bound to local port 721 Connected to host: 200.200.200.2 Sent Receive Print Job command [02] Receive Print Job command successful. Sent 'Receive Command File' command Sent Command File Remote comfirmed reception of Command File Data file: \system\0C000002.QDR\000C0001.Q Print job size: 1071344 bytes Sent 'Receive Data File' command: 1071344 dfA000ROMAN1 Received positive reply on 'Receive Data File' command Sent Data File Remote comfirmed reception of Data File ResetFD: Forceful, locally initialized SAMPLE AUTOEXEC.NCF The following is an example AUTOEXEC.NCF from a Netware Server at Network Instruments. Yours will be different. FILE SERVER NAME NETWORK IPX INTERNAL NET 1 LOAD TCPIP LOAD C:\WD\SMCPLUSS PORT=280 FRAME=ETHERNET_802.3 NET=20 NAME=E_802.3 LOAD C:\WD\SMCPLUSS PORT=280 FRAME=ETHERNET_II NET=5 NAME=E_2 BIND IPX TO E_802.3 BIND IP TO E_2 ADDR=200.200.200.200 LOAD PSERVER NI_PRSERV LOAD RSPX Note the two "LOAD lines are spit due to the margins of this manual, not by syntax. PROGRAM DESCRIPTIONS FarPRINT is a Novell Netware Netware Loadable Module (NLM) based program that provides bi-directional LPD/LPR capabilities to any Netware 3.11 or greater server. FarPRINT’s main components are: FARPRINT.NLM - the FarPRINT NLM program FARCONF.NLM - FarPRINT’s configuration NLM NINSTALL.NLM - FarPRINT’s installation NLM The FarPRINT configuration, data files and storage directories are installed into the SYS:/ETC/NI directory. The FARPRINT.NLM and FARCONF.NLM programs are installed into the SYS:/SYSTEM directory. OVERVIEW OF THE LINE PRINTER DAEMON PROTOCOL (LPD) Line Printer Daemon Protocol (LPD/LPR) is a TCP/IP based protocol that enables remote systems to share their printers through the network. Because it has clear and simple set of commands, LPD/LPR provides one of the best printing protocols currently available. Because it is a standard in the UNIX community it will work across many UNIX platforms. LPD/LPR does not have any security provisions and may not be suitable for networks where it is crucial that no data is transferred in a non-encoded format. If your system does not use encoding for your terminal sessions, there should be no reason to worry about LPD being unsecure. LPD protocol contains a set of requests for information or directives to receive data, and replies to them. The Line Printer Daemon itself listens on TCP port 515. The remote system that calls the LPD uses ports in the range from 721 to 731. The daemon that requests LPD services is usually called LPR. When LPD receives a request from LPR to accept a print job, it checks whether the requested printer queue exists on the system, and if it exists, sends confirmation that it is ready to receive a print job. Then in a series of requests and replies, two files are transferred to LPD. One file is the print job itself - by convention this file is called a data file. The other file contains a description of the print job and information of how to process the job on the remote system. This file is called the command file. Both data and command files can be received in any order, and as soon as both are received by LPD, the print job is ready to be printed on the specified printer. (c) 1994 Network Instruments, LLC