Printers Zeilen Matrix Drucker 9045 Line Matrix Printer 9045 4pedloc April 4, 2000 Installieren, in Betrieb nehmen und Warten Installation, Startup and Maintenance 55flcab May 5, 2000 PrintNet® User’s Manual
READ THIS SOFTWARE LICENSE AGREEMENT BEFORE USING THIS PRINTER Software License Agreement 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. Definitions.
PrintNet® User’s Manual Edition July 2000
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 Fujitsu Siemens Computers.
Trademark Acknowledgements Portions of this manual used by permission of Wyndham Technologies, Inc. Copyright © 1991-1999 Wyndham Technologies Inc. IGP, LinePrinter Plus, PGL, PrintNet and Printronix are registered trademarks of Printronix, Inc. AIX, AS/400, NetView and OS/2 are registered trademarks, and AFP, Intelligent Printer Data Stream, IPDS, Print Services Facility, and PSF are trademarks of International Business Machines Corporation.
Table of Contents 1 Introduction ............................................... 13 Overview.................................................................................13 What is the PrintNet? .......................................................13 What Special Features are Available? .............................13 Interfaces................................................................................14 10Base2 and 10Base-T ...................................................15 10/100Base-T.......
Table of Contents Windows Host Configuration ..................................................40 Windows NT 3.51 Host Setup ..........................................40 Windows NT 4.0 Host Setup ............................................41 Windows 95 Host Setup...................................................46 Printronix Printing System (PPS) Host Setup ..................47 Windows 3.1 Host Setup..................................................48 Windows Troubleshooting Tips .........................
Table of Contents Unix Troubleshooting Tips ......................................................69 PrintNet Cannot be Found on the Network ......................69 Nothing Prints...................................................................70 Stair-Stepped Output .......................................................71 No Form Feed or Extra Page Comes Out........................71 TCP/IP Access Problem...................................................72 5 Novell Configuration .....................
Table of Contents Changing the PrintNet Mode (NDS and Bindery setups) .............................................101 Setting the PrintNet NDS Context (NDS setups) ...........102 Setting the PrintNet Preferred NDS Tree (NDS setups) .................................................................103 Novell Host Configuration (10/100Base-T)...........................104 NDS PSERVER Setup (Netware 4.x) ............................104 Bindery PSERVER Setup (Netware 3.x and Netware 4.x) .......................
Table of Contents Complete Command List ......................................................127 Store Commands ...........................................................127 Set Commands ..............................................................131 List Commands ..............................................................140 Debug Commands .........................................................142 Miscellaneous Commands .............................................144 9 Extra Features ...........
Table of Contents 12
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 Interfaces • 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.
10Base2 and 10Base-T 10Base2 and 10Base-T The PrintNet interface card at the rear of the printer for the 10Base2 and 10Base-T interfaces has three indicator lights, shown in Figure 1. Status Indicators STAT ERR NET Grn Red Grn OFF (Default is all switches OFF, as shown.) DIP Switches 1 2 3 Figure 1. Status Indicator Lights (10Base2 and 10Base-T) The LED patterns and the respective indications are given in Table 1. Table 1.
Chapter 1 Interfaces Operating Modes The PrintNet has a self test and internally controlled modes. These are: Power-on Self Test The power-on self test performs diagnostic tests on the PrintNet processor, RAM, ROM, EEPROM, parallel ports, and network interface. The STAT, ERR, and NET LEDs indicate which test is currently in progress. Run and Auto Reset Modes Run Mode is the normal operating state of the PrintNet.
10Base2 and 10Base-T Dipswitches On the back of the 10Base2 and 10Base-T interfaces, you will find a small window where you can access three dipswitches labeled 1, 2, and 3 (see Figure 1). The functions of the dipswitches are explained in Table 3. Table 3. 10Base2 and 10Base-T Dipswitch Settings Dipswitch Comments 1 Reserved. This dipswitch is not for customer use and should be left in the “off” position. 2 Factory Defaults.
Chapter 1 Interfaces 10/100Base-T The PrintNet interface card at the rear of the printer for the 10/100Base-T interface has two indicator lights, shown in Figure 2. DIP Switches 1 2 STAT (System Status) NET (Data to Network) Figure 2. Status Indicator Lights and Dipswitches (10/100Base-T) 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.
10/100Base-T Network Indicator The NET LED displays the status of the network link. When the NET LED is on, this confirms link integrity. The NET LED flashes off for 1/3 second when a data packet is being transferred. When the NET LED is off, the network connection has been severed. Dipswitches On the back of the 10/100Base-T interface, you will find a small window where you can access two dipswitches labeled 1 and 2 (see Figure 2). The functions of the dipswitches are explained in Table 5. Table 5.
Chapter 1 Conventions Used In This Manual Conventions Used In This Manual Command syntax and examples are formatted as follows: • The Courier font in boldface indicates commands that you type: $ ping ftp.CompanyWebsite.com • Regular Courier font indicates displayed results: ftp.CompanyWebsite.com is alive • Variable values are shown in italics in command syntax, output, and in text.
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 or 10/100Base-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 3, plug the network cable into the PrintNet connector.
Chapter 2 Installation $ $ Network Connector Figure 3.
Configuration Using the Printer Control Panel 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.
Chapter 2 Configuration Tools 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: 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 Operating Manual for instructions. 4.
IPAssign IPAssign IPAssign is a Windows utility which helps identify the PrintNet on the network. IPAssign relies on the TCP/IP protocol to locate PrintNet print servers so they can be assigned. Relying on TCP/IP as the underlying protocol, the print server can be assigned an IP address and subnet mask once it is detected on the network. Once IP address, subnet and gateway values are assigned, other tools like the HTML configuration forms can be used to do additional configuration. Figure 4.
Chapter 2 Configuration Tools 3. Direct your Web browser to the Uniform Resource Locator (URL) “http://IPaddress ” (e.g. “http://192.75.11.9”). The PrintNet HTML structure is divided into several menus as shown in Figure 5. Index/Home Configuration Status Help About I/O Port HTTP I/O Port Network Network TCP/IP Windows Novell Print Path Administration d1prn d2prn d3prn d4prn Figure 5. PrintNet HTML Structure NOTE: Online help is available for all HTML pages.
HTML Forms Printer Status Screen Using the printer IPAddress and any standard web browser, you can check the status of the printer. Figure 6 shows the exact state of the printer by showing the printer LCD message. Figure 6.
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 Printer Win 95 Figure 7. 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.
Optional Optional Additional settings, like routing entries, can be configured. This allows communication across subnets when no other router exists. Configuration of the PrintNet can be done from the printer control panel, IPAssign, Web browser, or host commands. To configure these options, see “Configuration Tools” on page 23. Configuration Using IPAssign NOTE: You must have the TCP/IP protocol and services enabled on this windows station first.
Chapter 3 Windows PrintNet Configuration 8. At the “IPAssign” main dialogue box that appears, you should see an entry for your PrintNet appear in the list box. Figure 8 shows an example screen. Figure 8. 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.
Configuration Using IPAssign 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.
Chapter 3 Windows PrintNet Configuration Figure 9.
Configuration Using ARP 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 cannot print to it yet since you have not identified the network printer to your Windows station. Refer to “Windows Host Configuration” on page 40 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.
Chapter 3 Windows PrintNet Configuration 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.
Communicating Across Routers 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.
Chapter 3 Windows PrintNet Configuration 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”).
Changing Destination Names The first field requires the IP address for the PrintNet and the second field must be filled in with a valid destination from the print server (e.g., d1prn). Otherwise, LPR will not be able to access the printer. Table 6 outlines the default destinations to choose from. Table 6. PrintNet Default Destinations Destination Mapped I/O Port d1prn PRN d2prn PRN d3prn PRN d4prn PRN This name can be changed to something more meaningful using the builtin HTML forms.
Chapter 3 Windows Host Configuration 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 11. Figure 11. Create a Printer Dialogue Box 4.
Windows NT 4.0 Host Setup 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 12. Figure 12. 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.
Chapter 3 Windows Host Configuration 3. Select “My Computer.” 4. At the next window, click on “Add Port ...
Windows NT 4.0 Host Setup 5. Double click on “LPR Port”. If LPR Port is not listed it means that the 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.
Chapter 3 Windows Host Configuration 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.
Windows NT 4.0 Host Setup 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 54.
Chapter 3 Windows Host Configuration 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.
Printronix Printing System (PPS) Host Setup Printronix Printing System (PPS) Host Setup To configure a PPS LPR port for a 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.
Chapter 3 Windows Host Configuration 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.
IPAssign Cannot Find the PrintNet 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.
Chapter 3 Windows Troubleshooting Tips PrintNet Cannot Be Found 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.
Cannot Browse the PrintNet on the Network Cannot Browse the PrintNet on the Network • Have you looked under the right Windows workgroup? By default, the PrintNet will be found under “WORKGROUP.
Chapter 3 Windows Troubleshooting Tips 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.
TCP/IP Access Problem 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.
Chapter 3 Windows Troubleshooting Tips 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 cannot “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 Operating Manual for configuration menu information.
Windows NT 4.0 Host Setup Problems • 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.
Chapter 3 56 Windows Troubleshooting Tips
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 13 illustrates this.
Chapter 4 Unix Environment Description Linux XTerm PC PC Solaris PC Ultrix OSF/1 XTerm IRIX SparcStation SunOS 4.1.1 IP Router SCO HP-UX Printer Figure 13.
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 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.
Using ARP 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.9/networkConf.html”).
Chapter 4 Unix PrintNet Configuration 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.
Using BOOTP 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.
Chapter 4 Unix PrintNet Configuration 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.
Manual System V Host Setup 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.).
Chapter 4 Unix Host Configuration 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.
Printing from AIX 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.
Chapter 4 Unix Host Configuration 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.
PrintNet Cannot be Found on the Network 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.
Chapter 4 Unix Troubleshooting Tips 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.
Stair-Stepped Output 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.
Chapter 4 Unix Troubleshooting Tips 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 156. 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.
TCP/IP Access Problem 3. On the PrintNet, place SWITCH 2 in the down position. 4. Power on the printer and wait for the ONLINE state. 5. On the PrintNet, place SWITCH 2 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. Try to “ping” this IP address to see if the PrintNet can be seen on your network.
Chapter 4 74 Unix Troubleshooting Tips
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. For additional information about further options available with the 10/100 Base-T interface, see Chapter 6, “Novell Configuration for 10/100Base-T Interfaces”.
Chapter 5 Novell Environment Description Novell Environment Description The PrintNet supports network printing under Novell environments by using IPX. It supports all 3.1X versions of NetWare. Figure 14 provides a Novell setup overview. Version 4.1X is supported under bindery emulation only. NetWare Workstation NetWare 4.1 File Server NetWare Workstation NetWare 4.1 File Server NetWare Workstation Bridge/Router NetWare Workstation Printer Figure 14.
Novell PrintNet Configuration Mandatory 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. However, with a new print queue setup on a Novell file server, there can be some mandatory settings needed on the PrintNet. Optional Additional settings are available to fine-tune the PrintNet’s Novell functionality. These options include: • NDS Context.
Chapter 5 Novell PrintNet Configuration 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).
NetWare Version 3.x PSERVER Setup 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 cannot service multiple file servers at one time. NetWare Version 3.
Chapter 5 Novell Host Configuration 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.
NetWare Version 3.x RPRINTER Setup 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 23 for further details.
Chapter 5 Novell Host Configuration 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.
NetWare Version 4.x PSERVER Setup 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.
Chapter 5 Novell Host Configuration 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.
NetWare Version 4.x PSERVER Setup 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.
Chapter 5 Novell Host Configuration 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.
NetWare Version 4.x RPRINTER Setup 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.
Chapter 5 Novell Troubleshooting Tips 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.
NetWare 4.x - No PSERVER Connection • 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.
Chapter 5 90 Novell Troubleshooting Tips
6 Novell Configuration for 10/100Base-T Interfaces Overview This chapter provides additional information for Novell environments using the 10/100Base-T interface, including: 1. PrintNet Configuration. This section includes: setting the preferred file server, setting password security, adjusting polling time, changing the PrintNet name, changing the PrintNet frame type, changing the PrintNet mode, setting the PrintNet NDS context, and setting the PrintNet preferred NDS tree. 2. Host Configuration.
Chapter 6 Novell PrintNet Configuration (10/100Base-T) Novell PrintNet Configuration (10/100Base-T) There are no mandatory Novell settings needed before the print server can be detected on the network. However, there can be some mandatory settings needed before a Novell print queue can be serviced by the PrintNet. These mandatory settings are covered separately for Netware 3.x and 4.x under the Host Configuration heading.
Preferred File Server (NDS and Bindery setups) Preferred File Server (NDS and Bindery setups) In a bindery setup, the preferred file server specifies the file server that the print server object was created on. In an NDS setup, it specifies a file server that the print server object resides on. Since NDS is distributed, most administrators will not know which file server(s) the print server object is actually stored on, so in most NDS environments this option is not used.
Chapter 6 Novell PrintNet Configuration (10/100Base-T) Manual (Telnet) Method 1. Telnet to the print server. This will bring up a login screen: telnet ipaddress 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’s no password by default. 2. You should now see a prompt displayed that has the PrintNet’s IP address followed by a colon then root. ipaddress:root> 3.
Setting Password Security (NDS and Bindery setups) Manual (Telnet) Method 1. Telnet to the print server. This will bring up a login screen: telnet ipaddress 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’s no password by default. 2. You should now see a prompt displayed that has the PrintNet’s IP address followed by a colon then root. ipaddress:root> 3.
Chapter 6 Novell PrintNet Configuration (10/100Base-T) 5. Proceed to the next section to store the password on the PrintNet. Netware 3.x 1. Enter PCONSOLE as supervisor on your Novell host. 2. Select “Print Server Information” from the main menu. 3. Select the appropriate printer and press ENTER. 4. Select “Change Password.” 5. At the prompts, type and re-type the new password. Press ENTER when you are finished. 6. Proceed to the next section to store the password on the PrintNet.
Adjusting Polling Time (NDS and Bindery setups) 2. You should now see a prompt displayed that has the PrintNet’s IP address followed by a colon then root. ipaddress:root> 3. At the prompt, enter: store pserver novell passwd password NOTE: The passwords entered in Netware Administrator or PCONSOLE must match the password set on the unit. 4. Reset the unit to ensure the changes take effect.
Chapter 6 Novell PrintNet Configuration (10/100Base-T) 3. Select the print server you have been using for your PSERVER setup and press ENTER. By default this will be “M_xxxxxx” where “xxxxxx” equals the last six digits of the print server’s Ethernet address found on the bottom of the device (e.g. “M_091C1A”). 4. Select “Print Server Configuration” from the menu that displays. 5. Select “Printer Configuration” from the next menu to display a list of configured printers. 6.
Changing the PrintNet Name (NDS and Bindery setups) HTML Method 1. Load a Web browser on a network station that can communicate with the print server over TCP/IP. 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 ID and press ENTER at the password prompt since there’s no password by default. 3.
Chapter 6 Novell PrintNet Configuration (10/100Base-T) Changing the PrintNet Frame Type (NDS and Bindery setups) The PrintNet allows the user to store a particular frame type for the unit to adhere to in a Novell environment. HTML Method 1. Load a Web browser on a network station that can communicate with the print server over TCP/IP. 2. Direct your Web browser to URL: “http://PrintNetIPaddress/networkConf.html” (e.g. “http://192.75.11.9/networkConf.html”).
Changing the PrintNet Mode (NDS and Bindery setups) Changing the PrintNet Mode (NDS and Bindery setups) The PrintNet allows the user to store a particular mode for the unit to operate in. This will be either NDS, Bindery, or autosense. If autosense is used, the PrintNet will first attempt to login to an NDS file server and if it fails it will try to login to a Bindery file server. NOTE: If you are using both NDS and Bindery file servers in your setup, make sure the mode is set to auto. HTML Method 1.
Chapter 6 Novell PrintNet Configuration (10/100Base-T) 3. At the prompt, enter: store pserver novell mode [nds | bindery | auto] 4. Reset the unit to make the changes take effect. reset Setting the PrintNet NDS Context (NDS setups) The PrintNet allows you to store the print server object in any context within the NDS tree you choose. By default the PrintNet will look for the print server object in the same context as the file server object it connects to is stored in. HTML Method 1.
Setting the PrintNet Preferred NDS Tree (NDS setups) 3. At the prompt, enter: store pserver novell context context 4. Reset the unit to make the changes take effect. reset Setting the PrintNet Preferred NDS Tree (NDS setups) The PrintNet supports Novell environments that have multiple trees. If your environment has more than one tree you may want to set a preferred tree. By default, the PrintNet will try to login to each tree it finds in turn until it is successful. HTML Method 1.
Chapter 6 Novell Host Configuration (10/100Base-T) 2. You should now see a prompt displayed that has the PrintNet’s IP address followed by a colon then root. ipaddress:root> 3. At the prompt, enter: store pserver novell tree tree 4. Reset the unit to make the changes take effect. reset Novell Host Configuration (10/100Base-T) This section covers PSERVER and RPRINTER/NPRINTER setups on the PrintNet. The PrintNet can handle up to eight RPRINTER/NPPRINTER setups.
NDS PSERVER Setup (Netware 4.x) To create a printer/print queue in an NDS environment using Netware Administrator print server objects, you will need to: 1. Login to NetWare Administrator as a user with security equal to “Admin” on your Novell host. 2. Click with the right mouse button on a branch in the tree that you would like to create a print queue object in. 3. Select “Create...” from the menu that pops up to bring up the “New Object” dialogue. 4.
Chapter 6 Novell Host Configuration (10/100Base-T) This destination allows for further processing of the print job before sending it to the printer. If you are using multiple print servers, you will have to either rename all your destinations to ensure that no printer object names conflict or keep all the printer objects for one print server in a different context than those for the other print server. 11. Select “Define additional properties” and click on “Create.” 12.
Bindery PSERVER Setup (Netware 3.x and Netware 4.x) 21. Click on “Assignments” in the dialogue that pops up, and then on the “Add...” button. 22. Select the printer you created earlier. 23. Click on “OK” to assign this printer to this print server. 24. Click on “OK” to close the printer servers details dialogue and make the changes permanent. 25. Physically re-power the printer to make the new settings take effect. Bindery PSERVER Setup (Netware 3.x and Netware 4.
Chapter 6 Novell Host Configuration (10/100Base-T) “auto” so that both NDS and Bindery logins are possible. See “Setting the PrintNet NDS Context (NDS setups)” on page 102. RPRINTER/NPRINTER Setup (Netware 3.x and Netware 4.x) This procedure associates an existing PSERVER with a remote PrintNet acting as a RPRINTER/NPRINTER in a NetWare 3.x or Netware 4.x environment. It is the PSERVER’s responsibility to get jobs from the queue and to pass them off to the PrintNet acting as the remote printer.
RPRINTER/NPRINTER Setup (Netware 3.x and Netware 4.x) 2. Load a Web browser on a network station that can communicate with the print server over TCP/IP. 3. Direct your Web browser to URL: “http://PrintNetIPaddress/networkConf.html” (e.g., “http://192.75.11.9/networkConf.html”). 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’s no password by default. 4. Look under the “Novell” section and find a row in the RPRINTER category.
Chapter 6 Troubleshooting (10/100Base-T) 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’s no password by default. 3. You should now see a prompt displayed that has the PrintNet’s IP address followed by a colon then root. ipaddress:root> 4. At the prompt, store the RPRINTER settings on the PrintNet. The pservername refers to the existing PSERVER.NLM on the file server created in step 1.
PSERVER Setup • Have you tried repowering the PrintNet? Wait about a minute before checking to see if it has logged in and attached to a queue. • • Is the network connector fastened tightly to the unit? • Is there an available NetWare user license for the PrintNet to utilize while it acts as a PSERVER? Every PSERVER takes up one user license since it logs in to the Novell file server.
Chapter 6 112 Troubleshooting (10/100Base-T) • Try doing a debug nest ipx telnet command on the PrintNet (or find the “IPX Layer” section on the Novell HTML status page). Check that a board has been bound to the PrintNet, and that the network number is correct for your network. If not, you may want to set a specific frame type for the PrintNet to use.
RPRINTER/NPRINTER Setup NOTE: Debug messages for the PSERVER setup are in the RPRINTER section here because the PSERVER setup on the PrintNet shares some code with the RPRINTER setup. • Try a debug nest logs telnet command (or find the “General Messages” section on the Novell HTML status page). Look for a valid entry for the printer. It will look something like this: “(0:InitSinglePrinter): printer= name=”.
Chapter 6 114 Troubleshooting (10/100Base-T) • Have you tried repowering the printer? Wait about a minute before checking to see if it has logged in and attached to a queue. • • Is the network connector fastened tightly to the unit? • Is there an entry when a list rprinter telnet command is done on the PrintNet (not found on the Novell HTML status page)? When the PrintNet is configured as an RPRINTER, this command should produce the appropriate entry.
Printing Related Only one RPRINTER connection is allowed to service a PSERVER.NLM printer. • If the PrintNet has logged in to the file server but has not attached to the queue, there may be a permission problem. Make sure the appropriate users have rights to this queue (they should be in the group “everyone.”) Also, you may have to assign the queue to “root” so that is available to everyone. If none of these help your situation, you may want to try the whole setup again.
Chapter 6 Troubleshooting (10/100Base-T) • Is the PrintNet configured as the queue’s “Currently Attached Server”? If not, make sure you have associated the queue and the printer. See “Novell Host Configuration” on page 79. • Is there a hold on the print job? If you select the job from PCONSOLE’s CURRENT PRINT JOB ENTRIES, change the User Hold or Operator Hold to “no.
Printing Related Some other things to consider when garbled data persists are: • • tab expansion (xtab) set on (in a model) with graphic jobs the correct driver for the printer if printing from within Windows For additional information on these suggestions or on various Novell printing mechanisms, please refer to your NetWare user manuals.
Chapter 6 118 Troubleshooting (10/100Base-T)
7 Monitoring Printers Implementing Printer Management Printer management includes the following tasks: • • • Monitoring the status of network printers Responding to alarms Gathering statistics on printer operations The three elements of network printer monitoring and management are: • • • Agent/manager model MIB, the management information database SNMP, the protocol used to get management information Agent/Manager Model The elements of a monitoring system, MIB and SNMP, are implemented in an agent/
Chapter 7 Implementing Printer Management MIB A MIB is a management information base that contains information a device makes available to SNMP. The MIB describes information about actual objects to be managed and controlled. There are many different MIBs defined.
MIB Information Provided by the MIB The Printer MIB contains the following types of information about network printers: Descriptions. Printer configuration, location, and contact. Status. Current operating status of printers. Alerts. Reportable events from printers.
Chapter 7 Monitoring Tools SNMP SNMP is the protocol used to communicate between manager and agent. Managers request information, usually through automated polling at specified intervals, and agents respond. Though used primarily on TCP/ IP networks, SNMP can be implemented on other protocols, for example, IPX. SNMP is a standard by which a network manager can get statistics and configuration information from the NICs and other devices on the network.
Setting the SNMP Community Name Setting the SNMP Community Name The default SNMP read-only community name is “public,” and cannot be changed. Change the SNMP R/W community name with the command: set user passwd snmp com_name save where com_name is the new SNMP R/W community name. The default is no R/W community name. NOTE: Changing SNMP community names or access rights may hinder or disable applications that are monitoring your printers.
Chapter 7 124 Monitoring Tools
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 (e.g.
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.
Set Commands store tcpip tcp opts [-]keepalive [-]disbufmgmt store tcpip tcp opts keepalive -disbufmgmt Controls whether the PrintNet maintains a connection with a host when data cannot be accepted into its buffer. Normally the keepalive feature is enabled so when the printer cannot 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 snmp manager index ipaddress trap-community The PrintNet continuously generates traps but unless the trap table is filled in, no SNMP manager will receive this information. To set the PrintNet to send traps to a particular SNMP manager, use this command to add a SNMP manager to the trap table. index is the idex number of the trap table. ipaddress is the IP address of the SNMP manager receiving traps. trap-community is the community string sent along with the trap information.
Chapter 8 Complete Command List set sysinfo logport null|syslog set sysinfo logport null Define where the debugging information should be sent to. This can be sent to an output device off of the PrintNet I/O port or to a central TCP/IP host running a SYSLOG daemon. To set this host, use the command “set sysinfo syslog hostIPaddress.” set sysinfo email emailname@IPaddress set sysinfo email joe@192.75.11.
Set Commands set time hours [minutes [seconds ]] set time 10 30 Set the current time noting the hours based on the 24-hour system and the minutes and seconds ranging from 0 through 59. If the PrintNet is reset, this value will be lost so you will need to set the time again. set user add|del username set user add eng Add or remove a user on the PrintNet defined by username. IMPORTANT Be careful not to delete the root user, or you will be unable to configure any further settings on the print server.
Chapter 8 Complete Command List 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., 0x04), or references to other pre-defined variables. It is easiest to make up the variablestring with hexadecimal values as shown in the example.
List Commands 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.” list ifc List the current UTP interface settings (e.g., link integrity). list key List the license details and license key number. list logins List any active user logins on the PrintNet. list logpath List the current logpath settings (e.g., names and mapped destinations).
Chapter 8 Complete Command List list time List the current time on the PrintNet. list user List the current user definitions (e.g., user names and types). list var List all pre-defined variables including any newly created ones. Any of these defined variables can be referenced in a string by placing a “ $” before the variable name (e.g., “set model m1 trailer $FF”). Debug Commands The “debug” set of commands help troubleshoot problems that may occur on the PrintNet.
Debug Commands debug nest logs View miscellaneous Novell log messages. debug nest odi Determine what frame type is bonded to which board number under Novell. debug nest pserver View the Novell PSERVER log messages including queues attached to. debug nest rprinter View the Novell PSERVER and RPRINTER log messages and destinations used on the PrintNet. debug nest sap Determine whether the PrintNet is seeing any Novell network activity. debug netbios List NetBIOS (i.e., Windows 95 and WfW) statistics.
Chapter 8 Complete Command List 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. If default is specified as well, factory settings will be saved, overwriting any new settings you have configured.
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 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. telnet hostIPaddress [escapecharacter] telnet 192.75.11.35 Start a Telnet session with another TCP/IP host specified by hostIPaddress on the PrintNet network. If escapecharacter is used, it resets the key sequence used to exit the Telnet session. It will return you to the telnet> prompt where you can execute “quit.
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 7. 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 Operator’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 16.
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 158 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 160 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 162
Index Symbols Communicating Unix, 64 ? Command, 126 Windows, 37 A Configuration available tools, 25 Access Lists description, 23 TCP, 149 Connection Access Methods to network, 21 npsh, 125 Control Panel Configuration AIX Printing, 67 gateway address, 23 architecture, 13 C IP Address, 23 subnet mask, 23 D Changing PrintNet name, 78 Command ?, 126 complete list, 127 getting help, 126 Command Prefixes, 126 Command Shell, 125 ways to access, 25 Commands debug, 142 list, 140 Debug Commands,
Index F IPAssign how to use, 31 Features overview, 25 list of, 13 troubleshooting, 49 formfeeds, 71 L FTP Printing, 67 G LED status, 50 Gateway Address List Commands, 140 control panel configuration, 23 Getting Help Command, 126 Logging, 150 through logpaths, 151 Guest, 147 M H Manual vs Host, 65 Home Page MIB, 120 PrintNet, 26 Miscellaneous Commands, 144 Host Configuration Mode Novell, 79 auto reset, 16, 18 Unix, 65 run, 16, 18 Host Setup models Windows 3.
Index printer monitoring Network connectors, 21 MIB, 120 HTML form, 33 SNMP, 122 tools, 122 Novell environments, 76 Printing Host Configuration, 79 AIx, 67 NetWare 3.x configuration, 79 direct socket, 68 NetWare Version 3.x, 81 NetWare Version 4.x, 83, 86 PrintNet configuration, 77 FTP, 67 PrintNet Configuration Windows, 30 PrintNet Name Novell 4.
Index S TCP/IP access problem, 72 using APR, 60 Security using ARPR, 62 PrintNet, 147 using BOOTP, 63 Self Test URL 10/100Base-T, 18 10Base2 and 10Base-T, 15 home page, 26 network configuration form, 33 Set Commands, 131 Users, 147 Setting a Password, 147 Using APR Shell Unix, 60 command, 125 Using ARP SNMP, 122 Windows, 35 Software Using ARPR downloading, 153 Store Commands, 127 Subnet Mask Unix, 62 Using BOOTP Unix, 63 control panel configuration, 23 W T Windows TCP Access Lists
Herausgegeben von / Published by Fujitsu Siemens Computers D-81730 München D-33094 Paderborn Bestell-Nr. / Order No.
