Fujitsu 9045 User Manual

Download

Printers

Zeilen Matrix Drucker 9045

4pedloc April 4, 2000

Line Matrix Printer 9045

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.

“Software” shall mean the digitally encoded, machine-readable data and program. The term “Software Product” includes the Software resident in the printer and its documentation. The Software Product is licensed (not sold) to you, and Fujitsu Siemens Computers either owns or licenses from other vendors who own, all copyright, trade secret, patent and other proprietary rights in the Software Product.

License.

1. Authorized Use. You agree to accept a non-exclusive license to use the Software resident in the printer solely for your own customary business or personal purposes.

2. Restrictions. a. To protect the proprietary rights of Fujitsu Siemens

Computers, you agree to maintain the Software Product and other proprietary information concerning the

typefaces in strict confidence. b. You agree not to duplicate or c opy the So ftware Pro duc t. c. You shall not sublicense, sell, lease, or otherwise

transfer all or any portion of the Software Product

separate from the printer, without the prior written

consent of Fujitsu Siemens Computers. d. You may not modify or prepare derivative works of the

Software Product. e. You may not transmit the Software Product over a

network, by telephone, or electronically using any

means; or reverse engineer, decompile or disassemble

the Software. f. You agree to keep confidential and use your best efforts

to prevent and protect the contents of the Software

3. Transfer. You may transfer the Software Product with the

Limited Software Product Warranty

Fujitsu Siemens Computers warrants that for ninety (90) days after delivery, the Software will perform in accordance with specifications published by Fujitsu Siemens Computers. Fujitsu Siemens Computers does not warrant that the Software is free from all bugs, errors and omissions.

Remedy

Your exclusive remedy and the sole liability of Fujitsu Siemens Computers in connection with the Software is replacement of defective software with a copy of the same version and revision level.

Disclaimer of Warranties and Limitation of Remedies

1. THE PARTIES AGREE THAT ALL OTHER WARRANTIES,

Product from unauthorized disclosure or use. printer, but only if the recipient agrees to accept the terms and

conditions of this Agreement. Your license is automatically terminated if you transfer the Software Product and printer.

EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY ARE EXCLUDED.

Fujitsu Siemens Computers does not warrant that the functions contained in the Software will meet your requirements or that the operation of the Software will be uninterrupted or error free. Fujitsu Siemens Computers reserves the right to make changes and/or improvements in the Software without notice at any time.

2. IN NO EVENT WILL FUJITSU SIEMENS COMPUTERS BE LIABLE FOR LOST PROFITS, LOST DATA, BUSINESS INTERRUPTIONS, OR ANY OTHER DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF OR INABILITY TO USE THIS PRODUCT, EVEN IF FUJITSU SIEMENS COMPUTERS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR ANY DAMAGES CAUSED BY THE ABUSE OR MANIPULATION OF THE SOFTWARE. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU.

3. Fujitsu Siemens Computers will not be liable for any loss or damage caused by delay in furnishing a Software Product or any other performance under this Agreement.

4. Our entire liability and your exclusive remedies for our liability of any kind (including liability for negligence except liability for personal injury caused solely by our negligence) for the Software Product covered by this Agreement and all other performance or nonperformance by us under or related to this Agreement are limited to the remedies specified by this Agreement.

5. California law governs this Agreement.

Termination of License Agreement

This License shall continue until terminated. This license may be terminated by agreement between you and Fujitsu Siemens Computers or by Fujitsu Siemens Computers if you fail to comply with the terms of this Licen se a nd s uc h fai lure is not correc ted w ithi n thirty (30) days after notice. When this License is terminated, you shall return to the place you obta ined the m, the pr inter and all copi es of the Software and documentation.

U.S. Government Restricted Rights

Use, duplication or disclosure by the Government is subject to restrictions as set forth in the Right s in Technic al Data and Comp uter Software clause at FAR 242.227-7013, subdivision (b) (3) (ii) or subparagraph (c) (1) (ii), as appropriate. Further use, duplication or disclosure is subject to restrictions applicable to restricted rights software as set forth in FAR 52.227-19 (c) (2).

Acknowledgement of Terms and Conditions

YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, UNDERSTAND IT, AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS. NEITHER PARTY SHALL BE BOUND BY ANY STATEMENT OR REPRESENTATION NOT CONTAINED IN THIS AGREEMENT. NO CHANGE IN THIS AGREEMENT IS EFFECTIVE UNLESS WRITTEN AND SIGNED BY PROPERLY AUTHORIZED REPRESENTATIVES OF EACH PARTY. BY USING THIS PRINTER, YOU AGREE TO ACCEPT THE TERMS AND CONDITIONS OF THIS AGREEMENT.

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.

Fujitsu Siemens Computers 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. Fujitsu Siemens Computers shall not be held responsible for errors contained herein or any omissions from this material or for any damages, whether direct or indirect, incidental or consequential, in connection with the furnishing, distribution, performance, or use of this material. The information in this manual is subject to change without notice.

Trademark Acknow ledgements

Portions of this manual used by permission of Wyndham Technologies,

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.

Netscape, Netscape Navigator, and the Netscape Communications logo are trademarks of Netscape Communications Corporation.

Code V is a trademark of Quality Micro Systems, Inc. Unix is a registered trademark of X/Open Company Limited. Microsoft, MS-DOS, Windows, Windows 95, Windows 98 and Windows

NT are registered trademarks of Microsoft Corporation. Novell and NetWare are registered trademarks of Novell, Inc. PostScript is a registered trademark of Adobe Systems Inc. Ethernet is a trademark of Xerox Corporation. FTP Software and OnNet are trademarks or registered trademarks of

FTP Software, Inc. NetManage and Chameleon are trademarks or registered trademarks of

NetManage, Inc. Frontier Technologies and SuperTCP are trademarks or registered

trademarks of Frontier Technologies Corporation. Solaris is a registered trademark of Sun Microsystems, Inc. DG/UX is a registered trademark of Data General Corporation. LINUX is a registered trademark of Linus Torvalds. Ultrix is a registered trademark of Digital Equipment Corporation. IRIX is a registered trademark of Silicon Graphics, Inc.

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...................................................................18

Conventions Used In This Manual..........................................20

2 Installation and Configuration............. ...... 21

Installation ..............................................................................21

Connecting to the Network.............................................. .21

Configuration Tools ................................................................23

Configuration Using the Printer Control Panel .................23

IPAssign...........................................................................25

HTML Forms....................................................................25

Configuration Alternatives................................................28

3 Windows Configuration............................. 29

Overview.................................................................................29

Windows Environment Descript ion.............. ....... ...... .............. 2 9

Windows PrintNet Configuration.................. ...........................30

Mandatory .......................................................... .............. 3 0

Optional........................ ...... ....... ...................................... .31

Configuration Using IPAssign ..........................................31

Configuration Using ARP .................................................35

Communicating Across Routers.......................................37

Changing Workgroup Names...........................................38

Changing Destination Names ..........................................38

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 ..............................................49

IPAssign Cannot Find the PrintNet ..................................49

PrintNet Cannot Be Found on the Network......................50

HTML Configuration Forms Will Not Display....................50

Errors Occur when Defining an LPR Printer ....................50

Cannot Browse the PrintNet on the Network ...................51

Printer Errors when Printing or No Output .......................51

TCP/IP Access Problem...................................................52

Web Browser/HTTP Problem...........................................54

Windows NT 4.0 Host Setup Problems............................54

4 Unix Configuration .................................... 57

Overview.................................................................................57

Unix Environment Description ............................... ....... ...... ....57

Unix PrintNet Configuration................ ...... ....... ...... ....... ..........59

Mandatory.......... ...... ....... ...... ....................................... ....59

Optional........................... ...... ....... ...... ....... ...... ....... ..........59

Using ARP .......................................................................60

Using RARP.....................................................................62

Using BOOTP ..................................................................63

Communicating Across Routers... ...... ....... ...... ....... ..........64

Unix Host Configuration......... ...... ....... ...... ..............................65

Manual System V Host Setup ..........................................65

Manual LPR/LPD Host Setup...........................................65

Printing from AIX..............................................................67

Printing with FTP..............................................................67

Direct Socket Printing.......................................................68

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 ................................. 75

Overview.................................................................................75

Novell Environment Description .............................................76

Novell PrintNet Configuration .................................................77

Using HTML Forms............................... ....... ...... ....... ...... .78

Novell Host Configuration.......................................................79

NetWare Version 3.x PSERVER Setup ...........................79

NetWare Version 3.x RPRINTER Setup..........................81

NetWare Version 4.x PSERVER Setup ...........................83

NetWare Version 4.x RPRINTER Setup..........................86

Novell Troubleshooting Tips ...................................................88

NetWare 3.x - No PSERVER Connection........................88

NetWare 4.x - No PSERVER Connection .......................89

6 Novell Configuration for

10/100Base-T Inte rfa ces............ ............... 91

Overview.......................................... ...... .................................91

Novell PrintNet Configuration (10/100Base-T) .......................92

Preferred File Server (NDS and Bindery setups).............93

Setting Password Security

(NDS and Bindery setups) ...............................................95

Adjusting Polling Time (NDS and Bindery setups)...........97

Changing the PrintNet Name

(NDS and Bindery setups) ...............................................98

Changing the PrintNet Frame Type

(NDS and Bindery setups) .............................................100

Table of Contents

Changing the PrintNet Mode

(NDS and Bindery setups) .............................. ....... ...... ..1 01

Setting the PrintNet NDS Context (NDS setups) ...........102

Setting the PrintNet Preferred NDS Tree

(NDS setups) ............................................ ...... ....... ...... ..1 03

Novell Host Configuration (10/100Base-T)...........................104

NDS PSERVER Setup (Netware 4.x) ............................104

Bindery PSERVER Set up

(Netware 3.x and Netware 4.x) ......................................107

Referencing a Bindery Queue in NDS

(Netware 3.x and Netware 4.x) ......................................107

RPRINTER/NPRINTER Setup

(Netware 3.x and Netware 4.x) ......................................108

Troubleshooting (10/100Base-T)..........................................110

PSERVER Setup ...........................................................110

RPRINTER/NPRINTER Setup........................ ....... ...... ..113

Printing Related .............................................................115

7 Monitoring Printers.................................. 119

Implementing Printer Management ......................................119

Agent/Manager Model....................................................119

MIB.................................................................................120

SNMP.............................................................................122

Monitoring Tools...................................................................122

OS/2 TCP/IP ..................................................................122

Monitoring with AIX NetView/6000.................................122

Setting the SNMP Community Name.............................123

8 Commands..............................................125

Command Shell Overview....................................................125

npsh Access Methods............................... ...... ....... ...... ..125

Main npsh Command Prefixes.......................................125

Getting Command Help..................................................1 26

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........................................ 147

PrintNet Security .... ...... ....... ...... ....... ...... ...... ....... ...... ............ 14 7

Users and Passwords ....................................................147

TCP Access Lists...........................................................149

Printer Monitoring and Logging ............................................150

Printer and Print Job Monitoring.....................................150

Printer Logging Through Logpaths.................................151

Downloading Software..........................................................153

Procedure.......................................................................153

PrintNet Naming Schemes .......................... ....... ...... ....... .....156

10 Glossary................................................ 157

Table of Contents

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. Following simple configuration steps, these peripherals can be simultaneously shared with users on the network whether you are using TCP/IP, NetBIOS over TCP/IP, or IPX (Novell

The PrintNet package contains a network interface card to attach itself and the printer to the network.



What Special Featur es are Availa ble?

The PrintNet offers an extensive list of features including:

• built-in HTML forms for easy cross-platform configuration

• availability of printer manager software

• a detailed and easy-to-use command shell built in to the firmware

• multi-level configuration security through passwords, permission

levels, and access lists

• WAN-wide communication access

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

• extensive built-in troubleshooting tools

• built-in “telnet” and “ping” clients

• configurable memory usage by disabling protocol s and desti nati on

services

• multiple destinations/queues for versatile printer manipulation and

distinct print setups

• header and trailer strings to instruct printers on font, pitch, printing,

etc.

• flexible naming conventions

• automatic network connection and frame type sensing

• simultaneous printing across all I/O ports and all supported protocols

• multiple network protocol support

” commands, SNMP, and pre-defined log methods

Interfaces

The PrintNet interfaces with your printer through an Ethernet™ interface connector. Three Ethernet interfaces are available: 10Base2, 10Base-T and 10/100Base-T, which supports 10Base-T or 100Base-T LANs. Some options and indicator switches differ for each Ethernet interface, as described below.

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.

STAT NETERR

Status

Indicators

Grn R ed Grn

OFF

DIP

Switches

123

Figure 1. Status Indicator Lights (10Base2 and 10Base-T)

The LED patterns and the respective indications are given in Table 1.

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

(Default is all switches OFF, as shown.)

ON FLASH ON Hardware Exception

Chapter 1 Interfaces

Operating Modes

The PrintNet has a self test and internally controlled modes. These are:

Power-on Self T est

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. 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.

Table 2. Run Mode and Auto Reset Mode Indicator Descriptions

STAT Rate Indication

OFF flashes ON once per

second

OFF flashes ON 2.5 times

per second

ON flashes OFF 2.5 times

per second

ON flashes O F F o nc e per

2 seconds

Normal Mode, IP address configured

Monitor Mode, IP address not configured

Monitor Mode or Download Mode, IP address not configured

Download Mode, IP address configured

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. With this dipswitch in the “on” posi-

tion, the unit boots up with its factory default settings (including the default IP address) as if it were a new unit. This means the unit uses the factory default settings rather than the settings stored in EEPROM.

With this dipswitch in the “off” position, the unit boots up using the settings in EEPROM rather than the default settings. This dipswitch is in the “off” position from the factory so the new settings you store will be used.

NOTE: Setting this dipswitch “on” will not clear any

settings you have stored in EEPROM. It simply boots the unit in a different state with the settings in EEPROM temporarily ignored.

If you would like to return all the stored settings back to factory defaults, issue the

from default

boot the unit with this dipswitch set to “off” so these new stored settings will be used.

3 Link Integrity Disable. This dipswitch determines

whether link integrity is turned on or off on the unit. For example, it may be necessary to turn link integrity off if the unit is connected to an older hub. Link integrity is only applicable to the 10Base-T interface. The default is “off.”

commands at any point. Just remember to

save default

store tcpip

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.

STAT (Syste m Status)

NET (Data to Network)

Figure 2. Status Indicator Lights and Dipswitches (10/100Base-T)

Run and Auto Reset Modes

DIP Switches

Table 4. Run Mode and Auto Reset Mode Indicator Descriptions

STAT Rate Indication

OFF flashes on once per second Normal Mode, IP address

configured OFF flashes on 2 times per second IP address not configured ON flashes off once per second Download (MOS) ON flashes off twice per second Error ON constantly Indicates link integrity ON flashes off 1/3 second Flashes off 1/3 second each

time a packet is transmitted

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. 10/100Base-T Dipswitch Settings

Dipswitch

Comments

off off Normal operation. With both dipswitches in the “off”

position, the PrintNet boots up using the settings in flash memory rather than the default settings.

on off Factory default settings. With the dipswitches in this

configuration, the PrintNet boots up and all settings stored in flash memory are erased except the Ethernet address and key value.

off on Default IP. With the dipswitches in this configuration,

the PrintNet boots up with factory default settings. However, the stored settings in flash memory are intact. Setting dipswitch 2 to “on” does not clear any settings stored in flash memory; it boots the unit in a different state with the settings in flash memory temporarily ignored.

on on If the PrintNet is connected to a network with link

integrity and then reset to MOS, a download will be forced. If the unit is not connected to a network, it will print a test page.

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 i n

in text.

ping

ipname

is alive

italics

in command syntax, output, and

2 Installation and

Installation

Configuration

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 Ne twork

To attach the PrintNet to a network as illustrated in Figure 3, plug the network cable into the PrintNet connector.

Watch the LEDs in the rear of the printer as they cycle through the power on self test (see page 15). When the test is complete, the STAT led is flashing.

Chapter 2 Installation

Network Connector

Figure 3. Physical Setup

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. A host has to be told where to send the data.

NOTE: Some network environments do not require any network settings

to be configured on the PrintNet. However, all network setups require configuration on the host end.

Configuration Using the Printer Control Panel

The PrintNet settings can be set from the printer control panel. The procedure is described below.

Configuration Using the Printer Control Panel

CAUTION

When the printer is first powered on, the message “ENET IS INIT” displays on the control panel. This process takes about two minutes. Make sure not to change the PrintNet settings while this message is displayed to prevent a loss of PrintNet configuration information. When the initialization is complete, the message “ENET IS READY” displays, and the PrintNet settings may be safely changed from the control panel.

You can set any of three listed parameters from the printer control panel. These parameters are located in the ETHERNET PARAMS menu. The available parameters are:

• IP Address

• Gateway Address

• Subnet Mask

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 instructions.

4. Press the LEFT or RIGHT arrow key until the LCD displays

“ETHERNET PARAMS.”

5. Press the DOWN arrow key to access the “IP Address” parameter.

6. Press the DOWN arrow key to view the current IP Address.

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 select the portion of the IP Address to be changed.

9. Press the DOWN arrow key.

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. 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

Manual

for details.)

Operating Manual

for

Operating

CAUTION

When a change is made from the control panel, the PrintNet is re-

initialized. The messages “ENET IS RESET” and “ENET IS INIT” display on the control panel. This process takes several minutes. Make sure not to shut the printer off or make further changes to the PrintNet settings during this initialization period to prevent a loss of PrintNet configuration information. When the initialization is complete, the message “ENET IS READY” is displayed.

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. IPAssign Sample Interface

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. Make sure your network station can su ccess fully “ over the network.

ping” the PrintNet

Chapter 2 Configuration Tools

3. Direct your Web browser to the Uniform Resource Locator (URL)

Index/Home

http://

“

The PrintNet HTML structure is divided into several menus as shown in Figure 5.

IPaddress

”

(e.g. “http://192.75.11.9”).

Configuration

Network

TCP/IP Windows Novell

Status Help

I/O Port Network

Print Path

d1prn d2prn d3prn d4prn

I/O Port HTTP

About

Administration

Figure 5. PrintNet HTML Structure

NOTE: Online help is available for all HTML pages.

System

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. WWW Printer Status Screen

Chapter 2 Configuration Tools

Configur atio n A lter nat iv es

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. A TCP/IP host uses this command to remotely execute a single command on the PrintNet.

Example:

rsh spike list prn

This command remotely executes the npsh command “list prn” on the PrintNet named

spike

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 Environmen t Description

The PrintNet supports network printing under Windows environments by using TCP/IP. In a Windows NT network protocol whereas with Windows 95 over TCP/IP is used.

Figure 7 shows two of the most common Windows setups you will see with the PrintNet. The ideal configuration is a network printer defined on the NT server to be shared by Windows 95 clients. However, any Windows station can also go directly to the PrintNet.



setup, pure TCP/IP is used as the



or Windows 98, NetBIOS

Chapter 3 Windows PrintNet Configuration

Win 95

Win 95 Win 95

Win 95

NT Server

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. This section offers alternative methods for configuring your PrintNet in a Windows environment and mentions some of the more common optional settings available.

Mandatory

IP Router

Printer

Since TCP/IP is used for Windows printing, the PrintNet must be configured with a minimum of an IP address and subnet mask before it can be seen on the network.

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.

To configure an IP address and subnet mask on your PrintNet:

1. Insert the diskette labeled “IPAssign” into the floppy drive.

2. Load the File Manager or WinFile and look under the floppy drive for an IPAssign self-extracting file.

3. Double click on the IPAssign file to launch the install program.

4. When prompted to install, click on YES to load the InstallShield Wizard.

5. Answer the prompts throughout the wizard.

6. Once the install process is complete, you will be prompted to view the “ReadMe” file. Select “Yes” to read this. Close the file when done.

7. Find the new IPAssign program group and double click on the “IPAssign” icon to load the program.

NOTE: IPAssign will search the network to find the correct device. This

may take several minutes. For larger networks, you may speed the process by powering the printer off and then on again.

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.

NOTE: You can also assign a default router/gateway entry within this

dialogue box allowing your PrintNet to communicate across subnets. This is optional.

11. Click SET when done to assign these TCP/IP settings to the PrintNet. IPAssign will then display two dialogue boxes informing you of its progress.

12. Once you see the message about successfully assigning the settings, click OK. These TCP/IP settings are now in the PrintNet current memory, to be retained until the next power cycle.

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. Please load it manually and go to the URL, “

networkConf.html networkConf.html

IP_address

15. Once your Web browser is loaded and you are prompted for a “User ID,” type “

16. At the “Password” prompt, press ENTER since there is no default password configured and click OK.

17. At the “Network Configuration” HTML form that displays, fill in the PrintNet IP address under the “IP Address” field. Figure 9 shows an example configuration form.

root.”

http://

” (e.g., “http://192.75.11.9/ ”) or use a Telnet server: “Telnet

.”

PrintNetIPaddress

18. Click in the field labeled “Subnet Mask” and fill in the PrintNet subnet mask.

NOTE: If you would like to communicate with the PrintNet from across

routers, you will need to fill in an entry within the “Routing” section. Please see “Communicating Across Routers” on page 37 for more details.

19. Click on the SUBMIT button when done.

20. Turn the printer off, then on again so the changes take effect, or click on the “System” link at the top of the “Network Configuration” HTML form. Once at the “System” form, click on the REBOOT button.

Chapter 3 Windows PrintNet Configuration

Figure 9. Network Configuration HTML Form

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. Log on to a Windows station with TCP/IP loaded and located on the same subnet as the PrintNet.

2. Find the Ethernet address for the PrintNet on the configuration printout. It must be entered as part of this procedure.

3. Use the “ ARP table for the PrintNet. This is the most common syntax for this command:

Syntax:

arp -s

Example for Microsoft TCP stacks:

arp” command to add an entry into the Windows station

ipaddress ethernetaddress

arp -s 192.75.11.9 00:80:72:07:00:60

This example specifies a PrintNet using IP address 192.75.11.9 and Ethernet address 00:80: 72: 07 :00: 60.

4. Check to see if the ARP entry was accepted.

arp -a

You should see an entry in the listed ARP table with the IP address and Ethernet address specified in Step 3.

5. Try to “ your network.

ping” this IP address to see if the PrintNet can be seen on

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://

“ (e.g., “

PrintNetIPaddress

http://192.75.11.9/networkConf.html”).

/networkConf.html”

NOTE: If prompted for a “User ID” and password first, type “

the ID and press ENTER at the password prompt since there is no password by default.

2. At the “Network Configuration” HTML form that displays, click in the field below the “IP Address” heading and type in the IP address for the PrintNet.

3. Under the “Subnet Mask” heading, enter the PrintNet subnet mask.

NOTE: If you would like to communicate with the PrintNet from across

routers, you will need to fill in an entry within the “Routing” section. Please see “Communicating Across Routers” on page 37 for more details.

4. Click on the SUBMIT button when done and physically repower the printer to make the new settings take effect.

root” for

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. In order for hosts across a router to see your PrintNet, it is best to store a default router/gateway within the print server so that any packets destined for another subnet get forwarded to this router automatically. The router (or series of routers) can then take over ensuring the packets get to their final destination on another subnet on your network.

To configure a default router/gateway within the PrintNet:

1. Load a Web browser on your Windows station and direct it to the URL

http://

“ (e.g., “

PrintNetIPaddress

/networkConf.html”

http://192.75.11.9/networkConf.html”).

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there is no password by default.

2. At the “Network Configuration” HTML form that displays, click in the first field below the “Gateway” heading and type in the IP address of the default router/gateway for the PrintNet subnet.

3. Click on the SUBMIT button when done and physically repower the print server to make the new settings take effect.

root” for

Chapter 3 Windows PrintNet Configuration

Changing Workgrou p 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://

“ (e.g., “

PrintNetIPaddress

http://192.75.11.9/networkConf.html”).

/networkConf.html”

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there is no password by default.

2. At the “Network Configuration” HTML form that displays, search for the “Windows (NetBIOS TCP/IP)” section and highlight the “Workgroup Name” field.

3. Type in the new workgroup name for the PrintNet.

4. Click on the SUBMIT button when done and physically repower the print server to make the new settings take effect.

root” for

Changing Destination Names

When defining some printers within Windows environments, the PrintNet requires that you specify a pre-defined destination rather than any name you would like. For example, when creating a new printer under Windows NT, you are presented with a screen similar to Figure 10.

Figure 10. Windows NT Print Setup Dialogue Box

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. To do this:

1. Load a Web browser on your Windows station and direct it to the URL

http://

“ (e.g., “

PrintNetIPaddress

/destConf.html”

http://192.75.11.9/destConf.html”).

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there is no password by default.

2. At the “Print Path Configuration” HTML form that displays, select a destination link from the top of the page to bring up the appropriate destination form. By default, you should see a line near the top of the form showing the destinations listed in Table 6.

3. Once the desired destination HTML form displays, highlight the “Name” field and type in the new name for this destination.

4. Click on the SUBMIT button when done and physically repower the print server to make the new setting take effect.

root” for

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. Define a name to represent this print setup and select the appropriate driver for the printer that will be used in this setup. For printer driver choose “generic text” or Epson “FX1050” or “Proprinter” based on print need.

5. Under the “Print To” field, select “Other...”

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. You will probably use “

9. Click OK when done specifying these two fields.

d1prn.”

You now have a new network printer which relies on the standard TCP/IP print protocol, LPD, to print remotely to a printer with the PrintNet.

Windows NT 4.0 Hos t Setu p

This installation procedure assumes that the PrintNet adapter is configured with the correct IP address, subnet mask and gateway (if

ping

required). In addition, the administrator can “ PrintNet adapter from the server console.

If this is not the case, use the printer front panel or the IPAssign utility to configure the PrintNet adapter before proceeding.

1. Select “Settings:Printers” from the “Start” menu.

2. Double click on the “Add Printer” icon. The “Add Printer Wizard” window is displayed.

” and telnet to the

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. At the “Browse for Printer” dialogue box that displays, double click on the appropriate workgroup containing the PrintNet. By default, the print server falls under the workgroup, “WORKGROUP.”

6. Continue searching the network until you see the PrintNet name,

xxxxxx

“M_ server Ethernet address found when a configuration is printed.

7. Once you see the PrintNet, double click on it to display a list of predefined destinations/queues to choose from.

”, where “

xxxxxx

” equals the last six digits of the print

8. Select a destination/queue that will use “

9. Click OK once you have selected a destination.

10. Back at the network path window, select NEXT since this path should now be filled in for you.

11. At the next window, select the appropriate print driver and click on NEXT.

12. Fill in a name for this new network printer at the next window and decide if you want this to be the default printer. This printer name can be anything you would like as long as it is unique.

13. When prompted for a test page, select either “Yes” or “No” depending on the state of the attached printer and click on FINISH.

NOTE: Windows may ask for a disk or CD-ROM to load the appropriate

printer driver to complete this new printer setup.

There should now be a new printer icon within the “Printers” folder. This new network printer relies on NetBIOS over TCP/IP as the underlying protocol to print to the PrintNet.

d1prn.”

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. Once extracted to a directory, find the “Setup” file and double click on this to load the InstallShield Wizard.

5. Answer the prompts throughout the wizard and select “Yes” to restart your computer at the end.

6. Once your computer is rebooted, open the “Settings:Printers” folder to view your existing printers.

NOTE: PPS will only work with an existing printer. Therefore, if you do

not have an existing printer that you can alter, create one now using any port settings you would like. These will be changed in the following steps.

7. Select the printer that you want to use with PPS and click the right mouse button to bring up a sub-menu.

8. Select “Properties” from this menu to display the current settings for this printer.

9. Click on the “Details” tab to display the printer port settings.

10. Click on the ADD PORT button.

11. At the “Add Port” dialogue box that displays, click on the button labeled “Other.”

12. Click on “TCP/IP Printer Port” within this “Other” list.

13. At the next dialogue box that displays, fill in the host name or IP address of the PrintNet in the first field.

14. Fill in a valid TCP port number on the PrintNet in the second field. The choice is

4400 or 9100 for PRN.

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. If IPX is used, you will have a print queue defined on a Novell file server which your Windows

3.1 stations will send their print jobs to. The PrintNet will then service this

print queue as either a PSERVER or an RPRINTER. Please see Chapter 5, “Novell Configuration” for further details.

If you want to rely on TCP/IP, you will need a third party TCP stack loaded onto your Windows station since TCP/IP support did not automatically come with Windows until the introduction of Windows NT and Windows

95. You may also be running a third party stack if you decided not to use

a Microsoft operating system. Some common TCP stacks are FTP Software's

Chameleon, and Frontier Technologies' allow your Windows 3.1 station to communicate with other TCP/IP devices. This means you can send print jobs to the PrintNet as well.



SuperTCP. In each case, they

OnNet, NetManager's

The most common print method offered with Windows TCP stacks is LPR/LPD, a multi-platform remote printing protocol used on everything from PCs to mainframes. The LPR print setup is very simplistic, involving only two parameters:

1. PrintNet IP address. The IP address or host name of the print server you want to print to.

2. PrintNet destination/queue. A pre-defined name on the print server telling the device which I/O port to send the jobs to. The standard name for the PRN port is “

NOTE: This destination name is case sensitive and by default, all names

are lowercase.

d1prn.”

Windows Troubleshooting T ips

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. Give a detailed description of your network and the components attached.

Please follow these tips to determine what the problem may be with your PrintNet configuration.

IPAssign Cannot Find the PrintNet

• Have you loaded IPAssign onto a Windows station on the same

subnet as the PrintNet? IPAssign cannot see print servers across routers unless BOOTP broadcast packets can travel from subnet to subnet.

• Have you waited several minutes for IPAssign to recognize the

PrintNet or have you repowered the printer to speed this identification process?

• Do you have a DHCP, RARP, or BOOTP server running that may be

providing the PrintNet with an IP address upon bootup? If so, IPAssign is not needed to assign an IP address to the print server.

NOTE: If the PrintNet has an IP address, it will no longer send out a

BOOTP packet. This means IPAssign will not be able to see the device on the network.

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.

• If you look at the back of the printer, is the STAT LED flashing once a

second or is it quicker than that? A slower, once-a-second rate tells you that the print server is in fact configured with an IP address. A 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.

HTML Configuration Forms Will Not Display

• Can you “ping” the PrintNet from your Windows station? If not,

please refer to “PrintNet Will Not Talk on the Network” above.

• Have you used the correct URL for the PrintNet home page? It should

http://

be “

http://192.75.11.9”).

(e.g., “

PrintNetIPaddress

”

Errors Occur when Defining an LPR Printer

• Can you “ping” the PrintNet from your Windows NT station? If not,

please refer to “PrintNet Will Not Talk on the Network” above.

• Did you specify the correct IP address or host name for the PrintNet

in the first field of the “Add LPR Compatible Printer” box?

• Did you specify a valid destination/queue on the PrintNet in the

second field of the “Add LPR Compatible Printer” dialogue box? If so, did you also enter it in lowercase letters?

Cannot Browse the PrintNet on the Network

• Have you looked under the right Windows workgroup? By default, the

PrintNet will be found under “WORKGROUP.”

• Are you able to browse other Windows stations and devices on the

network from this same station?

• Has this Windows station been given enough time to update its

registry so it can see this newly added workgroup device? Sometimes Windows stations can take considerable time, depending on the size of the network.

Printer Errors when Printing or No Output

• Is there a large job currently printing taking up all of the printer

resources? Usually when printing from Windows 95 stations, a busy printer can cause Windows to display a printer error message. This is because it demands immediate printer attention rather than holding the data until the printer is ready again. The best way around this is to use a central spooling station like an NT server.

• Have you tried restarting the spooler under “Control Panel:Services”?

Sometimes this is needed to get printing started.

NOTE: As a last resort, you may want to reboot the Windows station.

Sometimes this is the only option to completely clear this situation. The PrintNet usually has nothing to do with this problem.

Chapter 3 Windows Troubleshooting Tips

TCP/IP Access Problem

If you can “ 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. 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

Operating Manual

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.

To add/delete a TCP access list entry, refer to “TCP Access Lists” on page 149.

NOTE: When the following procedure is used, the TCP access list will be

To reset all TCP/IP values to the factory defaults when access is impossible:

ping

” the printer from a workstation, but you cannot Web

for configuration menu information). From the

cleared but all IP addresses will need to be entered again after the procedure is complete.

1. Obtain a printer configuration printout using the control panel. See the

Operating Manual

2. Power off the printer.

3. On the PrintNet Interface, place SWITCH 2 in the down position.

4. Power on the printer and wait for the ONLINE state.

5. On the PrintNet Interface, place SWITCH 2 in the up position.

for configuration menu information.

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 “

8. Telnet into the PrintNet using the same IP address as above. Log in

9. At the system prompt, enter:

ipaddress

ping

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.

as root with no password.

> <

MACaddress

” this IP address to see if the PrintNet can be seen on

store tcpip from default config http on save 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. Enter the following command:

config http on

If you are still experiencing difficulty accessing or browsing the printer, contact technical support for further assistance.

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.

ping

If you cannot “ subnet mask, and default gateway are set correctly by checking the Ethernet Parameters menu from the operator panel. See the

Manual

If you can “ pages, perform the following procedure to verify the PrintNet HTTP is turned on.

1. Telnet into the PrintNet and log in as root with no password.

2. At the system prompt enter the following commands:

for configuration menu information.

ping

config http on save reset

3. After approximately 30 seconds, point your browser to the PrintNet IP address. The printer web pages should now be accessible.

” the PrintNet IP address, make sure the IP Address,

” the PrintNet IP address but cannot access the web

Operating

If you are still experiencing difficulty accessing or browsing the printer, contact technical support for further assistance.

Windows NT 4.0 Host Setup Problems

The installation procedure covered earlier in this chapter assumes that the PrintNet adapter is configured with the correct IP address, subnet

ping

not

” the

mask and gateway (if required), and that the administrator can “ and telnet to the PrintNet adapter from the server console. If this is case, use the printer front panel or the IPAssign utility to configure the PrintNet adapter before proceeding.

The PrintNet installation for Windows NT 4.0 also requires “Microsoft TCP/IP Printing” service on the server. To install this service, click on the Network icon in the Control Panel and click on the “Services” tab. Click on “Add Service” and select “Microsoft TCP/IP printing.”

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 betwe en the NT se rver and the PrintNet card. Check cabling, IP address settings, gateway, etc.

• Test page does not print or prints incorrectly.

1. Is the printer online? Re-send test page.

2. The print queue name in step 6 should be “d1prn”; however, the

name can be changed. To verify the queue names, print an Ethernet Test Page. Refer to your information.

3. The Printronix NT print driver requires P-Series emulation active on the printer. The Generic/Text driver should print in any printer emulation.

4. Delete then re-install Microsoft TCP/IP Print service on the server.

Operating Manual

for

Chapter 3 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

XTerm

Linux

Solaris

Ultrix

SparcStation SunOS 4.1.1

SCO

XTerm

Printer

OSF/1

IRIX

IP Router

HP-UX

Figure 13. Unix Integration

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. To configure these options, see “Configuration Tools” on page 23.

Optional

Additional settings, like routing entries, can be configured allowing for communication across subnets.

Configuration of the PrintNet can be done from the control panel or through host commands. To configure these options, see “Configuration Tools” on page 23.

Mandatory

Chapter 4 Unix PrintNet Configuration

Using ARP

To configure the Ethernet Interface with its TCP/IP settings using a

manual “

arp -s

For the “aix” command, the syntax is:

aix -s

To use either of these commands:

1. Log on to a Unix station as superuser or root. This station must be

2. Find the Ethernet address for the PrintNet by printing a configuration

arp” command, the syntax is:

ipaddress ethernetaddress

ether ipaddress Mac_address

located on the same subnet as the PrintNet since ARP is limited to subnets.

or reading it from the control panel. It must be entered as part of this procedure.

3. Use the “ table for this PrintNet. Here is the most common syntax for this command:

arp -s

Example for Microsoft TCP stacks:

arp” command to add an entry into the Unix station ARP

ipaddress ethernetaddress

arp -s 192.75.11.9 00:80:72:07:00:60

This example specifies a PrintNet using IP address 192.75.11.9 and Ethernet address 00:80:72:07:00:60.

4. Verify that the ARP entry was properly applied.

arp -a

You should see an entry in the listed ARP table with the IP address and Ethernet address specified in Step 3.

5. Try to “ your network.

ping” this IP address to see if the PrintNet can be seen on

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://

“ (e.g., “

PrintNetIPaddress

/networkConf.html”

http://192.75.11.9/networkConf.html”).

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there is no default password.

2. At the “Network Configuration” HTML form that displays, click in the field below the “IP Address” heading and type in the IP address for the PrintNet.

3. Under the “Subnet Mask” heading, enter the PrintNet subnet mask.

NOTE: If you would like to communicate with the PrintNet from across

routers, you will need to fill in an entry within the “Routing” section. Please see “Communicating Across Routers” on page 64 for further details.

4. Click on the SUBMIT button when done and physically repower the print server to make sure the new settings are in effect.

root” for

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. If

it is running, send an HUP signal to it with the “

Syntax:

kill -HUP

where

3. Power on the PrintNet so that it immediately sends out an RARP request. Wait one minute to allow the address assignment process to complete. You should see the STAT LED on the PrintNet interface slow down indicating it knows about an IP address to use.

pid

is the process ID of the RARP daemon.

kill” command:

4. Try to “ if it can be seen on your network.

NOTE: You will only be able to communicate with the PrintNet from a

ping” the PrintNet IP address from a local Unix station to see

network station on the same subnet as the print server. The PrintNet needs to be told about a default router/gateway so any packets that come in from a different subnet can be returned via this gateway. Please see “Communicating Across Routers” on page 64 to set this up.

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.

Syntax:

PrintNetIPname

netmask

:sm=

homedirectory

:hd= :bf=null:\

defaultgateway

:gw= :ht=ethernet:\

ethernetaddress

:ha=

ipaddress

:ip=

timeserver

:ts= :to=

timezone

Example:

spike:\ :sm=255.255.255.0:\ :hd=/usr/null:\ :bf=null:\ :gw=192.75.11.1:\ :ht=ethernet:\ :ha=008072070060:\ :ip=192.75.11.9:\ :ts=192.75.11.7:\ :to=25200:

2. Turn the PrintNet on so that it immediately sends out a BOOTP request. Wait one minute to allow the IP address assignment process to complete. You should see the STAT LED, on the PrintNet interface, slow down indicating it knows about an IP address to use.

3. Try to “ it can be seen on your network.

ping” the PrintNet IP address from a network station to see if

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.

After following one of the PrintNet configuration methods mentioned (other than the BOOTP method), you will most likely only be able to communicate with the print server from the same subnet. This means any host across a router will not be able to see your PrintNet. In order to communicate across a router, it is best to store a default router/gateway within the print server so that any packets destined for another subnet get forwarded to this router automatically. The router (or series of routers) can then take over ensuring the packets get to their final destination on another subnet on your network.

To configure a default router/gateway within the PrintNet:

1. Load a Web browser on your Unix station and direct it to the URL

http://

“ (e.g., “

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there is no default password.

3. Click on the SUBMIT button when done and physically repower the print server to make sure the new setting is in effect.

PrintNetIPaddress

/networkConf.html”

http://192.75.11.9/networkConf.html”).

root

” for

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 interface file is used for each defined printer and in the case of any System V print setup involving a PrintNet, the RSHD protocol is used to transfer data from the host to the print server.

To manually configure a new System V printer on a Unix station, create a dummy device file that acts as a locking mechanism between contending print jobs.

Syntax:

touch /dev/

where

portname

Example:

PrintNetname

PrintNetname.portname

is one of its four I/O ports.



, HP-UX, DG/UX, etc.). This means an

is the host or IP name of the print server and

touch /dev/spike.prn

Manual LPR/LPD Host Setup

The PrintNet also supports Unix operating systems which follow a BSD print system (e.g., SunOS 4.1.x). This means a printcap file is used to define all printers available on the host and interface scripts are not commonly used. Instead, LPR/LPD printers are defined.

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.

Syntax:

printername:

:sh:pw#80:mx#0:\

PrintNetname

:rm= :rp=

PrintNetdestination

:lp=:\ :sd=/usr/spool/lpd/ :lf=/usr/spool/lpd/ :af=/usr/spool/lpd/

where

printername PrintNetname PrintNetdestination

device. Example:

P5000: :sh:pw#80:mx#0:\ :rm=spike:\ :rp=d1prn:\ :lp=:\ :sd=/usr/spool/lpd/ P5000:\ :lf=/usr/spool/lpd/ P5000/log:\ :af=/usr/spool/lpd/ P5000/acct:

2. Create the spool directory specified by the “sd=” entry in the printcap

entry for this printer.

is any name you would like to give to this new printer,

is the host or IP name of the print server, and

is one of the pre-defined destinations/queues on the

printername printername printername

:\ /log:\ /acct:

Example:

touch /usr/spool/lpd/ P5000

3. Create the log and account files specified by the “

entries in the printcap entry for this printer.

Example:

lf=

” and “

af=

touch /usr/spool/lpd/P5000/log touch /usr/spool/lpd/P5000/acct

4. Change permissions and ownership on the spool directory and

everything within it.

”

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. This means, to set up a new printer under this operating system, you only need to define these two parameters:

1. PrintNet IP address. The IP address or host name of the print server you want to print to.

2. PrintNet destination/queue. A pre-defined name on the print server telling the device which I/O port to send the jobs to. You will most

likely use “

d1prn” for the PRN.

Printing with FTP

Print jobs can also be sent to the PrintNet using the File Transfer Protocol (FTP). To do this:

1. On your network station, change to the directory containing the file you want to print.

2. Open an FTP session with the PrintNet.

Syntax:

ftp

PrintNetIPaddress

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

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 “

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. By default, ASCII is set for text-only files but if you need to print both text and graphics, select binary using the “

9. Place the file to be printed within this directory on the PrintNet so it can be spooled and printed.

dest

directory.

d1prn” for the PRN port.

bin” command.

Syntax:

put

filename

10. Close the FTP session, unless you have more jobs to print.

Syntax:

quit

Direct Socket Printing

Within TCP/IP environments, there are some setups which require the host to print directly to a TCP port number on the PrintNet, bypassing all of the higher level destination/queue names. If you run into a setup which requires this, you will need to define two parameters for a new print setup:

1. PrintNet IP address. The IP address or host name of the print server you want to print to.

2. PrintNet TCP port number. A pre-defined number for the I/O port on the print server. 9100 is the default port number.

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.

Unix T roublesh ooting Tips

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?

PrintNet Cannot be Found on the Network

6. Give a detailed description of your network and the components attached.

Please follow these tips to determine what the problem may be with your PrintNet configuration.

PrintNet Cannot be Found on the Network

• Have you configured the PrintNet with 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 Unix station

on the same subnet? Currently, the print server can only be seen locally unless you configured it with a routing entry.

• If you look at the back of the printer, is the STAT LED flashing once a

second or is it quicker than that? A slower, once-a-second rate tells you that the print server is in fact configured with an IP address. A

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.

• Is the PrintNet able to communicate with the attached printer? To test

this, you can:

telnet” to the print server (e.g., “telnet 192.75.11.9”)

1. “ and log in as “

root.”

2. Enter the command “

3. Execute “

This test will send the same text line over and over to the attached printer.

stop

start fox

prn

” right after starting the test.

prn

.”

• Is the job getting stuck in the Unix host queue? If so, check that the

printer is online. If it is, there is a configuration error on the Unix station so creating a new print setup may be needed.

• Is the control panel showing any activity to indicate it is receiving

data? If so, but there is nothing printing, check to see if a manual form feed is needed. Also, ensure that the printer can support the type of job coming through.

• Do all jobs fail or just certain ones? For example, is it possible that

jobs from a certain application are the only ones to fail? If so, check the type of data it sends to make sure it matches the printer emulation. Check the application printer configuration for mistakes.

• If you are using System V, was the spooler restarted?

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. The printer may be told to do a linefeed but the Unix job does not specify anything about a carriage return to follow this.

To fix this, carriage return insertion must be enabled somewhere in the print setup. The easiest and most common location is on the PrintNet

itself within the appropriate model. The feature is called “onlcr” and the command syntax is:

set model save

For example, if printing to the destination, d1prn, the associated model is m1. Therefore, the command is:

set model m1 stty onlcr save

modelname

stty onlcr

No Form Feed or Extra Page Comes Out

Unix text jobs may also have problems outputting the last page of a job especially when the BSD Remote (LPD) print method is used. This means the form feed button has to be pressed on the printer to get this last page out.

To make this process automatic, tell the PrintNet to handle this task by setting this feature “on” in the appropriate model. The command syntax is:

set model save

modelname

trailer $FF

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

1. The TCP list must have an entry added to grant access to this workstation.

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

Operating Manual

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.

To add/delete a TCP access list entry, refer to “TCP Access Lists” on page 149.

NOTE: When the following procedure is used, the TCP access list will be

To reset all TCP/IP values to the factory defaults when access is impossible:

ping

” the printer from a workstation, but you cannot Web

for configuration menu information). From the

cleared but all IP addresses will need to be entered again after the procedure is complete.

1. Obtain a printer configuration printout using the control panel. See the

Operating Manual

2. Power off the printer.

for configuration menu information.

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 “

8. Telnet into the PrintNet using the same IP address as above. Log in

9. At the system prompt, enter:

ipaddress

ping

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.

as root with no password.

> <

MACaddress

” this IP address to see if the PrintNet can be seen on

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. Enter the following command:

config http on

If you are still experiencing difficulty accessing or browsing the printer, contact technical support for further assistance.

Chapter 4 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 4.1

NetWare Workstation

File Server

NetWare Workstation

NetWare 4.1 File Server

NetWare Workstation

Bridge/Router

NetWare Workstation

Printer

Figure 14. Novell Integration

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. The NDS context in which the print server object was

created. This option is required if you create the print server object in a different context from the context the file server object for the file server that you logged in with is on.

• NDS Tree. The NDS tree the print server object was created in. This

is only needed if your environment uses more than one NDS tree.

• Mode. The mode the PrintNet will run in. This can be either auto,

bindery, or NDS. The default is auto so that the PrintNet can autosense which mode it should run in. See “NetWare Version 4.x

RPRINTER Setup” on page 86 for information on what to do when using both bindery and NDS file servers at the same time.

• Preferred File Server. In a bindery setup, this specifies the file

server that the print server object was created on. In an NDS setup, this specifies a file server(s) 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.

For additional information about these options, see Chapter 6, “Novell

Configuration for 10/100Base-T Interfaces”.

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

xxxxxx

the format “M_ PrintNet Ethernet address found on a configuration printout or control panel settings under Ethernet parameters, MAC Address (e.g., M_071C1A).

To use the HTML forms to define a print queue, do the following:

1. Load a Web browser on a network station that can communicate with the print server over TCP/IP. The command to change the print server name is:

Syntax:

store pserver name

Example to change the name to micro1:

store pserver name micro1

2. Direct your Web browser to URL

http://

“

http://192.75.11.9/adminConf.html”)

(e.g., “

” where “

newname

PrintNetIPaddress

xxxxxx

” equals the last six digits of the

/adminConf.html”

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there is no password by default.

3. At the “Administration Configuration” HTML form that displays, highlight the field beside the “Name” heading and type in the new name of the print server.

4. Click on the SUBMIT button when done and physically repower the printer to make the new setting take effect.

root” for

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 informati on .

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.x PSERVER Setup

To configure a print queue on a NetWare 3.1x network:

1. Log on to the Novell file server as supervisor.

2. Enter PCONSOLE.

3. Select “Print Queue Information” from the PCONSOLE Main Menu.

4. Press INSERT to add a new queue to the list of currently defined queues showing.

NetWare Version 3.x PSERVER Setup

5. Type in the name of this new queue when prompted and press ENTER. This can be any name you would like.

6. Press ESCAPE to return to the Main Menu.

7. Select “Print Server Information” and press ENTER.

8. Press INSERT when the list of existing print servers displays.

9. Type the name of the PrintNet when prompted for a print server name and press ENTER when done. By default, the PrintNet is named

xxxxxx

“M_ Ethernet address found on configuration printouts or reading MAC address on control panel. (e.g., M_071C1A).

10. Back at the print server list, select this newly defined PrintNet and press ENTER.

11. Select “Print Server Configuration” from the menu that displays.

12. Select “Printer Configuration” from the next menu to display a list of configured printers.

” where “

xxxxxx

” equals the last six digits of the print server

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. Press ESCAPE again to return to the “Print Server Configuration” menu.

19. Select “Queues Serviced by Printer.”

20. Select this new printer from the printer list that displays and press ENTER.

21. At the empty queue list that displays, press INSERT.

22. Select the queue created in step 5 and press ENTER.

23. When prompted for the priority, press ENTER to select the default or select a priority.

24. Press ESCAPE until back at the PCONSOLE Main Menu.

25. Repower the printer.

26. Wait two minutes and then select “Print Queue Information” from the PCONSOLE Main Menu.

27. Select this new queue from the menu that displays. Select “Currently Attached Servers” to see which print server is servicing this queue.

At this point, the PrintNet name (e.g., M_071C1A) should show within this window. This means the PrintNet knows about this new Novell print queue it must service as a PSERVER. Therefore, it will poll this queue regularly looking for jobs to print.

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.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. If you have only Novell available, you will need to use a PC, laptop, or terminal.

NOTE: If you use HTML configuration, you will need to go to the

“Network Configuration” HTML form (i.e.,

http://

“ (e.g., “ look under the “Novell” section. The settings in the following step are found there. If using a Telnet session, you will need to manually execute the commands listed in the next step.

PrintNetIPaddress

/networkConf.html”;

http://192.75.11.9/networkConf.html”) and

2. Store the RPRINTER settings on the PrintNet. This will refer to an existing PSERVER.NLM on the file server or to one that you will create later in these steps.

Syntax:

store rprinter add

PSERVERname printernumber

PrintNetdestination

Example for an RPRINTER servicing printer 0 of the PSERVER.NLM called pserver1 and sending jobs to the PrintNet destination d1prn:

store rprinter add pserver1 0 d1prn

3. Leave this PrintNet login session and log on to the NetWare 3.x file server as Supervisor.

4. Load a PSERVER.NLM if there is not one loaded already. This will be the PSERVER that the PrintNet services as an RPRINTER so it must match the PSERVER name given in step 2.

5. Enter PCONSOLE.

6. Select “Print Queue Information” from the PCONSOLE Main Menu.

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 pres s ENTE R.

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. Select “Print Server Configuration” from the menu that displays.

14. Select “Printer Configuration” from the next menu to display a list of configured printers.

15. Select an item from the list (i.e., either an existing printer name or a “Not Installed” one) to display the printer configuration window.

16. Assign a name (if not an existing printer) to this printer.

17. At the “Type” field, select “Remote Other/Unknown.”

18. Press ESCAPE to save the changes.

19. Press ESCAPE until back at the “Print Server Configuration” menu.

20. Select “Queues Serviced by Printer” to display a list of defined printers.

21. Select the printer you just defined and press ENTER.

22. At the list of queues that displays, press INSERT to add a queue to the list.

23. Select the queue defined and press ENTER.

24. When prompted for a priority, press ENTER to select the default or select a priority.

25. Press ESCAPE until you have exited PCONSOLE.

26. Reload the PSERVER.NLM that the PrintNet is to service as an RPRINTER.

27. Repower the PrintNet by turning the printer off and then back on.

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. If you are setting up a NetWare 4 environment, the destination must be renamed to uppercase to match the PCONSOLE entry.

The PrintNet can be used in a NetWare 4 environment with either of the following options:

• Set the PrintNet up as a PSERVER, replacing a dedicated printer.

• Set the PrintNet up as an RPRINTER, interacting with an existing

PSERVER (see page 86).

NOTE: Following a PSERVER setup, bindery emulation is required. To configure the PrintNet as a PSERVER in a NetWare 4 environment:

1. Log in to the Novell as supervisor.

2. Enter PCONSOLE.

3. Press F4.

4. Select PRINT QUEUES.

5. Press INSERT to add a queue.

6. Type in new queue name and press ENTER.

7. Press ESCAPE.

8. Select PRINT SERVERS.

9. Press INSERT to add the new print server.

10. Type the name of the PrintNet. By default, it is “M_

xxxxxx

“ (e.g., M_000BF5).

11. Select this new print server and press ENTER.

” equals the last six digits of the Ethernet address

xxxxxx

” where

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. Select a priority and press ENTER. Priority 1 should be sufficient.

19. Press ESCAPE until you are back to Main Menu.

20. Reboot the Print Server by repowering the printer.

21. Check the CURRENTLY ATTACHED SERVERS and verify the print server is active.

22. Press ESCAPE until you are out of the PCONSOLE.

Even though the entire print set up is done through PCONSOLE, you may want to communicate directly with the print server in order to modify settings, monitor the unit, etc. To communicate with the print server, the optional host software, executable program that can be run from a DOS prompt on a NetWare workstation.

npsh.exe performs the following:

npsh.exe, is included. npsh.exe is a DOS

npsh nvplist

Lists all of the PrintNet devices on the network; each name is in the

default format “M_ unit Ethernet address). This is regardless of whether it is configured as a PSERVER or an RPRINTER.

npsh

Starts a Telnet-like session with the named print server, allowing you to configure, monitor, and troubleshoot the unit with the built-in command set.

unitname

xxxxxx

” (where “

xxxxxx

” equals the last six digits of the

NetWare Version 4.x PSERVER Setup

npsh

Initiates a single Command with guest access only to the unit instead of entering into a complete sess io n.

To communicate with the unit using

1. From a DOS prompt on a Novell workstation, begin an npsh session

npsh

2. To obtain root access to the unit, type:

unitname command

npsh.exe:

with the unit.

unitname

Starts a Telnet-like session with the named print server with guest access only.

supervisor

A standard login screen is displayed prompting you for the login name and password.

3. Login to the unit as root user.

root

NOTE: Root users require the use of a password as configured in the

unit user list.

4. Enter the password. If this password is not yet set, press enter at the password prompt. Otherwise, enter the password that is already stored in the unit.

password

You are now logged in to the unit as a root user and can access any npsh command on the unit.

NOTE: Because

problems communicating across a router.

npsh.exe makes use of broadcasts, you may have

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. Using PCONSOLE, bindery mode, create a bindery printer server object whose name matches that of the PrintNet at the root context of the 4.1x box (i.e., M_03092B). After creating the bindery PrintServer on the 4.1x server, reboot PrintNet and use the

pserver

Test Page out to make sure there is a successful server login.

2. Using either PCONSOLE in NDS mode, or NWADMIN: a. create an NDS queue (any name you want), or simply use an

command via a Telnet or npsh session, or print the E-net

existing one;

debug Novell

b. create a print server to use (any valid name, or choose one

already in existence);

c. create a printer object to use with the print server object you

chose or created, and attach it to the chosen queue;

NOTE: The 4.1x queue name, print server name, and printer object don’t

have to match any PrintNet name; multiple printers can be

defined, but only one print server can be attached to. Example: NDS queue name: Finance

NDS print server name: Fin_Q NDS printer name: Fin_Prt_1 NDS printer name: Accounting_Prt_1

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 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. Assume for our example that one printer previously existed (number 0), and we are adding two more, whose numbers became 1, and 2.

NOTE: On the load command you must strictly follow case of the name

(this is not required on PrintNet).

4. Via a Telnet or npsh session create RPRINTER attachments:

load pserver Fin_Q

store rprinter add Fin_Q 1 d1prn

This command assigns destination d1prn as the RPRINTER 1 service path.

store rprinter add Fin_Q 2 d4prn

This command assigns destination d4prn as the RPRINTER 2 service path.

For PrintNet entries, case does not have to be observed. Also, if you

want to change the destination names from d

set dest <

use the save command so these reappear after a reboot.

dest

> name <

new name

prn, do so first with the

command, being sure to

5. Reboot the PrintNet adapter (power the printer off and on, or use the

reset

command) so the new RPRINTER service names are

broadcast.

6. Open a Telnet or npsh session and log into PrintNet. Wait a minute or two, then use the your entries. You could also do this by looking at the connection status on the 4.1x PSERVER printer status entries.

7. If you add, delete or change RPRINTER entries on PrintNet or 4.1x console, you should always unload and reload the pserver.nlm module to register the changes. The PrintNet can be configured and ready before the pserver.nlm is reloaded, or PrintNet can be reset after pserver.nlm is reloaded.

8. A web browser can also be used to see the RPRINTER attachments, etc. and status.

list rprinter

command, and you should see

Chapter 5 Novell Troubleshooting Tips

Novell Troubleshooting Tips

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. Give a detailed description of your network and the components attached.

Please follow these tips to determine what the problem may be with your PrintNet configuration.

NetWare 3.x - No PSERVER Connection

• Has the PrintNet been power cycled once the PCONSOLE steps

were completed? This will make the print server boot up and realize which print queue and file server it needs to service.

• Is the PrintNet already servicing a queue on another file server? If so,

it cannot service another file server at the same time.

• When defining a new “print server” within PCONSOLE, did you

use the correct name for the PrintNet (e.g., M_071C1A)? By default, it

xxxxxx

only recognizes itself as “M_ six digits of its Ethernet address found on the configuration printout.

” where “

xxxxxx

” equals the last

• When defining a new “printer name” within PCONSOLE, did you

use a pre-defined destination/queue rather than a name of your own? By default, the PrintNet only recognizes names like “ other names will be ignored by the device.

d1prn.” All

• Is the PrintNet in Bindery mode as seen under the “list

pserver

server, it must be set to handle Bindery services. The default setting is Bindery.

” output on the device? If servicing only a NetWare 3.x file

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.x - No PSERVER Connection

• Has the PrintNet been power cycled once the PCONSOLE steps

were completed? This will make the print server boot up and realize which print queue and file server it needs to service.

• Is the PrintNet already servicing a queue on another file server? If so,

it cannot service another file server at the same time.

• When defining a new “print server” within PCONSOLE, did you

use the correct name for the PrintNet (e.g., M_071C1A)? By default, it only recognizes itself as “M_ six digits of its Ethernet address found on the configuration printout.

xxxxxx

” where “

xxxxxx

” equals the last

• When defining a new “printer name” within PCONSOLE, did you

use a pre-defined destination/queue rather than a name of your own? By default, the PrintNet only recognizes names like “ other names will be ignored by the device.

d1prn.” All

• Is the PrintNet in Bindery mode as seen under the “list

pserver

server, it must be set to handle Bindery services. The default setting is Bindery.

” output on the device? If servicing only a NetWare 4.x file

• 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.

Chapter 5 Novell Troubleshooting Tips

6 Novell Configuration for

Overview

10/100Base-T Interfaces

This chapter provides additional information for Novell environments using the 10/100Base-T interface, including:

1. Pr intNet 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. This section includes: NDS PSERVER setup, Bindery PSERVER setup, referencing a Bindery queue in NDS, and RPRINTER/NPRINTER setups.

3. Troubleshooting tips. This section covers PSERVER setups, RPRINTER/NPRINTER setups, and printing related problems.

The information in this chapter does not apply to Novell environments using the 10Base-T and 10Base2 interfaces.

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. The print server setup in a Novell environment is much simpler than that

required in a TCP/IP one. No addresses, masks, or router entries are necessary and in most cases, the PrintNet can simply be connected to the network, turned on, and then configured for printing from a Novell station through PCONSOLE or Netware Administrator. See Figure 15 for an example of a Novell network, showing the use of file servers and how they relate to the print server.

However, there are some optional parameters you may wish to change such as the preferred file server(s), print server password, polling time, frame type, print server name, NDS context, and NDS preferred tree. The following sections describe these optional parameters.

NetWare Workstation

NetWare 4. 1 File Server

NetWare Workstation

Bridge/Router

Printer

Figure 15. Novell Integration

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. This feature is useful in a large Novell network so that the PrintNet does not ignore important file servers. If you are setting up the PrintNet to work with a Bindery file server, it is a good idea to set a preferred server on the PrintNet.

To view which file servers the PrintNet does acknowledge at a given time, use the

for more information.

debug nest fserver

Adding Preferred File Server

HTML Method

1. Load a Web browser on a network station that can communicate with the print server over TCP/IP.

command. See Chapter 8, “Commands”,

2. Direct your Web browser to URL:

http://

“ (e.g. “

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there’s no password by default.

3. Look under the “Novell” section and add the name of the preferred file server in the “File Server” field.

4. Click on the SUBMIT button when done and physically re-power the print server to make the new settings take effect.

PrintNetIPaddress

/networkConf.html”

http://192.75.11.9/networkConf.html”).

root

” for

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 “

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

3. At the prompt, enter:

store pserver novell fserver add

where add as a preferred file server. This adds the specified file server as a preferred file server on the PrintNet.

4. Reset the unit to ensure the changes take effect.

:root>

fservername

is the name of the Novell file server you want to

root

” for

reset

Removing Preferred File Server

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://

“ (e.g. “

PrintNetIPaddress

/networkConf.html”

http://192.75.11.9/networkConf.html”).

root

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there’s no password by default.

3. Look under the “Novell” section and remov e the nam e of the preferred file server from the “File Server” field.

4. Click on the SUBMIT button when done and physically re-power the print server to make the new settings take effect.

” for

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 “

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

3. At the prompt, enter:

store pserver novell fserver del

where remove as a preferred file server.

4. Reset the unit to ensure the changes take effect.

:root>

fservername

is the name of the Novell file server you want to

root

” for

reset

Setting Password Securit y (NDS and Bindery setups)

Besides the general security measures, a Novell setup provides further password security. A password can be set on the PrintNet and within your PCONSOLE or Netware Administrator setup so that when the PrintNet tries to login to the file server, the passwords are compared.

To set the password on the Novell host for use in a PSERVER setup, you will need to:

Netware 4.x

1. Login to NetWare Administrator as a user with security equal to “Admin” on your Novell host.

2. Double click on the print server object you are using for your setup. This will bring up the print server objects details pages.

3. Select the “Change Password...” button on the “Identification” page.

4. At the prompts, type and re-type the new password. Press OK when you are finished.

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

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.

supervisor

on your Novell host.

Print Server Setup - 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://

“ (e.g. “

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there’s no password by default.

3. Look under the “Novell” section and add the new password to the “Pserver Password” field.

PrintNetIPaddress

/networkConf.html”

http://192.75.11.9/networkConf.html”).

root

” for

NOTE: The passwords entered in Netware Administrator or PCONSOLE

must match the password set on the unit.

4. Click on the SUBMIT button when done and physically re-power the printer to make the new settings take effect.

Print Server Setup - Manual (Telnet) Method

1. Telnet to the print server. This will bring up a login screen:

telnet

NOTE: If prompted for a “User ID” and password first, type in “

ipaddress

root

” for the ID and press ENTER at the password prompt since there’s no password by default.

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

3. At the prompt, enter:

store pserver novell passwd

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.

:root>

password

reset

Adjusting Polling Time (NDS and Bindery setups)

To set the poll time the PrintNet will use when checking for new jobs under a PSERVER setup:

Netware 4.x

1. Login to NetWare Administrator as a user with security equal to “Admin” on your Novell host.

2. Double click on the printer object you wish to change the poll time for. This will bring up the printer objects details pages.

3. Click on “Configuration” to display the configuration page.

4. Change the “Service Interval” to the desired number (in seconds).

NOTE: You may also want to change the “Service mode for forms” to

“Change forms as needed”. If you do not do this, the PrintNet will need to poll the file server twice as much to get all the information it needs.

5. Re-power the PrintNet by turning the printer off and on to make the changes take effect.

Netware 3.x

1. Enter PCONSOLE as

2. Select “Print Server Information” from the main menu, and press ENTER.

supervisor

on your Novell host.

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_ 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. Select the printer you wish to alter the poll time for and press ENTER.

7. Change the “Sampling Interval” to the desired number (in seconds).

NOTE: You may also want to change the “Service mode for forms” to

“Change forms as needed”. If you do not do this, the PrintNet will need to poll the file server twice as much to get all the information it needs.

8. Press ESCAPE and select “Yes” to save the changes to this new printer.

9. Re-power the PrintNet by turning the printer off and on to make the changes take effect.

xxxxxx

” where “

xxxxxx

”

Changing the PrintNet Name (NDS and Bindery setups)

xxxxxx

the format “M_ PrintNet’s Ethernet address found on the bottom of the device (e.g. “M_091C1A”). You must make sure that the print server object that you are using for your PSERVER setup has the same name as that stored on the PrintNet. If you need to rename the print server object in Netware Administrator, please delete the object, and re-create it with the new name. Netware administrator seems to have some problems with renaming objects.

NOTE: Changing the name will effect all of the protocols that are running

on the PrintNet.

” where “

xxxxxx

” equals the last six digits of the

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://

“ (e.g. “

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there’s no password by default.

3. Look under the “System Information” section and enter the new name into the “Name” field.

4. Click on the SUBMIT button when done and physically re-power the printer to make the new settings take effect.

PrintNetIPaddress

/adminConf.html”

http://192.75.11.9/adminConf.html”).

root

” for

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 “

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

3. At the prompt, enter:

store pserver name

4. Reset the unit to ensure the changes take effect.

:root>

name

root

” for

reset

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://

“ (e.g. “

NOTE: If prompted for a “User ID” and password first, type in “

the ID and press ENTER at the password prompt since there’s no password by default.

3. Look under the “Novell” section and go to the “Frame Type ” field to select the appropriate frametype.

PrintNetIPaddress

/networkConf.html”

http://192.75.11.9/networkConf.html”).

root

” for

100

4. Click on the SUBMIT button when done and physically re-power the printer to make the new settings take effect.

Manual (Telnet) Method

1. Telnet to the print server. This will bring up a login screen:

telnet

NOTE: If prompted for a “User ID” and password first, type in “

2. You should now see a prompt displayed that has the PrintNet’s IP address followed by a colon then root.

ipaddress

3. At the prompt, enter:

store pserver novell frametype [ethernet2 | 802.3 |802.2 |802.2snap | autosense]

4. Reset the unit to make the changes take effect.

reset

ipaddress

root

” for the ID and press ENTER at the password prompt since there’s no password by default.

:root>

Fujitsu 9045 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Trademark Acknow ledgements

1 Introduction

Overview

What is the PrintNet?

What Special Featur es are Availa ble?

Interfaces

10Base2 and 10Base-T

Figure 1. Status Indicator Lights (10Base2 and 10Base-T)

Table 1. LED Pattern Indications

Operating Modes

Power-on Self T est

Run and Auto Reset Modes

Table 2. Run Mode and Auto Reset Mode Indicator Descriptions

Dipswitches

Table 3. 10Base2 and 10Base-T Dipswitch Settings

10/100Base-T

Figure 2. Status Indicator Lights and Dipswitches (10/100Base-T)

Run and Auto Reset Modes

Table 4. Run Mode and Auto Reset Mode Indicator Descriptions

Network Indicator

Dipswitches

Table 5. 10/100Base-T Dipswitch Settings

Conventions Used In This Manual

Installation

Connecting to the Ne twork

Figure 3. Physical Setup

Configuration Tools

Configuration Using the Printer Control Panel

CAUTION

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.

5. Press the DOWN arrow key to access the “IP Address” parameter.

6. Press the DOWN arrow key to view the current IP Address.

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 select the portion of the IP Address to be changed.

9. Press the DOWN arrow key.

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. Press the UP arrow key and you will be returned to step 8.

CAUTION

IPAssign

Figure 4. IPAssign Sample Interface

HTML Forms

Figure 5. PrintNet HTML Structure

Printer Status Screen

Figure 6. WWW Printer Status Screen

Configur atio n A lter nat iv es

Telnet

Remote Shell

3 Windows Configuration

Overview

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 Environmen t Description

Figure 7. Windows Integration

Windows PrintNet Configuration

Mandatory

Optional

Configuration Using IPAssign

1. Insert the diskette labeled “IPAssign” into the floppy drive.

3. Double click on the IPAssign file to launch the install program.

4. When prompted to install, click on YES to load the InstallShield Wizard.

5. Answer the prompts throughout the wizard.

7. Find the new IPAssign program group and double click on the “IPAssign” icon to load the program.

Figure 8. IPAssign Main Screen

9. Once your PrintNet Ethernet Address appears in the list box, select it and click on ASSIGN.

18. Click in the field labeled “Subnet Mask” and fill in the PrintNet subnet mask.

19. Click on the SUBMIT button when done.

Figure 9. Network Configuration HTML Form

Configuration Using ARP

1. Log on to a Windows station with TCP/IP loaded and located on the same subnet as the PrintNet.

4. Check to see if the ARP entry was accepted.

3. Under the “Subnet Mask” heading, enter the PrintNet subnet mask.

Communicating Across Routers

Changing Workgrou p Names