PrintNet™ User’s Manual 5525B/31/32 Line Matrix Printer
READ THIS SOFTWARE LICENSE AGREEMENT BEFORE USING THIS PRINTER Software License Agreement Disclaimer of Warranties and Limitation of Remedies CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING THIS PRINTER. USING THIS PRINTER INDICATES YOUR ACCEPTANCE OF THESE TERMS AND CONDITIONS. IF YOU DO NOT AGREE TO THESE TERMS AND CONDITIONS, PROMPTLY RETURN THE PRINTER AND ALL ACCOMPANYING HARDWARE AND WRITTEN MATERIALS TO THE PLACE YOU OBTAINED THEM, AND YOUR MONEY WILL BE REFUNDED. 1.
5525B/31/32 Line Matrix Printer PrintNet™ User’s Manual P/N 422720-001
This document contains proprietary information protected by copyright. No part of this document may be reproduced, copied, translated or incorporated in any other material in any form or by any means, whether manual, graphic, electronic, mechanical or otherwise, without the prior written consent of Compaq®. Compaq makes no representations or warranties of any kind regarding this material, including, but not limited to, implied warranties of merchantability and fitness for a particular purpose.
Trademark Acknowledgements IGP, LinePrinter Plus, PGL and Printronix are registered trademarks, and PrintNet is a trademark of Printronix, Inc. Compaq is a registered trademark of Compaq Computer Corporation. AIX, AS/400, and OS/2 are registered trademarks, and AFP, Intelligent Printer Data Stream and IPDS are trademarks of International Business Machines Corporation. Netscape, Netscape Navigator, and the Netscape Communications logo are trademarks of Netscape Communications Corporation.
Table of Contents 1 Introduction ............................................. 11 Overview..............................................................................11 What is the PrintNet? ....................................................11 What Special Features are Available? ..........................11 Indicators.......................................................................12 Operating Modes...........................................................13 Conventions Used In This Manual .....
Table of Contents Windows NT 3.51 Host Setup .......................................33 Windows NT 4.0 Host Setup .........................................34 Windows 95 Host Setup................................................39 Printronix Printing System (PPS) Host Setup ...............40 Windows 3.1 Host Setup...............................................41 Windows Troubleshooting Tips ...........................................42 IPAssign Cannot Find the PrintNet ...............................
Table of Contents PrintNet Will Not Talk on the Network...........................62 Nothing Prints................................................................63 Stair-Stepped Output ....................................................64 No Form Feed or Extra Page Comes Out.....................64 TCP/IP Access Problem................................................65 5 Novell Configuration ............................... 67 Overview.......................................................................
Table of Contents AS/400 Configuration ..........................................................90 Procedure .....................................................................90 Example ........................................................................91 8 Commands.............................................. 99 Command Shell Overview ...................................................99 npsh Access Methods ...................................................99 Main npsh Command Prefixes ........
1 Introduction Overview This chapter introduces you to the PrintNet™ architecture and special features, as well as providing information on installation and configuration tools. What is the PrintNet? The PrintNet print server allows you to attach printers on a local area network (LAN) rather than attaching them directly to a host system.
Chapter 1 Overview • numerous printer logging methods (e.g. automatic email) to record printer errors and usage • remote management through HTML forms, Telnet sessions, “rsh/ rcmd/remsh” commands, SNMP, and pre-defined log methods • • • extensive built-in troubleshooting tools • multiple destinations/queues for versatile printer manipulation and distinct print setups • header and trailer strings to instruct printers on font, pitch, printing, etc.
Operating Modes Table 1. LED Pattern Indications STAT ERR NET Mode ON OFF ON RAM Test ON OFF OFF ROM Test ON ON OFF EEPROM Test OFF ON ON Network Interface Test OFF OFF ON PRN1 Test FLASH OFF FLASH Run Mode FLASH ON FLASH Auto Reset Mode FLASH FLASH OFF Firmware Panic ON FLASH ON Hardware Exception Operating Modes The PrintNet has a self test and internally controlled modes.
Chapter 1 Overview Run and Auto Reset Modes Run Mode is the normal operating state of the PrintNet. Auto Reset mode is entered when the watchdog timer is triggered and the Print Server resets itself. In either mode, the STAT LED flashes at a varying rate, depending on whether the unit IP address is configured. The Run Mode and Auto Reset Mode indicator descriptions are given in Table 2. Refer to the Glossary for definitions. Table 2.
2 Installation and Configuration Installation The PrintNet is unique in that different network connection options are available upon purchase. The base PrintNet model provides an RJ-45 connector for 10Base-T (UTP) networks. A 10Base2 version of the adapter is also available. Connecting to the Network To attach the PrintNet to a network as illustrated in Figure 2, plug the network cable into the PrintNet connector.
Chapter 2 Installation $ $ Network Connector Figure 2.
IPAssign Configuration Tools There are two parts to a PrintNet setup: 1. Configuring the PrintNet so it can be seen on the network. This involves network related settings (e.g. an IP address within TCP/IP environments) configured through the built-in command shell, npsh, or from the control panel. 2. Configuring a host with a new printer so it knows how to send data to the PrintNet. Just being able to see the printer on the network does not mean you can automatically print to it.
Chapter 2 Configuration Tools HTML Forms The PrintNet settings can be configured over TCP/IP through a standard Web browser. The PrintNet Web pages provide a handy way to access some of the commands built in to the print server. NOTE: If a router is used, make sure a gateway value is configured. To access the PrintNet home page: 1. Make sure the print server has an IP address and subnet mask so it is recognizable on your TCP/IP network. 2.
HTML Forms Printer Status Screen Using the printer IPAddress and any standard web browser, you can check the status of the printer. Figure 5 shows the exact state of the printer by showing the printer LCD message. Figure 5.
Chapter 2 Configuration Tools Configuration Alternatives Besides the HTML forms and software provided, the PrintNet internal command shell, npsh, can also be reached using these methods: Telnet A TCP/IP command that helps configure PrintNet settings remotely. A TCP/IP host starts a Telnet session with the print server and logs in to the device command shell to alter and view settings. Example: telnet 192.75.11.9 Remote Shell A TCP/IP command that helps configure print server settings remotely.
3 Windows Configuration Overview This chapter details a complete Windows configuration setup including: 1. Identifying the PrintNet on the network using TCP/IP as the underlying protocol 2. Configuring the PrintNet with its mandatory TCP/IP settings (IP address and subnet mask) 3. Configuring a new printer on the Windows station Windows Environment Description The PrintNet supports network printing under Windows environments by using TCP/IP.
Chapter 3 Windows PrintNet Configuration Win 95 Win 95 Win 95 Win 95 NT Server IP Router Win 95 Figure 6. Windows Integration Windows PrintNet Configuration The IP address and subnet mask are mandatory TCP/IP settings and are needed before the print server can be detected on the network. There are also additional settings which are optional. This section offers alternative methods for configuring your PrintNet in a Windows environment and mentions some of the more common optional settings available.
Optional Optional Additional settings, like routing entries, can be configured. This allows communications across subnets. Configuration of the PrintNet can be done from the printer control panel, IPAssign, Web browser, or host commands. Configuration Using the Control Panel You can set any of three listed parameters from the printer control panel. These parameters are located in the Ethernet™ Parameters menu.
Chapter 3 Windows PrintNet Configuration 11. Press the ENTER key to make the selection. An asterisk appears to the right of the value. 12. Press the UP arrow key and you will be returned to step 8. 13. When you are finished changing parameters, exit the configuration menus and lock the ENTER key. (Refer to your printer’s User’s Manual for details.) Configuration Using IP Assign NOTE: You must have the TCP/IP protocol and services enabled on this windows station first.
Configuration Using IP Assign 8. At the “IPAssign” main dialogue box that appears, you should see an entry for your PrintNet appear in the list box. Figure 7 shows an example screen. Figure 7. IPAssign Main Screen 9. Once your PrintNet Ethernet Address appears in the list box, select it and click on ASSIGN. 10. At the “Assign IP” dialogue box that displays next, fill in the IP address and subnet mask for this PrintNet.
Chapter 3 Windows PrintNet Configuration 13. If you want to store the TCP/IP settings into the PrintNet flash memory via a browser, click on LAUNCH BROWSER at the next window that displays. This will prevent you from losing the settings after a power cycle. If not, click “No.” 14. Read the text in the “Configuration Information” window that displays and click OK to launch your Web browser. NOTE: If you are returned to the IPAssign main dialogue box, you will be unable to launch your browser this way.
Configuration Using IP Assign Figure 8.
Chapter 3 Windows PrintNet Configuration At this point, the TCP/IP settings are stored in flash memory and you should be able to see the PrintNet on your Windows network. However, you can not print to it yet since you have not identified the network printer to your Windows station. Refer to “Windows Host Configuration” on page 33 to identify the network printer to the Windows station. Configuration Using ARP To configure the PrintNet with its IP settings using a manual “arp” command: 1.
Configuration Using ARP At this point, you should be able to communicate with the PrintNet from your local Windows station. This means the print server knows about an IP address and subnet mask and has these settings in its current memory. However, if the PrintNet is power cycled, these settings will disappear unless you store them into flash memory. To do this: 1. Load a Web browser on your Windows station and direct it to the URL “http://PrintNetIPaddress/networkConf.html” (e.g. “http://192.75.11.
Chapter 3 Windows PrintNet Configuration Communicating Across Routers Since Windows environments rely on TCP/IP to communicate with the PrintNet, crossing routers becomes an issue. After following one of the PrintNet configuration methods mentioned, you will most likely only be able to communicate with the print server from the same subnet. This means any hosts across a router will not be able to see your PrintNet.
Changing Workgroup Names Changing Workgroup Names Windows environments define groups of related computers as “workgroups.” By default, the PrintNet belongs to the workgroup called “WORKGROUP”. However, you may want to change this to suit your network better. To do this: 1. Load a Web browser on your Windows station and direct it to the URL “http://PrintNetIPaddress/networkConf.html” (e.g. “http://192.75.11.9/networkConf.html”).
Chapter 3 Windows PrintNet Configuration The first field requires the IP address for the PrintNet and the second field must be filled in with an existing destination from the print server (e.g. d1prn). Otherwise, the PrintNet will not accept this as a valid network printer. Table 3 outlines the default destinations to choose from. Table 3.
Windows NT 3.51 Host Setup Windows Host Configuration This section covers Windows NT and Windows 95, Windows 3.1 and Printronix Printing System (PPS) new printer setups. Windows NT 3.51 Host Setup To configure a new printer on a Windows NT 3.51 station: 1. Open the “Control Panel.” 2. Double click on “Printers.” 3. Select “Create a Printer” from the “Printer” menu to display the dialogue box in Figure 10. Figure 10. Create a Printer Dialogue Box 4.
Chapter 3 Windows Host Configuration 6. Select “LPR Port” from the list that displays and click OK to bring up a dialogue box similar to the one found in Figure 11. Figure 11. Add LPR Compatible Printer Dialogue Box 7. Type in the IP address or host name of the PrintNet in the first field. 8. Type in the name of a pre-defined destination/queue on the PrintNet in the second field. NOTE: This name must be a name of an existing destination/queue on the PrintNet and it must be lowercase by default.
Windows NT 4.0 Host Setup 3. Select “My Computer”. 4. At the next window, click on “Add Port ...”.
Chapter 3 Windows Host Configuration 5. Double click on “LPR Port”. If LPR Port is not listed it means that Microsoft TCP/IP Printing service is not installed. 6. In the “Name or address of server providing lpd:” box, enter the IP address of the PrintNet adapter. In the “Name of printer or print queue on that server:” box, enter d1prn.
Windows NT 4.0 Host Setup 7. Select the “Generic/Text only” printer driver or install the Printronix P5000 series driver from the Printronix web page at www.printronix.com. The generic driver is good for troubleshooting installation problems. The network administrator can always go back and install the P5000 driver at a later time. 8. In the “Printer Name” box, enter a name for this printer.
Chapter 3 Windows Host Configuration 9. Determine if the printer is shared with other network users. If it is shared, the share name and the operating system must be selected. 10. Print a Windows test page. 11. If there are any problems during or after installation, see “Windows NT 4.0 Host Setup Problems” on page 47.
Windows 95 Host Setup Windows 95 Host Setup To configure a new printer on a Windows 95 station: 1. Select “Settings:Printers” from the “Start” menu. 2. Double click on the “Add Printer” icon. 3. Select “Network Printer” from the second window of the “Add Printer” wizard that loaded. 4. At the next window, click on BROWSE to help fill in the network path of this printer. 5. At the “Browse for Printer” dialogue box that displays, double click on the appropriate workgroup containing the PrintNet.
Chapter 3 Windows Host Configuration Printronix Printing System (PPS) Host Setup To configure a new PPS printer on a Windows station, you will need to: 1. Insert the diskette labeled “PPS” into the floppy drive. 2. Load the File Manager or WinFile and look under the floppy drive for a PPS ZIP file. 3. Double click on the PPS ZIP file to extract all files within it to a directory on the Windows station. 4.
Windows 3.1 Host Setup 15. Click OK when done to return to the “Details” window. You should now see something relating to “PPS Port” within the “Print to the following port:” field. 16. Click OK to close this printer properties window. You now have a new network printer which relies on PPS to print remotely to a printer off of the PrintNet. Windows 3.1 Host Setup If you are running Windows 3.1 stations on your network, you will need to rely on either TCP/IP or IPX to print to the PrintNet.
Chapter 3 Windows Troubleshooting Tips Windows Troubleshooting Tips This section provides information on possible solutions to some standard configuration errors. If you require technical support, please have as much of the following information as you can available when you call: 1. What level of software are you running? 2. What type of attachment do you have? 3. What is your host operating system? 4. Give a detailed description of the problem. 5. How often, and when, does the problem occur? 6.
PrintNet Will Not Talk on the Network PrintNet Will Not Talk on the Network • Have you assigned the PrintNet a unique and valid IP address which corresponds with the other IP addresses on your network? For example, are you sure no other device is using this IP address? • Are you sure you are trying to talk to the PrintNet from a Windows station on the same subnet? Currently, the print server can only be seen locally unless you configured a routing entry earlier.
Chapter 3 Windows Troubleshooting Tips Can Not Browse the PrintNet on the Network • Have you looked under the right Windows workgroup? By default, the PrintNet will be found under “WORKGROUP.
TCP/IP Access Problem TCP/IP Access Problem If you can “ping” the printer from a workstation, but you cannot Web browse, Telnet, or print to the printer through the PrintNet, there may be an incorrect entry in the TCP access list. In order for this workstation to use the PrintNet interface in this case, one of two things must happen. 1. The TCP list must have an entry added to grant access to this workstation. 2.
Chapter 3 Windows Troubleshooting Tips 6. From a workstation attached to this network segment, create an ARP entry. The PrintNet IP address and hardware or MAC address are needed. At the workstation enter: arp -s ping 7. Try to “ping” this IP address to see if the PrintNet can be seen on your network. If the interface does not respond, verify you are on the same network segment as the printer and that the ARP entry was created. 8.
Web Browser/HTTP Problem Web Browser/HTTP Problem In some cases you may not be able to browse the printer web page simply because the PrintNet HTTP may be turned off. If you can not “ping” the PrintNet IP address, make sure the IP Address, subnet mask, and default gateway are set correctly by checking the Ethernet Parameters menu from the operator panel. See the User’s Manual for configuration menu information.
Chapter 3 Windows Troubleshooting Tips • Are you logged in as the “Administrator”? This installation requires administrator privileges. • “LPR port” is not listed in step 5. Cancel the installation and install Microsoft TCP/IP printing service on the server. • LPR configuration warning during step 6. The ethernet cable is not plugged in, or printer is not turned on. This message is a communication failure between the NT server and the PrintNet card. Check cabling, IP address settings, gateway, etc.
4 Unix Configuration Overview This chapter details a complete Unix setup including: 1. Configuring the PrintNet with its mandatory TCP/IP settings (i.e. IP address and subnet mask). 2. Configuring the Unix host station with a new printer. Unix Environment Description The PrintNet supports network printing under various TCP/IP environments including all variations of Unix. Printing can come from multiple hosts directly or through central spooling machines. Figure 12 illustrates this.
Chapter 4 Unix Environment Description Linux XTerm PC PC PC XTerm Solaris Ultrix OSF/1 IRIX SparcStation SunOS 4.1.1 IP Router SCO HP-UX Figure 12.
Mandatory Unix PrintNet Configuration There are mandatory settings needed before the print server can be detected on the network, as well as some additional optional settings. This section offers alternative methods for configuring your PrintNet and mentions some of the more common optional settings available. Mandatory Since TCP/IP is used, the PrintNet must be configured, at a minimum, with an IP address and subnet mask before it can be seen on the network.
Chapter 4 Unix PrintNet Configuration The procedure for changing any of the parameters is the same. The procedure for changing the IP Address is given here as an example. Use the same procedure for the other required parameters. To change the IP Address parameter, proceed as follows: 1. Make sure the printer is on and raise the printer cover. 2. Press the ONLINE key to place the printer in the OFFLINE mode. 3. Unlock the ENTER key. Refer to the User’s Manual for instructions. 4.
Using ARP Using ARP To configure the Ethernet Interface with its TCP/IP settings using a manual “arp” command, the syntax is: arp -s ipaddress ethernetaddress For the “aix” command, the syntax is: aix -s ether ipaddress Mac_address To use either of these commands: 1. Log on to a Unix station as superuser or root. This station must be located on the same subnet as the PrintNet since ARP is limited to subnets. 2.
Chapter 4 Unix PrintNet Configuration At this point, you should be able to communicate with the PrintNet from your local Unix station. This means the printer knows about an IP address and subnet mask and has these settings in its current memory. However, if the PrintNet is shut off, these settings will be lost unless you store them in flash memory, as follows: 1. Load a Web browser on your Unix station and direct it to the URL “http://PrintNetIPaddress/networkConf.html” (e.g. “http://192.75.11.
Using RARP Using RARP RARP allows you to dynamically assign an IP address to the PrintNet upon bootup. To configure the PrintNet with its TCP/IP settings using RARP: 1. On your RARP server, make an entry in the /etc/ethers file for the PrintNet. Syntax: ethernetaddress PrintNetIPaddress Example: 00:80:72:07:00:60 192.75.11.9 2. Start the RARP daemon on the RARP server if not already running.
Chapter 4 Unix PrintNet Configuration Using BOOTP BOOTP allows you to dynamically assign an IP address to the PrintNet upon bootup. In addition, the BOOTP server can provide additional details like a default router/gateway address. To configure the PrintNet with its TCP/IP settings using BOOTP: 1. On your BOOTP server, make an entry in the /etc/bootptab file for the PrintNet.
Communicating Across Routers NOTE: You will be able to communicate with the PrintNet from network stations on different subnets if the print server has been told about its default router/gateway in the BOOTP response from the BOOTP server. Communicating Across Routers Since Unix environments rely on TCP/IP to communicate with the PrintNet, crossing routers becomes an issue.
Chapter 4 Unix Host Configuration Unix Host Configuration There may be times when you would prefer to or have to perform the manual setup steps for a new printer definition. There may also be times when you require a less common print solution such as direct socket capabilities. This section covers these additional setups. Manual System V Host Setup This setup involves any Unix operating system using System V print spooling (e.g. SCO, Solaris, HP-UX, DG/UX, etc.).
Manual LPR/LPD Host Setup To manually configure an LPR/LPD printer on a BSD Unix system: 1. Define an entry for this new printer within the printcap file, /etc/ printcap.
Chapter 4 Unix Host Configuration Example: chmod -R g+rwX,o+rX /usr/spool/lpd/ P5000 chmod -R daemon.daemon /usr/spool/lpd/ P5000 5. Start the printer daemon for this new printer. Example: lpc start P5000 You now have a new printer which relies on LPR/LPD to print to a PrintNet printer. Use the following command to test printing: Syntax: lpr -printername filename Example: lpr -P5000 /etc/hosts Printing from AIX Version 4.0 and higher of AIX offers LPR/LPD support for network printing.
Direct Socket Printing 3. Log in as “root”. 4. At the password prompt, press ENTER since there is no default password. 5. Change to the dest directory. Syntax: cd dest 6. List the contents of this directory using the “dir” command and determine which destination/queue you would like to send the print job through. Most likely you will select “d1prn” for the PRN port. 7. Change to this destination directory. Example: cd d1prn 8. Change the mode to correspond with the type of file you are going to print.
Chapter 4 Unix Troubleshooting Tips Though the host will be sending directly to a TCP port number on the PrintNet, the port numbers are still mapped to destinations/queues in case there is some type of special processing or logging to be done to the job. However, the destination name is of no concern in this type of printer definition. Only the two parameters mentioned above need to be defined for printing to work.
Nothing Prints faster rate says it knows nothing about this so you may need to try the configuration process again. • Have you confirmed that the network connection to the PrintNet is working correctly? Trying different network cables and locations will help narrow down the problem. Nothing Prints • Can you “ping” the PrintNet from your Unix station? If not, please refer to “PrintNet Will Not Talk on the Network,” above.
Chapter 4 Unix Troubleshooting Tips Stair-Stepped Output Stair-stepped output is print which starts at the top left of the page but every line thereafter starts a little further over to the right. It also refers to Unix jobs that print one line of text at the top of a page followed by a series of blank pages. This kind of output happens only with Unix text jobs if carriage return insertion is not incorporated into the print setup.
TCP/IP Access Problem For example, if printing to the destination, d2prn, the associated model is m2. Therefore, the command is: set model m2 trailer $FF save For default destination model mappings of the PrintNet, please see “PrintNet Naming Schemes” on page 128. TCP/IP Access Problem If you can “ping” the printer from a workstation, but you cannot Web browse, Telnet, or print to the printer through the PrintNet, there may be an incorrect entry in the TCP access list.
Chapter 4 Unix Troubleshooting Tips 3. On the PrintNet, place SWITCH 2, the center switch, in the down position. 4. Power on the printer and wait for the READY state. 5. On the PrintNet, place SWITCH 2, the center switch, in the up position. 6. From a workstation attached to this network segment, create an ARP entry. The PrintNet IP address and hardware or MAC address are needed. At the workstation enter: arp -s ping 7.
5 Novell Configuration Overview This chapter details a complete Novell setup including: 1. Identifying the PrintNet on the network. 2. Configuring the PrintNet with its mandatory print setup settings. 3. Configuring a new print queue on the file server. Novell Environment Description The PrintNet supports network printing under Novell environments by using IPX. It supports all 3.1X versions of NetWare. Figure 13 provides a Novell setup overview. Version 4.1X is supported under bindery emulation only.
Chapter 5 Novell PrintNet Configuration NetWare Workstation NetWare 4.1 File Server NetWare 4.1 File Server NetWare Workstation NetWare Workstation Bridge/ Router NetWare Workstation Figure 13. Novell Integration Novell PrintNet Configuration Under all Novell environments, the PrintNet does not require any network settings to make it visible on the network. Simply plug it in to your network and power it on.
Using HTML Forms Using HTML Forms When defining a new print queue on a Novell file server, a new print server must be defined to represent the PrintNet. This name must match the pre-defined name given to the print server. By default, this name is in the format “M_xxxxxx” where “xxxxxx” equals the last six digits of the PrintNet Ethernet address found on a configuration printout or control panel settings under Ethernet parameters, MAC Address (e.g. M_071C1A).
Chapter 5 Novell Host Configuration Novell Host Configuration Under all versions of NetWare, both PSERVER and RPRINTER setups are supported by the PrintNet. Since a PSERVER setup is the most common, you will find the necessary steps to configure the PrintNet as a PSERVER shown first. Configuration for RPRINTER and NPRINTER setup follow the PSERVER information. NOTE: The PrintNet can service up to four printers on one file server. It can not service multiple file servers at one time. NetWare Version 3.
NetWare Version 3.x PSERVER Setup 13. Select the first item listed as “NOT INSTALLED” and press ENTER. 14. At the printer configuration window, type in the name for this new printer. This name must be one of the pre-defined destinations/ queues on the PrintNet. This will normally be “d1prn”. 15. Go to the “Type” field and press ENTER to see the possible choices. 16. Select “Defined Elsewhere” from this list. 17. When done, press ESCAPE and select “Yes” to save the changes to this new printer. 18.
Chapter 5 Novell Host Configuration NetWare Version 3.x RPRINTER Setup These steps are for Novell environments with Netware 3.x (or earlier) file servers. To configure a new RPRINTER on a NetWare 3.x network: 1. Log in to the PrintNet command shell, npsh, as root. If you have TCP/IP available and this print server already has an IP address stored within it, you can use the built-in HTML configuration forms or a Telnet session. Please see “Configuration Tools” on page 17 for further details.
NetWare Version 3.x RPRINTER Setup 7. Press INSERT to add a new queue to the list of currently defined queues. 8. Type in the name of this new queue when prompted and press ENTER. This can be any name you would like. 9. Press ESCAPE to return to the Main Menu. 10. Select “Print Server Information” and press ENTER. 11. Press INSERT when the list of existing print servers displays. 12. Select the print server that you want the PrintNet to service as an RPRINTER. This is the PSERVER.NLM loaded in step 4. 13.
Chapter 5 Novell Host Configuration 28. Wait two minutes and then check your PSERVER to see if the appropriate printer is being serviced. The PSERVER should indicate that the printer is “Waiting for job.” At this point, the PrintNet knows to receive any jobs this PSERVER.NLM has to send to it through the defined printer. NetWare Version 4.x PSERVER Setup PrintNet destinations are case sensitive and will not be recognized if they are typed incorrectly. By default, they are all lower case.
NetWare Version 4.x PSERVER Setup 12. Select PRINTERS. 13. Press INSERT to add a printer to the list. 14. Type in the name of one of the default destinations on the unit for the NAME field and go to the type field. 15. Press ENTER at this field and select DEFINED ELSEWHERE. If DEFINED ELSEWHERE is not available, choose PARALLEL. 16. Press ENTER on the Print Queues Assigned field. 17. Press INSERT to display all queues; select the one you defined in step 5 and press ENTER. 18.
Chapter 5 Novell Host Configuration npsh unitname command Initiates a single Command with guest access only to the unit instead of entering into a complete session. To communicate with the unit using npsh.exe: 1. From a DOS prompt on a Novell workstation, begin an npsh session with the unit. npsh unitname Starts a Telnet-like session with the named print server with guest access only. 2.
NetWare Version 4.x RPRINTER Setup NetWare Version 4.x RPRINTER Setup PrintNet can be configured to service both RPRINTER, NDS mode, and PSERVER, bindery mode. Use the following procedure to set up an RPRINTER form of attachment on a 4.x server: 1. PrintNet requires a bindery server login on the 4.1x as the first step to servicing RPRINTER. This bindery login is necessary for registering the PrintNet Pserver name; no bindery queues or printers are setup.
Chapter 5 Novell Host Configuration 3. At a 4.1x console session, if a pserver.nlm session is already running for Fin_Q, first unload it, then reload it to find the new objects, or, simply issue load pserver Fin_Q. If you are successful the print server console screen will show a “printer status” option. In the “printer status” window, note the numbers assigned to the printers you created.
NetWare 3.x - No PSERVER Connection Novell Troubleshooting Tips This section provides information on possible solutions to some standard configuration errors. If you require technical support, please have as much of the following information available when you call: 1. What level of software are you running? 2. What type of attachment do you have? 3. What is your host operating system? 4. Give a detailed description of the problem. 5. How often, and when, does the problem occur? 6.
Chapter 5 Novell Troubleshooting Tips • Is there an available NetWare user license for the PrintNet to use while it acts as a PSERVER? Every PSERVER takes up one user license since it logs in to the Novell file server. • Have you given the connection process some time after repowering the PrintNet? In larger Novell environments, the file server identification and connection process can take several minutes. NetWare 4.
6 OS/2 Configuration Overview This chapter details a complete OS/2 configuration setup including: 1. Configuring the PrintNet Interface with its TCP/IP settings 2. Configuring a new printer on an OS/2 workstation. The procedure given will be from an OS/2 Warp 4 system, but the setup is similar to OS/2 Warp 3 and v2.11. 3. OS/2 must have TCP/IP installed on it and be configured with the correct IP parameters. See OS/2 documentation/help and your network administrator.
Chapter 6 Configuring the PrintNet Interface TCP/IP Settings Mandatory Settings The PrintNet Interface must be configured with an IP address and subnet mask at a minimum. Consult you network administrator to obtain the proper values for these parameters. Optional Settings One additional setting, the gateway address, is necessary if the OS/2 workstations must communicate with the PrintNet Interface across a router. Consult your network administrator to obtain the proper value for this parameter.
Using the LPR Command 7. Press the DOWN arrow key to access the portion of the IP Address to be changed. 8. Press the LEFT or RIGHT arrow key to change access to the portion of the IP Address to be changed. 9. Press the DOWN arrow key to select the portion of the IP Address to be changed. 10. Press the LEFT or RIGHT arrow key to select the desired value. 11. Press the ENTER key to make the selection. An asterisk appears to the right of the value. 12.
Chapter 6 OS/2 Workstation Configuration NOTE: This name must be the name of an existing destination/queue on the PrintNet and it must be lowercase by default. You will most likely use d1prn. Troubleshooting Check the IP information on both the PrintNet and the OS/2 station for correctness. Make sure the PrintNet_queue is actually defined on the Ethernet Interface and that you are spelling it correctly.
Using an OS/2 LPR Print Queue d. Click on “Refresh.” Several \PIPE\LPDx port icons should appear in the “Output port” list. If none appear, type d:\MPTN\DLL in step c. and try this step again. NOTE: If no ports appear after completing step d., search your drives for the LPRPDRVR.PDR and type the path to this file, not including the file name, in step c. The final step available is to ask OS/2 support to install these ports. e. Select all the ports with the mouse pointer and click on “Install.
Chapter 6 OS/2 Workstation Configuration Starting the LPR Port Daemon The LPR Port Daemon must be started to enable TCP/IP printing. To start the LPR Port Daemon; 1. Open the TCP/IP folder, which is in the OS/2 System folder for Warp 3.0. 2. Open TCP/IP Configuration. 3. Select the “Autostart” tab on the notebook. 4. In “Services to Autostart,” select “lprportd.” 5. Select “Foreground Session” and “Minimized.” 6.
TCP/IP Access Problem 2. All entries must be deleted from the TCP list to grant all workstations/ hosts access to the above TCP services. To view the current access list: Use the printer control panel to access the configuration menu (see the User’s Manual for configuration menu information). From the DIAGNOSTICS/Printer Tests menu choose the E-net Test Page. When the page prints, look under the “TCP ACCESS TABLE” section for the TCP access list entries.
Chapter 6 OS/2 Workstation Configuration 9. At the system prompt, enter: store tcpip from default config http on reset NOTE: This will reset all TCP/IP settings to factory default and reset the PrintNet. 10. Power the printer off and then back on. 11. Set the IP address, subnet mask, and default gateway parameters to the desired values. 12. If Web browser access does not work, Telnet into the PrintNet as root.
7 AS/400 Configuration Overview There are several methods of printing with PrintNet to a print server attached printer via an AS/400; each method should be chosen on the basis of your print needs. The easiest methods for single files or print specific files which require manually entered data are LPR, and FTP. For spooled (automatic) or batch printing, a Remote Output Queue should be created. Start by considering the nature of the data you wish to print.
Chapter 7 AS/400 Configuration AS/400 Configuration The process of using Ethernet printing via the PrintNet interface on an AS/400 involves the same procedure as setting up any other print server. Procedure 1. Obtain an IP address and subnet mask to use for the PrintNet adapter. Usually the default subnet mask of 255.255.255.0 is satisfactory (for a class C network). 2. Decide on what you want the name of the print destination to be. The defaults for the PrintNet are d1prn, d2prn, d3prn, or d4prn.
Example 5. If you choose a destination name other than the default of dxprn, establish a TELNET session (or use a Web browser) and modify the PrintNet destination name. This can be done via a “green screen” TELNET session, a tn5250 session from OS/2, a TELNET session from Windows, etc. 6. The end data stream required for the PrintNet is ASCII.
Chapter 7 AS/400 Configuration 1. Use RTVWSCST command to retrieve a table as a model to modify. See the print screens below. Retrieve WSCST source (RTVWSCST) Type choices, press Enter. Device type . . . . . . . . . . . . . . . . . . . . . . > *TRANSFORM *TRANSFORM, 3101, 3151... Manufacturer type and model . . . . . . . . Source member . . . . . . . . . . . . . . . . . . Name Source file . . . . . . . . . . . . . . . . . . . . . . . QTXTSRC Name Library . . . . . . . . . . . . . . . . . . . . . . . . . .
Example 3. Pick the IBM 6404 as a starting point. Retrieve WSCST source (RTVWSCST) Type choices, press Enter. Device type . . . . . . . . . . . . . . . . . . . . . . > *TRANSFORM *TRANSFORM, 3101, 3151... Manufacturer type and model . . . . . . . . *IBM6404 Source member . . . . . . . . . . . . . . . . . . SRC6404 Name Source file . . . . . . . . . . . . . . . . . . . . . . . QTXTSRC Name Library . . . . . . . . . . . . . . . . . . . . . . . . . . *LIBL Name, *CURLIB, *LIBL Text ’description’ . . . . . . .
Chapter 7 AS/400 Configuration 5. Entering an SEU session will then give you a screen such as the following: Columns . . . : 1 71 SEU==> Edit QGPL/QTXTSRC SRC6404 FMT ** ...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 *************** Beginning of data ************************************* 0000.01 :WSCST DEVCLASS=TRANSFORM. 0000.02 0000.03 :TRNSFRMTBL. 0000.04 :PRTDTASTRM 0000.05 DATASTREAM=IBMPPDS1. 0000.06 :INITPRT 0000.
Example 6. Use the SEU editor so that the table only contains the simple commands wanted. Columns . . . : 1 71 SEU==> Edit QGPL/QTXTSRC PTXPGL FMT ** ...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 *************** Beginning of data ************************************* 0001.00 :WSCST DEVCLASS=TRANSFORM. 0002.00 0003.00 :TRNSFRMTBL. 0004.00 :RESETPRT 0005.00 DATA =’0C’X. 0006.00 :SPACE 0007.00 DATA =’20’X. 0008.00 :CARRTN 0009.00 DATA =’0D’X. 0010.00 :FORMFEED 0011.00 DATA =’0C’X.
Chapter 7 AS/400 Configuration 8. Create an Output Queue using the WSCST Object, and printer destination “d1prn”. In this example the Output Queue is named “IP_P5000”. Create Output Queue (CRTOUTQ) Type choices, press Enter. Output queue. . . . . . . . . . . . . . . . . . . . . > IP_P5000 Name Library . . . . . . . . . . . . . . . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB Maximum spooled file size: Number of pages . . . . . . . . . . . . . . . . . *NONE Number, *SAME, *NONE Starting time . . . .
Example The last part (“More”) of the screen is: Create Output Queue (CRTOUTQ) Type choices, press Enter. Queue for writer messages . . . . . . . . . . QSYSOPR Library . . . . . . . . . . . . . . . . . . . . . . . . . *LIBL Connection type . . . . . . . . . . . . . . . . . . *IP Name, *SAME Name, *LIBL, *CURLIB *SNA, *IP, *SAME Destination type . . . . . . . . . . . . . . . . . . *OTHER *SAME, *OS400, *OS400V2... Notice the entries for Connection type and Destination type (required).
Chapter 7 98 AS/400 Configuration
8 Commands Command Shell Overview The PrintNet comes with an in-depth command shell called “npsh.” It allows you to manipulate objects like destinations, I/O ports, and models and provides monitoring and troubleshooting capabilities. npsh Access Methods There are many ways this command shell can be accessed: • • • built in HTML forms a Telnet session from a TCP/IP host to the PrintNet a single remote shell command (i.e.
Chapter 8 Command Shell Overview Getting Command Help The PrintNet command shell provides several online help tools. These include: “?” Command Typing “?” when logged in to the command shell will produce a full listing of all commands available. Command Prefixes Typing in the first portion of a command will produce an error message showing the correct syntax. For example, typing in “store tcpip” will produce a list of all commands that start with this prefix.
store Commands Complete Command List This section outlines the entire PrintNet command set including the command syntax, a description, and in most cases, an example for each command listed. NOTE: If you see the word “ifnum ” in any npsh commands, you should substitute a “1” unless told otherwise. This “1” represents the one network interface (i.e. Ethernet) supported. store Commands These commands change the settings stored in flash memory and do not affect the current or working settings in memory.
Chapter 8 Complete Command List store pserver tcpsocket TCPportnumber port newTCPportnumber store pserver tcpsocket 4000 port 5000 Change a pre-defined TCPportnumber on the PrintNet to a newTCPportnumber. The default number is 9100 for prn. store pserver tcpsocket TCPportnumber dest destination store pserver tcpsocket 5000 dest d1prn Assign a pre-defined TCPportnumber to a particular destination on the PrintNet.
store Commands store pserver smb workgrp newworkgroupname store pserver smb workgrp eng Define a different Windows workgroup as defined by newworkgroupname for the PrintNet to be visible within. By default, the print server only comes up within the group called “WORKGROUP.” store pserver from default Set all general print server settings back to factory defaults. store pserver from current Store all current general print server settings to flash memory so they are retained after a power cycle.
Chapter 8 Complete Command List store tcpip ifnum frametype [[-]ethernet2] [[-]802.2snap] store tcpip 1 frametype ethernet2 802.2snap Control which frame type(s) is supported with the TCP/IP protocol. By default, both Ethernet 2 and 802.2snap are enabled but normal TCP/ IP communications rely on Ethernet 2. This setting has no affect on other supported network protocols (e.g. Novell). store tcpip route add|del host|net IPaddress ifnum store tcpip route add net 192.75.12.0 1 store tcpip route del net 192.
set Commands store tcpip tcp opts [-]keepalive [-]disbufmgmt store tcpip tcp opts keepalive -disbufmgmt Control whether the PrintNet maintains a connection with a host when data can not be accepted into its buffer. Normally the keepalive feature is enabled so when the printer can not accept data, the print job connection is maintained and continued once the situation clears. If disbufmgmt is disabled (i.e. “-”), the PrintNet will not buffer any data when there is a blocked situation with the printer.
Chapter 8 Complete Command List set dest destination name newname set dest d1prn name laser Change the current name of the destination to a new name as indicated by newname. This newname must be nine characters or less or it will be truncated. These names are case sensitive. set dest destination backchannel prn [prn] set dest d1prn backchannel prn Establish a return path for printer feedback for a given destination.
set Commands netbios Windows 95 and Windows for Workgroups printing. ftpd Printing using the File Transfer Protocol (FTP) via TCP/IP. set dest from default Set all destination settings back to factory defaults. set dest from stored Set all current destination settings to the values stored in flash memory. set logpath logpath name newname set logpath l1 name pagecount Change the current name of the logpath to a new name as indicated by newname.
Chapter 8 Complete Command List email Particular user’s email address. This address is set using the “set sysinfo email emailname@IPaddress” command. syslog A central TCP/IP host running the SYSLOG daemon. This host is set using the “set sysinfo syslog IPaddress” command. set logpath from default Set all logpath settings back to factory defaults. set logpath from stored Set all current logpath settings to the values stored in flash memory.
set Commands descramble Automatic descrambling of print jobs passing through which have been scrambled using Printronix proprietary scramble Unix utility, npscramble. xtab Tab expansion from 1 to 16 spaces. set model model trailer trailerstring set model m7 trailer $FF Set a trailer string to be sent to the printer at the end of any print jobs passing through this model. trailerstring can consist of up to nine elements. An example element is a hexadecimal code (e.g.
Chapter 8 Complete Command List set prn [-]opost set prn -opost Allow or disallow output processing on the parallel port such as carriage return insertion (i.e. onlcr). set prn [-]onlcr set prn -onlcr Enable or disable carriage return insertion on the parallel port. This may be needed for Unix text jobs coming through with solitary linefeeds. This feature is almost always set at the model level rather than the I/O port level though.
set Commands set sysinfo loginfo [-]sys | [-]tcp | [-]ipx | [-]spx set sysinfo loginfo -sys ipx Set the PrintNet debugging information type. Usually this information includes unexpected errors or exceptions from the print server divided into these groups: sys General system messages. tcp TCP stack messages. ipx IPX stack messages. spx SPX stack messages. NOTE: This is not printer or job logging information.
Chapter 8 Complete Command List set sysinfo descramblekey hexvalue set sysinfo descramblekey 1234 Set the key value used for descrambling print jobs that have passed through Printronix npscramble utility on a TCP/IP host. This key is a four-digit hexadecimal value obtained from the host software, npscramble. Within the npscramble source code, there is a variable called SR_KEY which contains the default key value. This can be changed to any four-digit value you would like.
list Commands set user from default Set all user settings back to factory defaults. set user from stored Set all current user settings to the values stored in flash memory. set var variablename variablestring set var LANDSCAPE 0x1b 0x26 0x6c 0x31 0x4f set var FINISH $FF $PCL-RST Define a new variable to be used in header, trailer, or switch strings on the PrintNet and call it variablename. variablestring can be a space-separated list of words, hexadecimal numbers (e.g.
Chapter 8 Complete Command List list pserver List the current general print server settings (e.g. print server name and Novell mode). list dest List the current destination settings (e.g. names and mapped I/O ports, models, and logpaths). list model List the current model settings (e.g. names and mapped destinations). list logpath List the current logpath settings (e.g. names and mapped destinations). list prn List the current parallel port setting (e.g. mode).
debug Commands list time List the current time on the PrintNet. list date List the current date on the PrintNet. list test List the status of output tests on the I/O ports. list key List the license details and license key number. list diff List the differences between the current settings and the stored settings in flash memory. Normally, you want these values to match so issue a “save” command followed by a “reset”.
Chapter 8 Complete Command List debug nif List network interface statistics. Miscellaneous Commands These commands do not fall under any specific section of the command shell but they are used quite frequently. save [default] Save the current settings to flash memory so they are available after power cycles. Sysinfo, destination, model, logpath, variable, user, and I/O port settings will be saved.
Miscellaneous Commands start fox|tts|loopb prn start fox prn Begin a debugging test on one of the I/O ports on the PrintNet. The tests available are: fox A continuous stream of text sent to the attached printer. This is a good test for troubleshooting hardware as long as the attached printer supports text output. tts A continuous stream of Gandalf 400C TTScompatible text sent to the attached printer. loopb Loopback test. Any input characters from the device attached to the I/O port is echoed back.
Chapter 8 Complete Command List ping [-s] hostIPaddress [datasize [packetnumber]] ping 192.75.11.30 “ping” another TCP/IP host specified by hostIPaddress on the PrintNet network. datasize is the datagram packet size which defaults to 64 bytes if no size is included in the syntax and packetnumber is the number of requests to be sent. NOTE: To use a host or IP name instead of the address, you must have set the DNS server on the PrintNet. Use the command “set sysinfo dns...” to do this.
9 Extra Features PrintNet Security There are TCP access lists available to restrict host connections with the device. Users and Passwords The PrintNet supports two user types: root Access to everything within the print server including all configurable settings. guest Ability to list settings only. Passwords can be set for each user type. However, most often you would just set a password for the root user to protect the PrintNet configuration.
Chapter 9 PrintNet Security Example: set user passwd root your_password_for_root save 2. Direct your Web browser to URL “http://PrintNetIPaddress/adminConf.html” (e.g. “http://192.75.11.9/adminConf.html”). NOTE: If prompted for a “User ID” and password first, type in “root” for the user ID and press ENTER at the password prompt since there is no password by default. 3. At the “Administration Configuration” HTML form that displays, scroll down to the “Passwords” section. 4.
TCP Access Lists TCP Access Lists Within TCP/IP environments, the PrintNet can restrict host access to destinations/queues and remote command (i.e. rsh, rcmd, remsh and telnet) execution services. This is done using an access list similar in function to the Unix .rhosts file. To view the current access list on the print server: NOTE: Access list settings are not configurable through the HTML forms provided with the PrintNet. 1. Start a Telnet session with the PrintNet. Syntax: telnet PrintNetIPaddress 2.
Chapter 9 Printer Monitoring and Logging Example: store tcpip tcp access add 192.75.11.25 store tcpip tcp access add 192.75.12.0 store tcpip tcp access del 192.75.11.25 reset NOTE: Although the maximum number of entries in the access list is 10, each entry can refer to a network rather than a specific host. This allows all hosts on that specified network to have access plus any individual hosts specified in the list.
Printer Logging Through Logpaths Table 4. Key Printer Logging Terms Term Description “idle” There is no job queued for the PrintNet I/O port. “blocked” The printer is not allowing the PrintNet to send data to it. Check that there is not a printer error and it is online and ready to go. “waiting” The PrintNet knows about a print job but is waiting for the host to send more data or to send an expected packet.
Chapter 9 Printer Monitoring and Logging To view the current logpath settings on the print server: 1. Load a Web browser on a network station that can communicate with the print server over TCP/IP or using Telnet (e.g. Telnet “ipaddress”). The command to view the logpath settings is: NOTE: If prompted for a “User ID” and password first, type in “root” for the ID and press ENTER at the password prompt since there is no password by default. Syntax: list logpath 2.
Procedure Downloading Software Emulation and operating system software must be loaded into flash memory on the controller board. This software is stored as a compressed file on a 3.5 inch, double-density floppy diskette. The software can be downloaded from the host computer to the printer’s flash memory using PrintNet. Procedure 1. Make a printout of all saved configurations. (Refer to the User’s Manual.) (Installing new software erases all saved configurations.
Chapter 9 Downloading Software 8. Get the name of the compressed file on the diskette by listing the contents of the diskette; at the DOS prompt type: DIR The compressed file on the diskette takes the form FILENAME.EXE 9. Copy the compressed file to the “download” directory you created in step 5; at the DOS prompt type: copy FILENAME.EXE c:\download where FILENAME.EXE is the name of the file contained on the diskette. 10.
Procedure 14. Once logged in, type the following sequence at the DOS prompt to download the FILENAME.PRG file to the printer: cd dest cd d1prn bin put FILENAME.PRG (where FILENAME.PRG is the name of the file decompressed in step 11.) 15. As the file downloads, the FTP program shows the progress as a percentage. Once the download is complete, exit out of the FTP program by typing: quit 16.
Chapter 9 PrintNet Naming Schemes PrintNet Naming Schemes I/O PORT DESTINATION MODEL LOGPATH d1prn m1 l1 d2prn m2 l2 d3prn m3 l3 d4prn m4 l4 PRN Figure 14.
10 Glossary ARP Address Resolution Protocol. Associates a selected IP address with a network device Ethernet address. bps Bits per second. Centronics Parallel port interface standard found on most printers. daemon A continuously running process that handles system-wide functions like print spooling. default router Local device that forwards any IP packets destined for another subnet. destination Logical print queue on the PrintNet which hosts send their print jobs to.
Chapter 10 130 Factory Settings S2 jumper position stating all factory default settings are to be used while the PrintNet is up and running. Firmware Panic Unrecoverable errors detected by the PrintNet firmware force the Print Server into Firmware Panic mode. Manually reset the PrintNet to resume operation. Flash Stores firmware code and configurable settings. Allows for upgrades without replacing hardware inside the PrintNet. FTP File Transfer Protocol.
logpath Determines type of print job and printer logging needed per job. One logpath is associated with every destination. LPD/LPR Line Printer Daemon. The most common TCP/IP remote printing protocol that crosses all hardware utilizing IP. MIB Management Information Base. A set of variables (database) managed by an SNMP manager application. model Defines how a print job should be processed (e.g. banner pages added, ASCII to PostScript conversion) as it passes through the PrintNet.
Chapter 10 132 protocol A set of rules or conventions governing the exchange of information between computer systems, or between a printer and a host computer. For computer printers, a protocol is the coding convention used to convey and print data. A printer protocol includes codes for printing text and graphics, as well as codes instructing the printer to perform special operations, and machine-to-machine communication codes. PSERVER Print Server.
subnet mask A binary value used to divide IP networks into smaller sub-networks or subnets. This mask is used to help determine whether IP packets need to be forwarded on to other subnets. TCP/IP Transmission Control Protocol/Internet Protocol. Suite of protocols that act as the base protocol for the Internet. TCP port A logical connection point in the software of a TCP host or device.
Chapter 10 134
Index Symbols npsh, 99 set, 105 ? Command, 100 store, 101 A Communicating Unix, 57 Access Lists Windows, 30 TCP, 121 Configuration Access Methods available tools, 17 npsh, 99 control panel, 23, 51 AIX Printing, 60 description, 17 architecture, 11 Configuring the TCP/IP AS/400 Configuration, 89 example, 91 OS/2, 81 Connection to network, 15 print server, 90 C Changing PrintNet name, 69 Control Panel Configuration, 23, 51 gateway address, 23, 51, 82 IP Address, 23, 51, 82 subnet mask, 23
Index F overview, 17 troubleshooting, 42 Features L list of, 11 LED formfeeds, 64 status, 43 FTP Printing, 60 G List Commands, 113 Logging, 122 Gateway Address through logpaths, 123 control panel configuration, 23, 51, 82 M Getting Help Command, 100 Manual vs Host, 58 Guest, 119 H Miscellaneous Commands, 116 Mode Home Page auto reset, 14 PrintNet, 18 run, 14 Host Configuration models Novell, 70 setting a formfeed, 64 Unix, 58 setting onlcr, 64 Host Setup Monitoring, 122 Window
Index NetWare 3.x configuration, 70 NetWare Version 3.x, 72 NetWare Version 4.x, 74, 77 PrintNet configuration, 68 PrintNet Configuration Windows, 22 PrintNet Name changing, 69 PrintNet Naming Scheme, 128 Novell 4.x troubleshooting, 80 PrintNet Security, 119 Printronix Printing System NPRINTER PPS, 40 overview, 70 PSERVER npsh main commands, 99 overview, 70 R npsh Access Methods, 99 npsh.
Index Store Commands, 101 Unix, 55 Using BOOTP Subnet Mask control panel configuration, 23, 51, 82 Unix, 56 T TCP Access Lists, 121 TCP/IP Access Problem W Windows communicating, 30 OS/2, 86 environment description, 21 Unix, 65 mandatory configuration, 22 Windows, 45 NT 3.51configuration, 33, 34 Troubleshooting optional configuration, 23 Novell 4.
5525B/31/32 Line Matrix Printer Compaq Computer Corporation P/N 422720-001 170118-001A
