rint Sewer

User's nual
Trademarks
Products in this manual are referred to by their trade names. In most, if not all
cases, these designations are claimed as trademarks or registered trademarks of
their respective companies.

Safety information
This manual contains the following safety information:
Where applicable, cautions and warnings are used throughout this manual to
draw your attention to precautions to be taken.

Copyright
OcC-Technologies B.V.Venlo, The Netherlands O 1998
All rights reserved. No part of this work may be reproduced, copied, adapted,
or transmitted in any form or by any means without written permission from
OcC.

Oc6-Technologies B.V.makes no representation or warranties with respect to

the contents hereof and spec~ficallydisclaims any mplied warranties of
merchantability or fitness for any particular purpose.
Further, Oc6-Technolog~esB.V reserves the right to revlse this publication and
to make changes from time to t m e in the content hereof without obligat~onto
notify any person of such revision or changes.

Code number 465221237

Edition D June 1998
Contents
Chapter 1
Introduction
Structure of the manual 10
Ethernet print server features 12
General 12
Novell features 12
TCPIIP features 13
AppleTalk features 13
NetBlOS features 13
Printer support 14
TCPIIP 14
Other 14
Overview of print server architecture 15
110 ports 15
Destinations 15
Models 16
Summary 17

Chapter 2
TCPiIP Unix configuration
Host software 20
Compiling host software 20
ezsetup and npconfig 21
Print server configuration 23
Configuration with ezsetup or npconfig 24
Manual configuration with ARP 25
Manual configuration with RARP 26
Manual configuration with BOOTP 27
Manuat configuration through the serial port 28
Restoring to factory defaults 29
Host configuration 30
Direct printing without the spooler 30
npwrite 31
rsh/rcmd/remsh 3 1
Printing via the spooler 32
npr.if interface script 32
Custom interface scripts 33
Modifying your script 33
Using npd and your own script 34
BSD UNIX 35

Contents
 Ipd remote printing 35
Setting up Ipd remote 35
BSD interface script printing 36
Setting up an interface script 37
System V UNIX 39
Setting up an interface script 40
npd pseudo-device interface 42
Starting npd 42
npd locks 43
Testing npd 44
Modifying a host to use npd 44
Stopping npd 45
Applications using npd 46
Sun Newsprint 46
Adobe Transcript 47
AIX 49
Other TCPLP print methods 5 1
NCSA 51
FTP's PCITCP 5 1
Direct socket printing 52
FTPdaemon 52

Chapter 3
Novell configuration
Host software 54
npsh.exe 54
Print server configuration 56
Host configuration 57
PSERVER bootup 57
RPRINTER bootup 57
PSERVER setup (Pre-NetWare 4) 58
RPRINTER setup (Pre-NetWare 4) 60
NetWare 4 options 63

Chapter 4
AppleTalk configuration
Print server configuration 68
Host configuration 69
Additional configuration options 70
AppleTalk zones 70
Changing print server name 70
Removing excess printers from the chooser 71

Ethernet Print Server User's Manual

 Disabling the AppleTalk module 7 1

Chapter 5
NETBJOS configuration
Basic setup sets 74
Setting up TCPJIP on Windows workstations 74
Windows NT version 3.5 (Net Use) 75
Windows NT version 3.5 [LPR Client) 75
Windows for workgroups (WfW) 76
Windows 95 and Windows NT4 76
Print server configuration 77
Host configuration 78
Windows NT version 3.5 78
Windows for workgroups (WfW) 80
Windows 95 and Windows NT4 81

Chapter 6
Internal architecture
Destinations 84
Models 85
Variables 86
Logpaths 87

Chapter 7
Command set
npsh overview 90
npsh prompt 90
User accounts and permission5 91
Redirecting output from commands 91
npsh basic commands 92
npsh command set 93
Command syntax 93
cancel 93
chr 93
debug 94
disable 94
enable 94
keycode 94
List Commands 95
list arp 95
list date 95

Contents
list dest 95
list diff 96
list ifc 96
list key 96
list logins 96
list logpath 96
list model 97
list pserver 97
list rprinter 97
list sysinfo 97
list tcpip 98
list test 98
list time 98
list user 98
list var 98
load 99
load default 99
Ip 99
lpstat 100
ping 100
reset 100
save 100
save default 101
Set Commands 101
set date 101
set dest 101
set logpath 102
set model 103
set rprinter 106
set sysinfo 106
set time 108
set user 108
set var 109
start 109
stop 110
Store Commands 111
store ifc 11 1
store pserver 112
store tcpip 114
supervisor 115
telnet 116
Chapter 8
Options
General options 1 19
Network security 1 19
Using different naming schemes 1 19
Setting up special job processing 1 19
Optimizing the print server's services 120
Capturing printer feedback 120
Controlling the frame types used 121
TCP/IP options 1 22
Restoring to factory defaults 122
Getting ready for complex networks 122
Remotely managing the print server 123
Maintaining network securlty 124
Using the terminal port 125
Novel1 options 126
Setting password security 126
Setting preferred file servers 126
Managing with SNMP 127
Custom MlBs and traps 127
Custom MIB variables 127
System variables 128
Product variables 128
Custom MIB traps 128
SNMP security 129
Adding an SNMP user 129
Setting the print server to send traps to an SNMP manager 129
Compiling and monitoring the custom MIB 130
FTP daemon 131
Print server FTP file system 13 1
Printing a file using FTP 132
Removing a print job using FTP 132
Monitoring a print queue using FTP 133
Configuring print server parameters using FTP 134
Restoring a configuration using FTP 135
Executing a configuration file using FTP 137
IP Routing 138

Chapter 9
Troubleshooting
TCPIIP problems 140
Communication related 140
Printing related 141

Contents
 Novel1 problems 143
Communication related 143
Printing related 144
AppleTalk problems 147
NetBIOS problems 148

Appendix A
Specifications
Variable definitions 150
Software specifications 151

Appendix B
Glossary 153

Appendix C
Installation
Installing the ethernet interface 162
Connecting the printer to your network 168
Switching the printer on 168
Unix print server installation 169
Novel1 print server installation 170
PSERVER setup 170
RPRINTER setup 170
Basic Windows configuration 172
Basic AppleTalk configuration I73

Appendix D
Planning your print setup
Configuration considerations 176

Appendix E
Miscellaneous
Notation conventions 180
Reader's comment sheet 181

Appendix F
Oce Offices
Your Oct Contacts 184

8 Ethernet Print Server User's Manual

 Ethernet Print Server
User's Manual

The purpose of this chapter is to get you acquainted with the Oce' Ethernet
print server. It contains an overview of the print server's features and
architecture.
Using the Oce' Ethernet interface print server, you can locate your printers
or plotters and other peripherals anywhere on the LAN rather than
attaching them directly to a host system.

Who should use this manual

A system administrator or someone with a good understanding of the
protocol involved should perform the installation and conjiguration
procedures in this manual.
 This manual is divided into 14 chapters, whch are summarized below. New
users are strongly advised to read Chapter 1.

Chapter 1 Introduction Organization and conventions used in this

manual. Description of the features and architecture of the
Ocd Ethernet print server.

Chapter 2 Unix Configuration ( P) Overview of TCP/IP host

software and in-depth on OcC Ethernet interface
configuration and various TCP/IP host setups.

Chapter 3 Configuring for NOVELL Full introduction to Novel1 host

software and to the various print configurations available with
all versions of NetWare.
Chapter 4 Configuring for AppleTalk Description of a full AppleTalk
setup.
Chapter 5 Configuring for NET IOS Explanation of a print setup in a
Windows NT, Windows 95 and Windows for Workgroups
(WfW) environment.
Chapter 6 Internal architecture Explanation of the Ocd Ethernet print
server's internal operating architecture and logic.
Chapter 7 Using the command set Full reference section based on the
Oct Ethernet interface's command set.
Chapter 8 Additional options Introduction to some of the print
enhancements provided by the OcC Ethernet print server.

Chapter 9 Troubleshooting Helpful hints and steps to consider when

you run into problems in any setup.
Appendix A Specifications Information on hardware specifications,
variable definitions and software specifications.

Appendix B Glossary Definitions of words, abbreviations, and acrorryms

used in this manual.

1
1
10 Ethernet Print Server User's Manual

i
Appendix C Installation How to install the ethemet board in your plotter
and a description of the OcC Ethemet interface's network
connectors and YO ports, along with steps to connect the print
server to the network.

Appendix D Planning your print setup Information on setting up your

printing environment.

Appendix E Miscellaneous covers Notation conventions and a Readers

comment sheet.

Appendix F Oc6 offices gives the official list of OcC offices, Worldwide.

Index A general quick reference section.

Introduction
General
a High-speed AUI port,
Serial port for the console,
a multi-level configuration security through passwords and permission levels,
SNMP support through MIB 11, custom MIBs, and custom traps to aid in
network management,
a multiple printer destinations for printing flexibility,
a the choice to disable selected print server services,
a extra printing functions such as carriage return insertion to remove some of
the processing burden from the host,
a banner and trailer page generation,
a autosensing of job/file format for automatic switching of the printer's
emulation mode (Automatic Language Sensing),
a header and trailer strings to select printer options,
a logging to keep track of job, user, page count, checksum, and plotter error
information,
a TCP/IP syslog and SMTP (email) support for additional logging
functionality,
backchanneling for plotters to send various messages about: print-job status,
paper out, paper jam, busy, etc. back to the host (Does not apply to all
workstations).
queuing of all print jobs on LANs or WANs, while supporting up to two ports
simultaneously.

Novell features
a support for all versions of NetWare, including NetWare 4,
simultaneous support of multiple Novell frame types,
a encrypted password support,
a queueing on up to 32 queues over 16 file servers,
a ability to add a preferred Novell file server list,
a automatic frame type sensing of all Novell frame types.

12 Ethernet Print Sewer User's Manual

TCP/IP features
R further configuration security through TCP access lists,
scrambled print job data to protect the job as it passes over the network,
ability to telnet and ping to another host on the network from the print server,
R up to 256 simultaneous TCP connections,

R GOSIP RFC- 1042 support,

IP Routing support for communications over separate networks,

R FTP daemon support for printing, unit monitoring, and configuration,

IP packet fragmentation support.

AppleTalk features
quick printer setup through the Chooser,
ability to disable certain print destinations on the print server so they don't
all appear in the Chooser,
R configurable AppleTalk zones.

Attention: To print from a Macintosh via EtherTalk, the Postscript option

must be installed in the printer and the printer data format must be set to
Postscript. This can be done from the printer% control panel or from your
workstation, via a remote configuration header.

NetBIOS features
R NetBIOS over TCPIIP support for Windows NT, Windows 95 and Windows
for Workgroups (WfW),
R simple printer setup.

Introduction
 The print server is compatible with PC's, UNIX systems, Macintosh
computers, minis, and mainframes as long as at least one of the following is
present:

an LPR client to interact with our Line Printer Daemon on the unit,
an RSH client (i.e. rsh, remsh, rcmd) to interact with our RSH Daemon,
the ability to print directly to a TCP port number on our unit; we have a TCP
port number mapped to each I/0 port on the unit by default (i.e. pltl is 4000),

Other
NetWare support,
a AppleTalk over EtherTalk support,
NetBIOS over TCPIIP support,

14 Ethernet Print Server User's Manual

 verview of print server arc
This section will provide an overview of how the print server works. To better
understand how the print server works, it is important to understand VO ports,
destinations and models.

VO ports
The print server has two V 0 ports. Each V 0 port has an internal queuing
mechanism that automatically queues print jobs on a first-come, first-serve
basis even if the print jobs come from different network environments (e.g.
Novell and TCPRP).

Destinations
When you send a print job to the print server, the print job doesn't go directly
to an V 0 port but first goes to a destination. A destination can be thought of as
logical place on the print server to send print jobs. Each destination has an V O
port and a model (see below) associated with it. The purpose of destinations is
to allow you to configure a two virtual ports with different print setups.

There are eight pre-defined destinations on the print server and each of them,
by default, is associated to one of the four UO ports on the unit (two
destinations per VO port). By default, the destinations have names such as
dlplt 1, d2plt2, d3pltl, d4plt2,. . . d8plt2, etc. If you like, any of these
destination names can be changed to be something more meaningful.

Note: Although the system hus four ports (at installation time you will see
four), only the first two ports ure available.

Introduction
Models
Each destination on the unit also has a model associated with it. The eight
models (one per destination) can be thought of as a series of mini-filter that can
do special processing to the print job data. For example, a model can be set up
to do such things as ASCII to Postscript conversion (a2ps) or carriage return
insertion (onlcr).

By default, all eight models on the print server are initially set up to be raw.
When raw, they simply pass data through to the UO port untouched. By default,
the models are named 01 through to 0 8 but can be changed to be something
more meaningful.

Models only need to be reconfigured when you want to do special processing

to all the print jobs that are sent to a particular destination.

16 Ethernet Print Server User's Manual

Summary
When you are doing a print setup, you must direct print jobs to a particular
destination which is mapped to an UO port to which the printer(s) is attached.
The destination's associated model is then used for any extra processing of the
data, if required. Each VO port has an internal queuing mechanism that
automatically queues print jobs on a first-come, first-serve basis.

For more information on I10 ports, destinations, and models, please see
chapter 6, 'Internal architecture' on page 83.
Print Server

PLT1
* VO Port

This example follows a print job sent to destination dlpltl.

dlpltl is associated with model m l and the I10 port pltl.
When the data is passed through the associated model, any job processing specified
by the model is performed on the data.
If no additional processing is specified, the data is passed through to the I10 port
untouched.

[I] Print server operating logic

Introduction
Ethernet Print Sewer User's Manual
 Ethernet Print Server
User's Manual

If you are conjiguring the print server in a TCP/IP

environment, this chapter will help you with all aspects of
the setup process. The provided host software is introduced
and then steps are given for conjiguring the print server for
communications over the network and for printing. Since
TCPIIP encompasses a wide variety of system types, the
common ones are covered in detail to help you get printing
in a TCP/IP environment.
Host soft
The TCPIIP software provided includes two setup programs, source code,
interface files, and various printing-related programs such as:

a2ps for ASCII to Postscript conversion,

B onlcr for carriage return insertion,
banner for banner page generation,
a chr for echoing ASCII characters and strings to standard output,
m npscramble for print job scrambling,
B npd for bi-directional communications when printing,
a npwrite for direct socket printing.

The chr binary must be used with the interface scripts for printing. The extra
processing binaries (aZps, onlcr, banner) can be configured for the host to
perform or they can each be set on the print server alleviating the host of these
extra tasks.

To be utilized on a host, they must be used in conjunction with an interface file.

Otherwise, please see 'Command set' on page 89 for information on the
commands necessary to set these features on the print server. By setting these
features, the compilation of chr may be the only one required.

Compiling host software

Some compilation may be needed before adding print setups to your host
unless you have SunOS 4. I .x,Solaris 2.x,or SCO Unix. Pre-compiled binaries
are provided for these. npconfig can be used to do the compilation or you can
try and compile each program independently.

For the npconfig method, please:

1 Select Detailed Configuration Options . . . from the npconfig Main Menu.

2 Select Manage Host Software . . . from the Options Sub-Menu.
3 Select Compile Host Software and answer the prompts until compiled.

For more information on all of this provided host software, please see the next
sub-sections.

20 Ethernet Print Server User's Manual

ezsetup and npconfig
ezsetup and npconfig are the two installation programs provided; one is for a
very quick, simple setup and the latter is for a more detailed configuration or
for maintaining and troubleshooting the print server. Both programs help you
configure your print server and direct print jobs to it.

ezsetup provides two choices only; these are the same as the first two choices
of npcontig's Main Menu. Within minutes, you will have configured the print
server so it can be recognized on the network and your host will be able to send
print jobs successfully to it. Refer to Table 1, below.

If you want to spend more time manipulating the extra capabilities of the print
server and your host's configuration, use npconfig. It can be used to configure
a print destination on your host and it can also be used as a print server
management utility allowing you ro monitor, change and troubleshoot the unit.

Both setup scripts create individual log files, /tmp/ezsetup.log and

/tmp/npconfig.log, which simultaneously log a copy of a11 of the commands
executed as you run through each of these scripts.

For an explanation of the menus refer to Tables I and 2.

Option Description
Configure New Unit Add a print server to your network. This option provides
for: IP name, IP address, hardware address, netmask, and
for root and guest passwords. (ezsetup as well)
Configure Host Setup Configure a print destination on the host including
communication mechanism and processing options.
(ezsetup as well)
-
Detailed Configuration Options . . See %ble 2: Derailed configuration option sub-menu.
Check Current print server Status Display current status of a print server and associated U 0

Cancel a Print Job in the print server Display current status of a print server, current print jobs

Table 1: npconfiglezsetup Main menu

TCPIIP Unix configuration

 Option Description
7

Select print server Select the print server you want to configure.
-
Configure print server's Destinations Configure the destination settings: name, 110 port,
model, logpath, state, alternate destination, and
service(s).
Configure print server's Models . . . Configure model settings: name, type, banner page,
carriage return insertion (onlcr), tab expansion (xtab),
descrambling,ASCII to Postscript conversion (azps),
and header and trailer strings.
Configure print server's Logpaths . . . Configure logpath settings: name, type, and port.
Configure print server's Users. Add and remove users. Change user passwords and user
types.
Configure print server's Novell Configure and list the Novell settings: name, frame type,
Options ... and PSERVER password. List PSERVER and
RPRINTER configuration.
Configure print server's Network Configure IP address, netmask, routing entries, frame
Options ... type, and RARP and BOOTP settings. Restore unit to
default settings. List all network-related settings.
Manage print server's System Display and modify system information of a print server:
Information . . . name, contact name, location string, log details,
descramble key, license key, and module(s).
- -- -

Configure print server's Permanent For print server settings, query current status and store
Settings. . . changes tolfrom EEPROM and factory defaults.
Debug print server. . . Use debug commands. Begin and start 110 port tests.
Manage Host Software. . Install manual pages, compile source code, and install
binaries and scripts provided on the host software
media.
Remote Host Security . . . Specify TCP hostslnetworks that can communicate with
the print server.
Table 2: npconfig Detailed configuration options submenu

22 Ethernet Print Sewer User's Manual

Print server configuration
When the print server is first installed on aTCPnP network, you are unable to
communicate with it since its network parameters are not initialized. During
configuration, the following parameters are initialized and saved in EEPROM:

IP address (mandatory),
E netmask or sub-netmask(mandatory),
root user password (recommended for security),
guest user password (recommended for security).

Initializing these parameters permits configuration of all remaining settings

through any of these five ways:

1 computer-aided configuration with ezsetup or npconfig,

2 manual configuration with a terminal connected to the serial port,
3 manual configuration through the network with RAW,
4 manual configuration through the network with B O W ,
5 manual configuration through the network with ARP.

At this point, you can then configure a host for printing by continuing with ,
'Host configuration' on page 30. This will complete your entire print setup
unless you want to enhance it.

If you want to continue with any of the following procedures, please find them
as indicated in other sections of this manual:

Add to or change configuration of your print server. Please see 'Command

set' on page 89.
Utilize more advanced features of the print server. Please see 'Options' on
page 117.

TCPnP Unix configuration

Configuration with ezsetup or npconfig
Note: Ifyou choose computer-aided conjguration, you must log on to your
system as root or superuser and use rhe host sofrware diskette supplied with
your Ethernet print sewex If the software is not provided, contact Ocb

To configure the print server with the aid of a script, you must:

1 Insert the diskette into the drive.

2 Login as root user.
3 cd to a directory with at least three megabytes of free space.
4 Transfer the compressed tar file from the diskette onto the host.
Type: tar xvf /dev/devicename
devicename is usually fdO for a diskette.
Note: Thejlename may change. See the READ MEjle on the diskette for more
information.
5 Uncompress this file. Enter: uncompress npdist.tar. 1 .Z
6 Untar this file. Enter: tar xvf npdist.tar. 1

A list of files displays and scrolls up on the screen as tar executes and several
files and sub-directories are created.

7 Assign an IP address and IP name to the print server in your host table
(/etc/hosts, hosts nis map, or DNS name tables).
8 Run ezsetup or npconfig. Enter: ./ezsetup or ./npconfig
Note: I f running the host software on an HP/UX system, you need to explicitly
set the Korn shell by adding "ksh " before "./ezsetup" or "./npconjg ".

9 Enter the number for Configure New Unit from the Main Menu.
10 Follow the prompts.
For more information, please see 'ezsetup and npconfig' on page 21.

24 Ethernet Print Sewer User's Manual

Manual configuration with ARP
To manually configure the print server using the network, go to a host terminal
and do the following:

Log on to your system as root user.

Assign an IP address and IP name to the print server in your host table
(/etc/hosts, hosts nis map, or DNS name tables).
Find the Ethernet address for the print server on a sticker on the board. It must
be entered as part of this procedure.
Use the arp command to add an entry in the host's arp able. The most common
syntax for this command: arp -s ipname ethernetaddress
where ipname is the print server's IP name or IP address and ethernet-address
is that of the print server. Refer to the note on page 161.

Note: Ifthis syntax doesn't apply, look in your host's reference manual to find
the proper syntax for the arp command.

telnet to the print server. This will bring up a login screen.

telnet ipname
Log into the print server as root.
Note: To reduce errors, you are advised to use a workstation on the same
network as the print servet:
At the password prompt, press <Enten. No password is required at this point
as the print server is still unconfigured.

The following WARNING message is normal at this point, so you can ignore
it: STORED AND CURRENT VALUES DIFFER

You should now see a prompt displayed that has the print server IP address
followed by a colon, then root.
ipaddress:root>
Store the new IP address and netmask in EEPROM so that the print server can
remember its configuration after reboots.
Enter: store tcpip ifnum addr ipaddress
store tcpip ifnum mask netmask

Note: ifnum is the index to a particular Network Inte$ace, ifnum will

always be I for the print server since there is only one network inte$ace,
Ethernet.
Configure the default gateway setup.
Enter: store tcpip route add default gatewayipaddress

TCPllP Unix configuration

 10 [Optional, but recommended] Configure root and guest user passwords with
the following commands.
set user passwd root newrootpasswd
set user passwd guest newguestpasswd
11 Save these configurations to EEPROM. Enter: save
12 Verify the IP address and netmask. Enter: list stored tcpip

These are now stored in EEPROM.

13 Logout of theTelnet session with quit. Then reboot the printer by powering the
unit off, then on.
14 Test theequipment and configuration after installation is complete. Enter at the
shell prompt on your UNIX machine: ping ipname. The system is working
correctly if the printer responds. For example: "Host is alive" or similar
message.

Manual configuration with RARP

The R A W daemon provides a mechanism for dynamic IP address assignment.
When a RAW-configured TCPIIP host boots, it broadcasts a RARP request
for an IP address. Your network must have this daemon running on some host.
If you do not know whether your network has one, please ask your system
administrator or configure the print server with one of the other methods in this
section.

To configure the print server with RARP, you need to:

1 Make an entry in the Ietclethers file for the new print server.
Example: 00:20:84:1:30:9 spike

This is the entry for the print server named spike which has this Ethernet
address.

2 Start the RARP daemon if it isn't running. Send a HUPsignal to it with the kill
command: kill -NUP pid
3 Reboot the printer. Wait another ten to twenty seconds to allow the RARP
process to complete.
4 Test the new IP address by trying a ping with the new IP name:
Type: ping ipname

5 [Optional, but recommended] At this point, set up the user passwords. Please
see 'set user' on page 108.

26 Ethernet Print Sewer User's Manual

 If no response is given by the print server, the RARP process probably failed.
Switch the printer OFFION to reboot the print server and try one of the other
methods mentioned in this section.

Manual configuration with BOOTP

BOOTP is a protocol for configuring the print server as it boots. During the
boot sequence, the print server can broadcast a BOOTP request and if a
BOOTP server is running on the network configured to respond to the
requesting device, it will provide the print server with its IP address, netmask,
default router, and a time server from which to query the current time (GMT)
and the timezone in which the print server is located.

By default, the print server will broadcast a BOOTP request when it boots. The
following command can be used to control this request:

Type: store lcpip ifnum opts [[-Irarp] [[-Ibootp]

On the BOOTP server, there must be an entry in /etc/bootptab similar to this: :

0-xxx:\
:sm=netmask:\
:hd=:usr:boot:\
:bf=null:\
gw=default router:\
:ht=ethernet:\
:ha=network address:\ (e.g. 0080720000DC)
:ip=ipaddress:\
:ts=time server:\
:to=timezone: in seconds from GMT)

TCPhP Unix configuration

 Manual configuration through the serial port
A terminal, PC, or laptop can be connected to the Ethernet print server's serial
port for configuration purposes. A straight-through serial cable is normally
needed unless a PC is attached; in this case, a null modem cable must be used.

To configure the print server through the serial port, you need to:

1 Configure your terminal settings according to the following specifications:

Baud rate: 9600
Data bits: 8
Stop bits: 1
Parity: NONE
Receive handshake: XONIXOFF
Transmit handshake: XONIXOFF

2 Turn on the printer. Wait until the printer is ready and then press the <Bre*
key on your terminal once.

Note: lfyou see garbage characters on the screen, check the baud rate and
parity settings of the terminal. If you aren't getting anything, it may be your
cable.

3 Press <Enter> for the local host (i.e. the print server) when the prompt appears
asking for an Internet address to login to.
4 Login as root when asked for a login name.
5 Press <Enter> at the password prompt. No password is required at this point,
as the print server is still unconfigured.
6 Store the new IP address and netmask in EEPROM so that the print server can
remember its configuration after reboot.
Enter: store tcpip ifnum addr ipaddress
store tcpip ifnum mask netmask

Note: ifnum is the index to a particular Network Inte$ace. ifrium will always
be I for the print sewer since there is onlj~one network interface, Ethernef.

7 [Optional, but recommended] Configure root and guest user passwords with
the following commands:
set user passwd root newrootpasswd
set user passwd guest newguestpasswd

8'
i 28 Ethernet Print Sewer User's Manual

I
 8 Save these configurations to EEPROM. Enter: save
9 Verify the IP address and netmask. Enter: list stored tcpip

These are now stored in EEPROM.

10 After configuration, turn the printer off, then on. This reboots the print server
and automatically logs you out of the terminal session.
11 Test the equipment and configuration after installation is complete.
Enter at the shell prompt on your UNIX machine: ping ipname. The system is
working correctly if the printer responds. For example: "Host is alive" or
similar message.

Restoring to factory defaults

If at any time you'd like to restore the print server's network settings to their
original state, you can do so with an npsh command.

Please see 'Restoring to factory defaults' on page 122 for more details on this
process.

TCPnP Unix configuration

 When setting up a print destination on a Unix host, you have the option to
utilize a computer-aided script such as ezsetup or npconfig or to do all of the
appropriate steps manually.

If you decide to use one of the provided installation scripts, select Configure
Host Setup from the Main Menu of either program to configure a print setup
on your host. It will step you through some questions and then perform all of
the necessary setup commands for you. Please see 'ezsetup and npconfig' on
page 21 for more information on these scripts.

The rest of this section introduces you to different printing methods, with the
spooler and without, and discusses each of the manual steps for these
environments:

ua BSD
a System V
B Sun Newsprint and Adobe Transcript
E AIX
E PC.

Direct printing without the spooler

Before configuring the spooling system, test that basic communications are
working with the print server. Perform tests by sending print jobs directly to
the print server and bypassing the spooler altogether. You can send print jobs
directly to the print server with either npwrite or rsh/rcmd/remsh.

The rsh/rcmd/remsh program provides the same functions as the npwrite

program except that the rsh/rcmd/remsh program exits with an error code when
the network connection is down. npwrite continually tries until the job is
completed. Remember this behavior when you are manually modifying your
interface script because some spooler systems simply send a message about the
error but the job gets flushed. The npr.if interface script gives you examples of
how this behavior should be handled.

30 Ethernet Print Server User's Manual

npwrite
The data transfer program npwrite is provided with the host software shipped
with the print server. It sends data to the print server over a TCP connection.
Data is read from a file or, if no file is specified, from standard input. The
format of the data is not altered by this program so make sure it is in
printer-ready format.

The syntax for npwrite is: npwrite ipname portname Vilenames]

Where:
ipname print server IP name or IP address.
portnanze I/0 port on the print server (i.e. pltl, plt2).
$filenames [optional]. Filename(s) to be printed. If no filename is specified,
data is read from standard input.

Example: npwrite 192.75.11.32 pltl testfile.txt

npwrite spike pltl testfile.txt
cat testfile.txt I npwrite 192.75.11.32 pit1

where spike and 192.75.1 1.32 are the print server's IP name and address.

If the npwrite binary is not available for your UNIX machine, use
rsMcmd/remsh instead.

The rsh/rcmd/remsh programs are remote command execution clients that talk
to the rshd server in the print server. rsh, rcmd, and remsh are actually the same
programs but have different names on different UNIX systems; some systems
may even have another name for remote command.
Enter man rshd to display the online manual pages for information on the
remote shell server for your version of UNIX.

The print server provides Ip, Ipstat, and cancel programs for print services
through the rshd server. The Ip command reads data from standard input and
sends it to the specified port as follows:

on SCO UNIX, either of the following:

rcmd spike Ip -d dlpltl < testfile.txt
cat testfile.txt I rcmd spike lp -d dlpltl

TCPllP Unix configuration

 on Sun UNIX, either of the following:
rsh spike Ip -d dlpltl < testfile.txt
cat testfile.txt I rsh spike Ip -d dlipltl

where spike is the print server's IP name and dlpltl is the destination.

j Printing via the spooler

i
I
Once you know your communications are correct and you can successfully
print directly to the print server, you can integrate the spooler.

Interface scripts play important roles in BSD spooling environments and

especially with System V print spoolers. BSD systems also provide a remote
printing method that utilizes the spooler but needs no script or host software at
all.

The following sections elaborate on different spooling environments and

provide the manual steps for full host configuration in various environments.
ezsetup or npconfig, in most cases, can be used instead to simplify the setup
process. Please see 'ezsetup and npconfig' on page 21 for further details.

\
1 npr.if interface script
I
The npr.if interface script provided works in most environments, but it can be
replaced by a custom interface script if you have other requirements. It is
usually a UNIX script which reads parameters from the command line,
processes the job according to the parameters, and sends it to the destination.

Two interface scripts, nprbsd.if and nprsysv.if, are shipped in raw state. These
interface scripts can be named anything you would like. Load the appropriate
one for your system spooler type and use it in this state if the print server can
do sufficient processing. The print server itself contains enough processmg
options, when they are turned on, to handle most processing needs without the
need for host software. Some of these options include ASCII to PostScript
conversion (a2ps) and camage return insertion (onlcr). Therefore, host
software may be unnecessary and you can turn off all processing options on the
host. Please see 'Host software' on page 20 to find out more about these
options.

Ethernet Print Sewer User's Manual

 If you require high-speed printing, use one of the interface scripts with host
processing turned on. This removes processing load from the print server and
increases printing throughput.

Both ezsetup and npconfig utilize the appropriate interface script by renaming
it to nprprintername.if, where printername is the name of the printer on the
host. To install one of these scripts manually, please refer to the section that
applies to your host: 'BSD UNIX' on page 35 or 'System V UNIX' on
page 39.

Custom interface scripts

If an interface script is to be used for your print setup, you have three choices:

1 Use npr.if provided in the host software.

2 Use a pre-defined script for your particular printer.
3 Use a script you have created yourself.

The npr.if method is explained throughout this section. However, if you have a ..
pre-defined printer script or a script of your own, there are certain
modifications you must make in order for it to work with the print server.

The important part of an interface script is where it sends the print job. With
the print server, the data must be captured and sent over the network for
printing, since your printer is no longer locally attached. There are two possible .
ways to make this happen with your current script:

1 Encapsulate your script's code with brackets ( ) and after the closing bracket,
add a command to send the data to the print server for printing.
2 Use npd as the print method.

Both of these methods are explained on the next page.

- -

Modifying your script

If you choose to simply edit the script, you need to understand how an interface
file works. The structure of any standard interface file should be as follows:
process options
(
generate printer setup characters

TCPnP Unix configuration

 generate banner page data for each file
translate data to printer format
) I communication program

where communication program is the command executing rsh/rcmd/remsh or

npwrite so the print job is redirected over the network to the print server.

Example: (
FILE=$6
#the spool file is found in the sixth parameter on System V
cat $FILE I onlcr
#fiker the job
) I rcmd spike Ip -d dlpltl

where spike is the name of the print server and the print jobs are being sent to
its destination d3plt3 by remotely executing the print server's Ip print
command.

Please see npwrite and rsh/rcmd/remsh on page 3 1, and Ip in page 99 for

more details on each command's syntax.

Note: Even ifyou have a very simnplistic script, it is important that you enclose
your scrip with brackets and then add in a communication program at the end.

Using npd and your own script

If npd is the print method you would like to use with your interface script, you
need to start the npd daemon on your host and then incorporate it into your
print setup. Please see npd Pseudo-device Interface in section to find out more
about npd and how to get it started.

Once you have this daemon running, you can go ahead and work it into your
printer configuration. For BSD systems, this requires an lp= field in your
printcap entry along with the standard if= field for the name of your interface
script. The lp= field is filled in with the name of the npd devicefile used in npd's
startup command. If you have a System V setup, the -v option in the lpadmin
command will equal the npd devicefile.

34 Ethernet Print Server User's Manual

 BSD systems allow you to print remotely or to print with an interface file for a
locally attached printer. This is configured within the Ietclprintcap database.

Ipd remote printing

The Ipd daemon spools files locally, then sends them to an print server acting
as a remote printer. As interface scripts cannot be used with this spooling
method, processing must be done by the print server.

This method should be used in the following conditions:

your UNIX host supports BSD 4.3 LPD protocol,
no bi-directional communication is required between the printer and printing
application,
you want to avoid using special host software.

The control file usually contains valid information about originating user and ,,

host. The control file contents are only used to gather log information on the
printed jobs. However, since the control file may not arrive before the data file
in the current LPD standards, fully detailed banner pages cannot be guaranteed
(Your printer must be able to print ASCII text, to have banner support).

Setting up lpd remote

To manually add a print server printer as a remote printer entry on your BSD
UNIX host, you need to add an entry to the letclprintcap file and then create its
associated files and directories. The following is an example of what the
printcap entry should look like followed by a description of the commands
necessary to create these entries:
Example: pslPostScript printer on spike's pltl port:\
:lp=:\
:rp=dlpltl :\
:rm=spike:\
:sd=/usr/spooVlpd/spike/ps:\
:If=lusrlspooVlpd/spikelps/log:\
:af=/usrlspooVlpd/spike/pslacct:

TCPnP Unix configuration

 where ps is the printer name sendingjobs to the destination dlpltl on the print
server named spike.

To create the necessary entries for this example, these commands are needed:
cd /usr/spooMpd
mkdir spike
mkdir spikelps
touch spikeIpsAog spike/ps/acct
chown -Rdaemon.daemon spike
chmod -R g+rwX,o+rX spike

Once this is done, you can then start this printer.

Ipc start ps

To send a print job, use this syntax:

rintername filename

SD interface script printing

If you decide not to go with a remote printer setup, you can use an interface file
instead. This interface script is specified in Ietclprintcap with the if= entry
instead of the rm= and rp= entries. The script is called by the Ipd daemon with
the following syntax:

nprbsd.if -wwidth -1length -iindent -nlogin -hhost acct-file

where:

nprbsd.if Name of the interface script.

width Width of page in characters.
length Length of page in lines.
indent Number of characters of indent from left margin.
login Login name of person originating the print request.
host Name of host where the print job originates.
acct-file File where accounting data is stored.

36 Ethernet Print Sewer User's Manual

Setting up an interface script
To manually set up your host with an interface file, you need to add an entry to
the /etc/printcap file and then create and edit its associated files and directories.

Here is an example of what the printcap entry should look like followed by a
description of the commands necessary to create these entries:

where hp is the printer name sending jobs to the print server named spike
through the interface file npr.if.

To create these entries, please do the following:

1 Create the printer's spooling directory and associated files.

cd /usr/spooVIpd
mkdir spike
mkdir spike/plt2
touch spikelplt2nog spike/plt2/acct
chown -R daemon.daemon spike
chmod -R g+rwX,o+rXspike
2 Copy the nprbsd.if file from the host software medium to the spooling
directory. Copy the file as npr.if or name it something meaningful.
cp nprbsd.if /usr/spooVlpd/spike/plt2/npcif
cd /usr/spooVlpd/spike/plt2
chown daemon.daemon n p ~ i f
chmod g+rwX,o+rX npr.if
3 Edit the npr.if variables to suit your system environment. Look for the
comment section beginning with "EDIT THESEVARIABLES' and at the end
of this large comment block, you will find these:

Note: When defining these variables, remember that each is case sensitive.
Please define them as seen in these descriptions. In addition, a further
description of these variables is included in the large comment block before
them.

TCPfiP Unix configuration

 NPDIR-PATN(mandatory) Define the directory location of chr, banner, onlcr,
a2ps, and npscramble binaries. Usually /usr/local/bin.

These binaries must be copied over from the host software medium. Please see
Host Software, section 3.2, for more details.

COMM-PROG(mandatory) Specify a communication program to transfer

data to the print server (is. npwrite, rsh). If the program is npwrite, define the
UNIT-PORT variable. Otherwise, define the LP-DEST variable.

PRINTER-TYPE(mandatory) Specify printer type (i.e. raw, ascii, ps, oce.

(mandatory) Define the print server IP name.

UNIT-PORT(conditiona1) Specify the print server port name (i.e. pltl, plt2).
Use only when COMM-PROG is defined as npwrite.

LP-DEST (conditional) Specify print server destination name. Use only when
COMM-PROG is defined as rsh.

Example: #END_MLARK-I
NPDIR-PATH=/usrnocal/bin
COMM-PROG=rsh
UNIT-NAME=spike
LP-DEST=dlpltl
PRINTER-TYPE=raw, ascii, o r oce
BANNERPAGE=l
#STARTMARK-1
Note: Additional variables can also be dejned within this variable section as
indicated by BANNERPAGE=/. Some other options are ASCII to PostScript
conversion, carriage return insertion, and scrambling. By setting a particular
variable to a I , this option is then turned on and a 0 turns it off. These too are
described further in the beginning of n p ~ i f .

4 Create the lp= device that is used as a locking mechanism for contending print
jobs.
touch /dev/spike.pItl
chmod go+rw /dev/spike.pltl
5 Start the print spooler.
lpc start oce
6 Try printing with the following syntax:
lpr &'printername filename

38 Ethernet Print Sewer User's Manual

ystem V UNIX
Printing in a System V environment requires the use of an interface file. It also
consists of:

the Ip printer interface program,

the lpsched printing scheduler,
a set of programs that act as interfaces between scheduler and printing
device.

The scheduler copies the file into a spooling directory and calls the interface
program when the job is ready to go to the print server. It processes the job
according to the script's settings and then sends it over to the print server for
printing.

The interface script is usually kept in /usr/spoo~p/adminsflp/interfacesand

carries the same name as the associated printer. It is copied there from the
original interface file in /usr/spool/lp/model when the lpadmin command is
executed.

The interface script is called with the following syntax:

ps203 reqid username title copies options filel ...

where:

ps203 Name of the interface script which is also the printer name on the
host.

reqid Print job identification.

username ID of the user requesting the job.

title Title of the print job if desired.

copies Number of copies of each file to be printed.

options Additional switches for extra job processing options.

file1 Spool file.

... Indicates additional spool files.

TCP/IP Unix configuration

Setting up an interface script
The following steps are the manual instructions for setting up your host with
npr.if:

The example commands provided represent a print setup involving a printer

named ocz, an print server named spike, and a printer attached to the print
sewer's pltl port.

1 Copy the nprsysv.if file from the host software medium to the model directory.
Copy the file as npcif or name it something meaningful.
ep nprsysv.if /usr/spooYlp/modeVnpcif
2 Edit the npr.if variables to match your system requirements.
Note: When dejning these variuhks, remember that each is case sensitive.
Please define them as seen in these descriptions. In addition, a further
description of these variables is included in the large comment block before
them

Look for the comment section beginning with "EDIT THESE VARIABLES"
and at the end of this large comment block, you will find these:
(mandatory) Define the directory location of chr,
banner, onlcr, a2ps, and npscramble binaries. Usually /usr/local/bin.

These binaries must be copied from the host software medium. Please see Host
Software, section 3.2, for more details.

COMNI_PROG(mandatory) Specify a communication program to transfer

data to the print server (i.e. npwrite, rsh, rcmd, remsh). If the program is
npwrite, define the UNIT-PORT variable. Otherwise define the LP-DEST
variable.

PRINTER-TYPE(mandatory) Specify printer type (i.e. raw, ascii, ps, hp,

pcl-ps, gen7170).

UNIT-NAME(mandatory) Define the print server IP name.

UNIT-PORT(conditiona1) Specify the print server port name (i.e. pltl, plt2).
Use only when COMM-PROG is defined as npwrite.

LP-DEST (conditional) Specify print server destination name.

Use only when COMM-PROG is defined as rsh, rcmd, or remsh.

40 Ethernet Print Server User's Manual

 Example: #END-MARK-1
NPDIR-PATH=/usr/locaVbin
COMM-PROG=rcmd
UNIT-NAME=spike
LP-DEST=dl pltl
PRINTER-TY PE=ps
BANNERPAGE=I
#START-MARK-1
Ipc start oce
Note: Additional variables can also be dejned within this variable section as
indicated by BANNERPAGE= I. Some other options are ASCII to Postscript
conversion, carriage return insertion, and scrambling. By setting a particular
variable to a I , this option is then turned on and a 0 turns it 08These too are
describedfurther in the beginning of npr$

3 Create the dummy output device file used as a locking mechanism between
contending print jobs.
touch /dev/spike.pltl
chmod go+rw /dev/spike.pltl
4 Install a new printer specifying printer name, interface script name, and
dummy device created in Step 3.
/usr/lib/lpadmin -poce -mnpcif -v/dev/spike.pltl
5 Start the scheduler.
lpsched
6 Enable the printer and allow it to accept requests.
enable oce
accept oce
7 Try printing a file with the following syntax:
lp -dprintername filename

TCPAP Unix configuration

npd pseudo-device interface
The npd pseudo-tty daemon is used when bi-directional communications is
required between the printer and printing application, and when changes to the
printer's interface script are undesirable.

Some applications like Sun Newsprint and Adobe Transcript work best with
a bi-directional communications channel to the printer because they can
provide more details on the printer status. For example, Postscript printers can
send error messages back to the application as they occur. npd is used in this
case making use of the TCP protocol and pseudo-tty device drivers.

processes the job

and passes it to the
printer device

\
:his device and sends
m y print jobs to the
x-int server

[2] npd Overview

Starting npd
Starting the npd daemon is all that is needed to utilize npd. Integrating any
special applications can then be done anytime thereafter.

Use the following syntax to start npd: npd devicejile ipname portname

where:
devicefile Name for a pseudo-tty pair's slave device acquired by npd.
ipname print server IP name or IP address.

42 Ethernet Print Server User's Manual

 portname print server VO port name (i.e. pltl, plt2).

Note: The devicejle cannot exist prior to starting npd and this particular npd
daemon cannot be running already. It is possible to have more than one
daemon running on the same host, howeves as long as they are not using the
same devicejile.

Example: npd /dev/spike.plt2 spike plt2

This starts an npd daemon utilizing ldevlspike.plt2 to send print jobs to the plt2
port on the print server named spike.

By default, npd looks in the Idev directory to find a free pseudo-tty pair
(Idevlpty?? and tdevltty?? files). However, if your UNIX system has these files
in a different directory, you can specify the directory pathname with a -p
option.

Example: npd -p Idevlpty ldevlspike.plt2 spike plt2

where Idevlpty is the directory to be searched for a free pseudo-tty pair.

Some systems such as HPUX place the master and slave devices in separate
directories (e.g. Idevlptym and Idevlpty). Specify where each of the pairs
reside with the -pm and -ps options.

Example: npd -pm Idevlptym -ps Idevlpty Idevlspike.plt2spike pit2

where Idevlptym is the directory searched to find a free pseudo-tty pair's

master device and Idevlpty is the directory used for locating the pseudo-tty pair
slave device.

npd locks
As npd acquires an exclusive lock on the print server port, it is possible to lock
out other daemons that may reside on other UNIX hosts. Therefore, npd is
designed to timeout and release the lock if the pseudo-tty pair is idle for a
specified time (30 seconds is the default). You can modify this value with the
-t option.

Example: npd -t 60 ldevlspike.plt2 spike plt2

for the timeout to occur in 60 seconds.

TCPIIP Unix configuration

Testing npd
Once npd has been started, it's a good idea to test and see if npd is working
before trying to print through the spooler. This is one test method.

Example: eat test.txt > ldevlspike.plt2

redirects the cat output of testsxt to the npd device /dev/spike.plt2

which is then sent to the print server named spike.

Modifying a host to use npd

If you want the npd daemon to start every time you reboot your UNIX
machine, edit your .rc file to include the appropriate npd startup command line
(from the previous section). After npd starts, integrate the print spooler into this
pseudo-tty setup.

In BSD print spooler systems, modify the Ip= field in the appropriate printer
entry in the JetcJprintcap file. Set Ip= to the devicefile argument of the npd
program.

On SystemV systems, the -v option in the lpadmin command will equal the
devicefile.

44 Ethernet Print Sewer User's Manual

Stopping npd
Whenever an npd daemon starts, it makes a log entry in thehsv'adn-hpdlog
file. The contents of this file have the following naming information:

pid ipname port masterfile slavefile devicefile

where:

pid Process ID of npd daemon.

ipname print server IP address or IP name serviced by npd.

port print server VO port used by npd (that is: pltl, plt2).

masterfile Master device used by npd.

slavefile Slave device used by npd.

devicefile Name linked to the slavefile by npd.

Example: 153 spike plt2 Idevlptyql Idevlttyql ldevlspike.plt2

is the log entry for the npd daemon using process ID 153.

You can acquire the process ID of the npd daemon that needs to be stopped and
then execute the following kill command for that process:

kill -TERM pid

TCPnP Unix configuration

I

tions using n

Sun NeWSprint page accounting works with Postscript printers. It utilizes the
bi-directionality of the print server to get this status back to the host.

Add anew Sun NeWSprint printer entry with the add-np-printer program. The
pseudo-tty device is a serial interface. Therefore, when this program prompts
you for a device interface, select Serial and device suffix a for any port on the
unit.

After NeWSprint creates the necessary spooling directory and entry in the
letclprintcap file, set the lp= field in the new entry to the devicefile argument
of the npd program.

Example: The modified Ietclprintcap entry looks like this for a print server
named spike:
# entry for a Postscript printer
pslPostScriptlPostScripton spike's plt2 port:\
:Ip=/dev/spike.plt2:\
:sd=/b/newsprinUlpd/spike/plt2:\
:If=Mnewsprintnpd/spike/plt2Aog:\
:af=/b/newsprinfflpd/spike/plt2/acct:\
:if=lb/newsprinfflpd/if:\
:gf=/b/newsprinfflpd/gf:\
:nf=/b/newsprinUlpd/nf:\
:tf=/b/newsprinfflpdftf:\
:rf=/blnewsprinfflpd/rf:\
:vf=/b/newsprinfflpd/vf:\
:cf=lblnewsprinfflpd/cf:\
:df=/b/newsprinthpd/df:\
:of=/b/newsprinfflpd/of:\
:mx#O:\
:sf:\
:sb:\
:xc#0177777:\
Note: Ifyou are using the PostScript option, remember to include :sh:\ in this
entry to suppress the standard LPD header:

46 Ethernet Print Server User's Manual

Adobe Transcript
Adobe Transcript page accounting works with Postscript printers. It utilizes
the bi-directionality of the unit to get this status back to the host.

Create and edit this .options file in the printer's spooling directory with global
read permissions. This setup uses rsh/rcmd/remsh or npwrite to talk to the unit.

Add the following variable definitions in this .options file:

NPDIR-PATH Define the directory location of npcomm.sh program.

Usually /usr/local/bin.

PSCOMM Redefine the communication program used by psint.sh to

use npcommsh instead of pscomm.

RCMD Specify the name of the remote shell command to use for
transferring data to the print server (i.e. rsh).

UNIT-NAME Define the print server IP name or IP address.

LKDEST Specify the print server destination name.

Use the mkprintersh program to add a new AdobeTranScript printer entry. For
now, use /dev/ttypa as the device interface for any port on the print server.
When the program creates the spooling directory and entry in letclprintcap file,
set the Ip= field to the devicefile argument from npd.

Example:

pslPostScriptlPostScript on spike's plt2 port:\

:Ip=/devIspike.pIt2:\
:sd=/usr/spooVlpd/spike/plt2:\
:If=lusr/adm/printers/ps-log:\
:af=/usr/adm/printers/ps-acct:\
:rw:fc#0000374:fs#0000003:\
:xc#0:xs#0040040:mx#O:sf:sb:\
:if=/usrAocaVlib/ts/psif:\
:of=/usrAocaVlib/ts/psof:\
:gf=/usflocaYlib/ts/psgf:\
:nf=/usflocaVlib/ts/psnf:\
:tf=/usdocaVlib/ts/pstf:\
:rf=lusrAocaMib/ts/psrf:\

TCPDP Unix configuration

Note: Using :sh:\ in this entry will suppress headers and also prevent
Transcriptfrom printing out hunner pages if they are set in the .optionsfile.

Ethernet Print Sewer User's Manual

IBM has a unique print spooler system that uses the qdaemon program. Use the
following steps to interface with the print server using rsh:

Note: These steps and associated examples refer to a setup with a queue named
queue2, a queue device named IpO, printing to the destination dlpltl on the
print server named spike.

Create a device. Enter: smit pdp

Select Printer/Plotter and then Add a PrinterPlotter. Follow the prompts until
SMIT executes the "mkdev" command to create this device.
Note: Select "parallel" as the interface.

Select p as the port number.

Select ppaO as the adapter.
Select a printer type that best matches what you are using.
Select a device 1pO. If this device is not available, go back and select "Remove
a Printer/Plotter" and remove IpO making it available for your next run through.
AIX has a limit of four physical devices. If you run out, IBM suggests deleting
the device after completing a print setup thus making it available for future
setups.
Create a new queue. Enter: mkque -q queue2
Create a queue device to do the one-to-one mapping with the printer and
specify the backend program for the qdaemon to send print jobs to. E n w :
mkquedev -d IpO -q queue2 -a 'backend = /usr/lib/lpd/piobe'
Sometimes /usrllpd/piobe is the location of this backend program.
Create a virtual port. This associates the queue, queue device, printerlplotter
name, data type, and printer/plotter type.

Enter: mkvirprt -q queue2 -d IpO -n Ip0 -s pcl -6 hplj3

-s is usually pcl but can also be ps (Postscript) or asc (ASCII).

Change the pio-file for your queue. This will be located in

/usr/lib/lpd/pio/custom and will be called queue2:lpO after the queue and queue
device names. Change the line beginning with 307 mo::.
Enter: 307 mo::rsh spike Ip -d dlpltl

This file is only created after the mkvirprt command has been executed in Step
5. This step redirects the print job over the network to the print server.

TCPfiP Unix configuration 49

 For destinations other than dlplt I , please see 'Destinations' on page 84.

7 Run chvirprt since the print setup has been altered and needs updating.
Enter: chvirprt -q queue2 -d IpO

If you need to delete an entire print setup, use the rmvirprt command.

This is the Ietclqconfig entry created for this particular setup:

Example: queue;?: queue stanza

device = IpO by mkquedev (queue device)
up = TRUE printer S ready to go
IpO: queue device stanza
backend = Iusrllibllpd/piobe for local printing

For further information on these commands, please see your AIX system
documentation.

Ethernet Print Server User's Manual

Other TC rint methods

NCSA
NCSA is a freeware package available on the Internet at zaphod.ncsa.uiuc.edu
in the directory /PC/Telnet/msdos/contributions. The file is tel23bin.zip. It
contains an lpr client for DOS that is compatible with the print server.

You can send jobs to the print server with the following command syntax:
Ipr -Sipname -Pdestname
where ipname is the print server I P name or IP address and destname is the
name of a print server destination.

Example: lpr &pike -Pd2plt2

which sends a print job to d2plt2 on the print server named spike.

FTP's PC/TCP
FTP Software markets a package called PCRCP which provides an lpr client
for DOS that is compatible with the print server.

Jobs can be sent to the print server directly with the following command syntax
after an entry has been made for the print server in the host table:

lpr -Sipname -Pdestname

where ipname is the print server's IP name or IP address and destname is the
name of an print server destination.

Example: lpr &spike -Pd2plt2

sends a print job to d2plt2 on the print server named spike.

FTP's package also provides Windows printing along with several other
software packages on the market. These are just two possible applications that
will work with the print server. Please see the user manuals of the appropriate
applications for more information.

TCPAP Unix configuration

Direct socket printing
The print server provides a socket interface for custom printing applications.
Programs can open a TCP connection to a TCP port on the print server. The
specified port number corresponds to a destination on the print server, and data
is processed according to the model associated with this destination. Please see
list pserver, list dest and list model in 'Command set' on page 89, for more
details.

npwrite is a sample program that performs this way. It is included in the host
software shipped with your print server. For examples, please refer to 'Direct
printing without the spooler' on page 30.

FTP daemon
The FTP daemon provides an additional method to submit print jobs to the
print server. For a complete discussion of printing and other print server
functions using the FTP daemon, please see 'FTPdaemon' on page 131.

Now that your TCP/IP host is configured for printing, please look to the
following for further configuration options:

Add to or change configuration of your print server.

Please see 'Command set' on page 89.

Utilize more advanced features of the print server.

Please see 'Options' on page 117.

Ethernet Print Server User's Manual

 Ethernet Print Server
User's Manual

This chapter introduces the Ethernet print server's

conjguration possibilities along with the various methods
of printing available within a Novel1 environment.
The print server works withJifferent NetWare versions,
including version 4. Setup steps are provided for each.
Host soft
Netware's PCONSOLE is generally used to change passwords, add print
servers, add remote printers, and add queues to be serviced. It can be used for
both a PSERVER or RPRINTER setup. To install a print server in a Novell
environment, PCONSOLE is used for the entire installation. The following
pages give step-by-step examples of installing the print server in various
Novell environments.

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, npsh.exe is included. npsh.exe is aDOS executable program that can
be run from a DOS prompt on a NetWare workstation.

npsh nvplist Lists all of the print server's on the network; each name is in the
format 0-xxxxxx (where xxxxxx equals the last six digits of the unit's
Ethernet address) by default regardless of whether it is configured as a
PSERVER or an RPRINTER. This name is configurable.

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

npsh unitname command Initiates a single command with guest access only
to the unit instead of entering into a complete session.

To communicate with the unit using npsh.exe, you need to:

t From a DOS prompt on a Novell workstation, begin an npsh session with the
unit.
Type: npsh unitname

which starts aTelnet-like session with the named print server with guest access
only.

2 To obtain root access to the unit,

54 Ethernet Print Server User's Manual

 Type: supervisor

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

3 Login to the unit as a root user.

Type: root

Root users require the use of a password as configured in the unit's 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 on 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 npsh.exe makes use of broadcasts, you may have problems
communicating across a router: Therefore, it should be run on the same
subnetwork as the printer For instance, it will not work when run on a
non-dedicated server such as Netware for OSB, because the server simulates
an internal alternate subnetwork.

Please see 'User accounts and permissions' on page 91 and'npsh command

set' on page 93 for further details.

Novell configuration
 er configuration
The print server configuration in a Novell environment is much simpler than
that required in a TCPIIP one. No addresses, masks, or router entries are
necessary and in most cases, the print server can simply be connected to the
network, turned on, and then configured for printing from a Novell station
through PCONSOLE. The only parameters that you may want to set is a
PSERVER password or possibly the frame type.

Please see 'store pserver' on page 1 12.

This type of configuration is done using npshexe as detailed on 'npsh.exe' on

page 54.

56 Ethernet Print Sewer User's Manual

-
Host configuration
The print server can act as either a PSERVER or as a RPRINTER in a Novell
environment. It supports encrypted passwords and it is capable of servicing up
to 16 file servers and 32 queues as a PSERVER. One print server can handle
eight RPRINTER setups.

PSERVER bootup
When booting as a PSERVER, the print server gets a server list from the first
file server it contacts. The unit then contacts those servers on that list to see if
there is a queue that needs servicing. The queues are then be polled every 5
seconds (by default) by the print server to see if there are any jobs queued.

RPRINTER bootup
When booting as a RPRINTER, the print server again gets a server list from
the first file server it contacts. For each server found on that list, it then looks
for a file called SYS:\LOGIN\O~xxxxxx\CONFIG where xxxxxx is the last six
hexadecimal digits in the Ethernet address found on a sticker on the board. This
file contains one set rprinter command for each RPRINTER serviced by the
print server since the RPRINTER settings do not hold their effect through a
power cycle.

If the print server loses a connection to a file server (as a PSERVER) or to a

PSERVER (as a RPRTNTER), it will automatically reconnect when that server
becomes available again.

Following is the configuration steps for a PSERVER setup, a RPRINTER

setup, as well as the options available for NetWare 4 environments.

Novell configuration
 ERVER setu
This procedure configures the Noveil file server to use an print server as a
PSERVER in a non-NetWare 4 environment. Please see NetWare 4 Options on
page 61 for more on a NetWare 4 setup.

The print server replaces a dedicated workstation running PSERVER.EXE or

PSERVER.NLM on the file server, so these are no longer needed.

To set up the unit as a PSERVER in a non-NetWare 4 environment, you need

to:

Step Action Result of Action

-
1 Log in to Novell as supervisor. Gives you supervisor rights.
-
2 Enter PCONSOLE. PCONSOLE's Main Menu displays.
Select PRINT QUEUE List of currently-defined queues comes up.
INFORMATION.
Press <Insert> to add a queue. Asks for new queue's name.
Type in this new name in any format New queue is added to list.
you like and press <Enten.
Press <Escape>. Returns to PCONSOLE's Main Menu.
Select PRINT SERVER
INFORMATION.
Press <Insert> to add a server. Prompts for the server's name.

Type the name of the print server. By This new server is added to the list.
default, it is 0-xxxxxx where xxxxxx
equals the last six digits of the unit's
Ethernet address. (e.g.0-000BF5)
Select the new server and press PRINT SERVER INFORMATION menu
anten. comes up.
Select PRINT SERVER This menu displays.
CONFIGURATION.
Select PRINTER CONFIGURATION.
Select the first item listed as NOT The PRINTER N CONFIGURATION window
INSTALLED and press <Enten.

Ethernet Print Server User's Manual

-
Step Action Result of Action
-
7

14 Type in the name of one of the eight Cursor sits at the Type field with a printer name
default destinations on the unit for the now assigned.
Name field (e.g, dlpltl, d5plt1, etc.)
and go to the Type field.
- Press <Enten at this field and then Comes back to the PRINTER N
15
select DEFINED ELSEWHERE. CONFIGURATION window.
Press <Escape> and select Yes to save Gives you the option to define more printers.
changes.
Press <Escape> again. Returns to PRINT SERVER
CONFIGURATION menu.
Select QUEUES SERVICED BY A list of defined printers displays.
PRINTER.
Select one of these printers. A list of queues comes up. It will be empty the
first time you use it.
Press <Insert>. Displays a list of available queues.
Select the queue created earlier to Asks for a priority.
service this printer and press <Enten.
Press <Enter> to select the default. Comes back to queue list.
This is fine for most cases.
Press <Escape> back to Main Menu Main Menu displays.
Reboot the print server by unplugging Unit will boot up and see the new queue that it
*
and plugging it back in. has to service. This may take a minute.
Check CURRENTLY ATTACHED You should see the print server's name
SERVERS once you have gone into displayed (e.g. 0-000BF5).
view the appropriate queue.
Press <Escape> until you have exited The configuration is complete.
PCONSOLE.

Novell configuration
 NTER setup (
This procedure associates an existing PSERVER with a remote print server
acting as a RPRINTER in a pre-NetWare 4 environment. It is the PSERVER's
responsibility to get jobs from the queue and to pass them off to the print server
acting as the remote printer. Unlike a PSERVER set-up, the print server does
not deal directly with the queues.

As a RPRINTER, the print server does not use a login ID. In addition, a
non-print server PSERVER (e.g. PSERVER.NLM) must be running for
RPRINTER to operate.

A RPRINTER set up requires the use of a configuration file. This file is

required to tell the print server to act as a RPRINTER upon boot up since
RPRINTER settings do not hold their effect through a power cycle. Once the
unit boots up, the print server contacts file servers it knows about and on each
one, looks for the file SYS:UOGIN\O~xxxXxx\CONFIGwhere xxxxxx is the
last six digits (in hexadecimal) of the Ethernet address as noted at installation
time (Refere to page 161). If it finds this file, it reads in each entry as if it were
an npsh command entered on a terminal attached to the Ethernet print server.

To ensure that the print server contacts the file server that contains the
CONFIG file, set up the appropriate file server as a preferred file server. Please
see 'Setting preferred file sewers' on page 126, for more information.

Attention: Ifyou are using a con$gurationjle and you have changed the
name of the print server, you must change the name of the directory
containing thisjle.
i

3
60 Ethernet Print Sewer User's Manual
I
 To set up the unit as a RPRINTER in a pre-Netware 4 environment, you need to:

Action Result of Action

Log in to Novel1 as supervisor. Gives you supervisor rights.
Enter PCONSOLE. PCONSOLE's Main Menu displays.
Select PRINT QUEUE List of currently-defined queues comes up.
INFORMATION.
Press <Insert> to add a queue. Asks for new queue's name.
Type in this new name in any format New queue is added to list.
you like and press <Enter>.
Press <Escape>. Returns to PCONSOLE's Main Menu.
Select PRINT SERVER A list of existing print servers displays.
INFORMATION.
Select one of the print servers and press Display's PRINT SERVER INFORMATION
<Enter>. menu.
Select PRINT SERVER Brings up this menu.
CONFIGURATION.
Select PRINTER CONFIGURATION. Displays a list of printers associated with the
print server.
Select or create a printer name which PRINTER N CONFIGURATION window
you want to install as a remote printer displays where N equals the selected printer.
and press <Enter>.
Put the cursor on the Type field and A list of options comes up.
press <Enten.
Select REMOTE This displays in thel'ype field.
OTHERXINKNOWN.
Ignore the other fields and press Takes you back to the list of printers.
<Escape> to save these changes.
Press <Escape> until you are at the Displays this menu.
PRINT SERVER CONFIGURATION
menu again.
Select QUEUS SERVICED BY A list of defined printers for this print server is
PRINTER. shown.
Select the printer you previously An empty queue list comes up.
defined and press <Enter>.

Novell configuration
Action Result of Action
Press <Insert>. A list of available queues displays.
Select thequeue you want this printer to Prompts you for a priority.
service and press <Enten.
Press < E n t e n to use the default. Returns you to the queue list.
Usually this is fine.
Press <Escape> until you have exited You're now at the command prompt.
PCONSOLE.
Start PSERVER. Starts the PSERVER so the print server can
service it as an RPRINTER.
In SYS VOLUME on the file server, You will be at this prompt.
change to the \LOGIN directory.
Create a directory named after the print This directory is created.
server. By default, this will be
0-xxxxxx wherexxxxxx is the last six
digits of the unit's Ethernet address.
(e.g. 0-.000BF5)
Within this directory, create a file called A blank file displays.
CONFIG and open it for editing.
Enter the line: set rprinter add One entry is written in the file. One entry is
pservername printernumber destname required for each RPRINTER serviced by the
where pservername equals the existing print server.
PSERVER's name, printernumber
equals the defined number for this
printer in that PSERVER, and destname
equals a print server destination
(e.g. dlpltl, d5plt1, etc.).
Reboot the print server to enable these The print server will boot up and read this entry
changes. from the CONFIG file and set itself to act as an
RPRINTER.

Ethernet Print Server User's Manual

NetWare 4 options
NetWare 4 introduces NDS and some new frame types. The print server can be
used in a NetWare 4 environment with either of these options:

Set the print server up as a PSERVER replacing a dedicated workstation

running PSERVER.EXE or PSERVER.NLM on the file server. The print
server replaces these loadable PSERVER's so they are no longer needed.
r Set the print server up as a RPRINTER interacting with an existing
PSERVER.

If following a PSERVER setup, bindery emulation is required.

Included in this sub-section are the steps for a PSERVER setup since the steps
have changed now that bindery emulation is required. A RPRINTER setup is
not included since the only changes from a pre-NetWare 4 RPRINTER setup
are some name changes in PCONSOLE.

To configure the unit as a PSERVER in a NetWare 4 environment, you need to:

Action Result of Action

I

Log in to Novel1 as supervisor. I Gives you supervisor rights.

I

Enter PCONSOLE. I PCONSOLE's Main Menu displays.

Press F4. Puts you into bindery emulation mode and
displays Main Menu.
Select PRINT QUEUES. List of currently-defined queues comes up.
Press <Insert> to add a queue. Asks for new queue's name.
Type in this new name and press New queue is added to list.
<Enter>.
Press <Escape>. Returns to PCONSOLE's Main Menu.
Select PRINT SERVERS. A list of existing print servers displays.
Press Insert to add a new print server. Prompts you for the name of the print server.
Type the name of the print server. By This new server is added to the list.
default, it is 0-xxxxxx where xxxxxx
equals the last six digits of the unit's
Ethernet address. (e.g. 0-000BF5)

Novell configuration 63
 Action Result of Action
Select this new print server and press PRINT SERVER INFORMATION menu
<Enten. displays.
Select PRINTERS. A list of defined printers comes up.
Press <Insert> to add a printer to the Prompts you for the printer name, type, and
list. some additional fields.
Type in the name of one of the eight Cursor moves to this field.
default destinations on the unit for the
Name field (e.g. dlprnl, d5plt1, etc.)
and go to the Q p e field.
Press <Enten at this field and then Brings you back to the printer's window.
select DEFINED ELSEWHERE. If
DEFINED ELSEWHERE is not
available, choose PARALLEL.
Press <Enten on the Print Queues List of available queues is displayed.
Assigned field. ..
Press <Insert> to display all queues; You are prompted for a priority
select the one you defined earlier and
press <Enten.
Select a priority and press <Enter>. Printer's window displays with fields now
Priority 1 should be fine. filled in.
Press <Escape> until you are back to Main Menu is displayed.
Main Menu.
Reboot the print server by unplugging Unit resets and realizes its new configuration. It
and then plugging it back in. then attaches to the queue after 30 seconds or
SO.

Check the CURRENTLY ATTACHED You should see the print server's name
SERVERS once you have gone into displayed (e.g. 0-OOOBF5).
view the appropriate queue.
Press <Escape> until you are out of The configuration is now complete.
PCONSOLE.

64 Ethernet Print Sewer User's Manual

If you want to continue with any of the following procedures, please find them
as indicated in other sections of this manual:

Add to or change configuration of your print server. Refer to 'Using the

command set', on page 89.
Utilize more advanced features of the print server. Refer to 'Options' on
page 117.
rn Troubleshoot Novell installation and printing problems. Refer to
'Troubleshooting' on page 139.

Novell configuration
Ethernet Print Sewer User's Manual
 Ethernet Print Server
User's Manual

This chapter will cover the few steps required to get your
print jobs printing to an Ethernet print sewer in an
AppleTalk over EtherTalk environment.

Note: The print server does not support LocalTalk.

__11_1

Attention: To print from a Macintosh via EtherTalk, the PostScript option

must be installed in the printer and the printer data format must be set to
PostScript. This can be done from the printer's control panel or from your
workstation, via a remote configuration header (RCH).
rint server onfiguration
An AppleTalk setup does not require any print server configuration. The
network parameters are automatically configured for you once the printer has
been switched OFFION to reboot the print server.

If you wish to modify some of the print server's default settings, you can use
the built-in command set. See Chapter 8, Using the command set, for more
information on the available commands.

There is no host software provided for the Macintosh. To do any configuration

on the unit, you must rely on:

a npsh commands available through a telnet session. These commands could

be issued from a Macintosh workstation if you a running program like NCSA
Telnet and MacTCP is installed on your system.
a Novel1 workstation running the host software npsh.exe.
r a terminal, PC, or laptop connected to the serial port on the print server.

Ethernet Print Sewer User's Manual

Host configuration
Once you have physically attached the print server to the network, the
following steps will get your Apple host printing to the print server:

1 Select Chooser from the Apple Menu.

2 Select the appropriate print driver icon (e.g. Laserwriter icon).
A list of available printers will appear. By default, the format of each name is
020xname-papname where 020xname is the name of the print server and
papname is an print server 110 port. Both names are configurable.

Example: 0-000BF5-pit1

is the printer associated with the print server named 0-000BF5 using the first
port.

The print sewer's default name is 0-xxxxxx where xxxxxx equals the last six
digits of the unit's Ethernet address as noted at installation time (Refer to
page 164).

3 From the list of printers, select one to print to.

You have now configured your AppleTalk system to print to the print server.

AppleTalk configuration
AppleTalk zones
If the print server does not come up in the correct AppleTalk zone, you can
configure a particular zone name on the unit. To do this, start an npsh session
with the unit and enter the following command:

store pserver apple zone [zonename]

reset
where zonename is the zone where you want the print server to appear.

To clear the AppleTalk zone, type the command without entering a zonename
and press <Enten.

Changing print server name

By default, the print server's name is 020xname-papname where 020xname
is the name of the print server and papname is an print server I/O port. The npsh
command, list pserver, will give you a listing showing both the print server
name and the papname.

The following example details the steps necessary to change the name that
appears in the Chooser from 0-000BF5-pltl to Sales-laser.

1 Start an npsh session with the unit.

2 Enter the name that you would like to appear for the print server (e.g. Sales).
This will make up the first part of the name in the Chooser.
Type: store pserver name Sales

Note: This new name will also affect Unix, Novel1 and NetBIOS setups.

3 Enter the name that you would like to appear for the papname (e.g. laser). This
will make up the second part of the name in the Chooser.
Qpe: store pserver applepap pltl name laser

4 Reset the unit so the changes take effect.

Type: reset

70 Ethernet Print Server User's Manual

-
Removing excess printers from the chooser
When you first install an print server in an AppleTalk environment, you will
notice that two printers show up in your Chooser; one printer for each
destination on the print server that has AppleTalk services enabled.

If you want to limit the number of printers showing up in the Chooser, you need
to disable the AppleTalk service from the related destination's list of services.
To do this, start an npsh session with the unit and follow the steps below:

1 Display a listing of the print server's characteristics across all protocols.

Type: list pserver

2 Look at the Apple Pap section of the listing to learn the destination name that
corresponds with the unnecessary printer's papname.
3 For each printer that you do not want to appear in the Chooser, disable the
AppleTalk service from the corresponding destination's list of services. Type
the following command:
set dest destname service [socket] [lpd] [lpsched]
[rprinter] [pserver] [netbios] [ftpd]
When typing this command string, you are merely omitting the reference to the
AppleTalk service. You can also turn off any other services that are not required
by this destination by also omitting them from the command string.

4 Repeat the previous step until you have removed the AppleTalk service from
each of destinations that correspond to the papname of the unnecessary
printers.
5 Save the changes to EEPROM.
Type: save

Disabling the AppleTalk module

If you have several print servers in your network and only some of them are
servicing AppleTalk networks, it is a good idea to turn off the entire AppleTalk
module from the particular print server. This will not only save on print server
resources but will ensure that only appropriate print servers show up in the
Chooser.

AppleTalk configuration
 To disable the AppleTalk module, start an npsh session with the unit and follow
the steps below:

1 Remove AppleTalk from the available protocols.

5pe: set sysinfo module novel1

You are merely leaving out AppleTalk from the command string of available
protocols. You can also turn off the Novell protocol by leaving it out of the
command string if the print server is not servicing any Novell networks. The
TCP/IP module cannot be turned off.

2 Save the changes to EEPROM.

5pe: save
If you want to continue with any of the following procedures, please find them
as indicated in other sections of this manual:

Add to or change configuration of your print server. Please see 'Using the
command set', on page 89. P
u Utilize more advanced features of the print server. Please see 'Options' on
page 117.

Ethernet Print Server User's Manual

 Ethernet Print Server
User's Manual

This chapter discusses the print server's NetBIOS over

TCP/IP support. The print server provides support for all
versions of Windows NT (including version 3.5), Windows 95
and Windows for Workgroupj +.‘(WfW) so examples of various
conjigurations are provided.
In these supported environments, TCP/IP is the data transfer
protocol used for printing. This means that IP addresses and
netmasks are required in your Windows network along with
the appropriate TCP/IP software. This chapter will also
discuss how you set this up in your environment.
 ---

Basic setup sets

There are two ways that the print server can fit into a Windows environment:

m Windows NT, Windows 95 or WfW workstations spooling to a Windows NT

Server which then prints to the print server.
r Windows NT, Windows 95 or WfW workstations printing directly to the print
server.

The steps in this chapter will help you get one workstation or server printing
to the print server print server. From there, you can set up other workstations
to either print directly to the print server or to spool to a central area.

We recommend the use of a central spooling area where a shared printer is

created.

In each of these environments, the basic setup steps required to get you printing
from one of these hosts are:
",

1 Ensure that you have the appropriate network software installed.

2 Configure the print server with an IP address and netmask.
3 Create a printer and select a method of printing to the print server (i.e. net use
connection or LPR).

Setting up TCPAP on Windows workstations

Since TCPAP is used as the data transfer protocol, EP addresses and netmasks
must be assigned to your Windows NT, Windows 95 or WfW workstation(s) if
you haven't already done so.

If you are not familiar with IP addresses and are sure that this network will not
go onto the Internet, the following are some sample settings to use:

I I
IP Address
I
Netmask
Host 1 192.1.1.1 I 255.255.255.0
Print server 192.1.1.2 255.255.255.0
Host 2 192.1.1.3 255.255.255.0
and so on...

74 Ethernet Print Server User's Manual

I
 To install the necessary software, please see the following sections below.
Generally, when you install this software,you will be prompted for theTCPLP
settings (That is, IP address and netmask). If you are not prompted for these
settings, please refer to your Windows documentation.

1_11

Windows NT version 3.5 (Net Use)

To make sure NetBIOS over TCPLP services are available, you need to:

1 Select Control Panel.

2 Select Network.
3 Look under Installed Network Software for NetBIOS TCP/IP. If it is there
already, then NetBIOS over TCPLP services are available and you can stop
these steps. If not, continue on.
4 Select Bindings.
5 Under Show Bindings For, choose All Components.
6 Choose Server -> NetBIOS TCPLP -> Streams Environment from the
available bindings list.
7 Select OK to add this to the Installed Network Software list in the previous
window.
8 At the previous window, select Add Software.
9 Choose TCP/IP Protocol from the Network Software list.
10 Select Continue to add this software.
11 Select OK to get out of this window.

Windows NT version 3.5 (LPR Client)

To make sure the TCPm services are available to allow you to print using
Windows NT LPR client, you need to:

1 Select Main.
2 Select Control Panel.
3 Select Network.
4 In this Network Settings dialogue box, make sure you see these in the Installed
Network Software scroll box:
MS TCP/IP Printing
TCP/IP Protocol
Simple TCPLP Service

NETBIOS configuration
 5 If these are not there, please install them and bind them to the network card.
Steps 3 to 11 in the previous section provide an example of this. Be sure,
however, to select the software components listed in step 4 of this section.

Windows for workgroups (WNV)

Make sure NetBIOS over TCP/IP services are available. With WfW, you
should have the Microsoft TCPIIP-32 group in your Program Manager. This
software is free from any of Microsoft's sites. The file is called wfwt32.exe.

Windows 95 and Windows NT4

Make sure NetBIOS over TCP/IP services are available as follows:

1 Open the control panel

2 Double-click on the Network icon XS-

3 Select the bindings tab (you need Administrator privilege)

4 If the "NetBios Interface" entry is present (which it should be)
5 Click on the + sign on its right and check that the line
"WINS client (TCPAP)" is present.

76 Ethernet Print Server User's Manual

_1_1

Print server configuration

Since TCPIIP is being utilized, the unit's configuration involves storing an IP
address and a netmask. This is normally handled with the arp command but in
the case of Windows NT, Windows 95 and WfW, this does not work reliably.

Therefore, the best way to store an IP address and a netmask is to connect a

terminal, PC, or laptop to one of the print server's serial ports. This will log you
into the unit where you can store the IP address and netmask.

To configure a print server with its network settings, please see 'Manual
configuration through the serial port' on page 28, for detailed instructions.

Once you have configured the unit the print server is configured and
recognizable on the network. At this point, you can now configure your host.

NETBIOS configuration
 Now that your workstation(s) and the print server have IP addresses and
netmasks, you can now configure a print setup. There are several methods
available depending on what Windows package you are using.

Windows NT version 3.5

With the introduction of an LPR client in Version 3.5, there are now two
choices for printing:

use the net use command

use the new LPR client to interact with the print server's built-in Line Printer
Daemon

Net use method

To set up a net use method you need to:

1 Open a DOS window.

2 From the DOS prompt, type the following command:
net use device \\unitname\destination
where:

unitname Will be 0-xxxxxx where xxxxxx is equal to the last six digits of
the unit's Ethernet address as noted at installation time. (Refer to page 164).
This is the default name which can be can be seen with a debug netbios
command on the unit itself.

destinationIs a pre-defined destination or queue on the print server that is

automatically mapped to an VO port. For example, destination dlpltl is
automatically mapped to the PLTl port. Please see 'Destinations' on page 84
for a more detailed description. Please note that destinations are case sensitive
and are lowercase by default.

Example: net use LPTl\\0_000BF5\dlpltl

3 Create a printer to use this NetBIOS over TCP/IP path; select Control Panel.
4 Select Printers.
5 Choose a listed printer or add one.

Ethernet Print Sewer User's Manual

6 Select Connect.
7 Choose a device:path to use (e.g. LPTI: \\0-000BF5\dlpltl)
8 Select OK.

Now this printer is available for printing. If you have another workstation (i.e.
WfW) that you want to access this printer, just make the printer shared on your
Windows NT workstations. To do this, you need to:

1 Export this printer as Shared on the Windows NT workstation.

2 Select this shared printer to print on your WfW workstation.

From this point on, print jobs will be spooled over to the Windows NT
workstation and then sent to the print server. This is a very clean and reliable
print method.

LPR method

To setup a LPR method, you need to:

1 Create a print path and printer; select Main.

2 Select Control Panel.
3 Select Printers which loads up the Print Manager.
4 Select Create a Printer from the Printer menu.
5 Define the printer name and driver; in the Print to field, select Other. ...
6 Choose LPR port from the list that comes up and select OK.
7 Fill in the host name or IP address of the print server.
8 Fill in the destination or queue on the print server (e.g. dlpltl) and select OK.

where:

destinationls a pre-defined destination or queue on the print server that is

automatically mapped to an 110 port. For example, destination dlpltl is
automatically mapped to the PLTl port. Please see 'Destinations' on page 84
for a more detailed description. Please note that destinations are case sensitive
and are lowercase by default.

This printer is now available for printing and will interact with the print
server's built-in line printer daemon.

NETBIOS configuration
Windows for workgroups (WfW)
To set up a Windows for Workgroups configuration, you need to:

1 Create a print path; select Print Manager.

2 Choose Connect Network Printer from the Printer menu.
3 Fill in the dialogue box with:
device Device on the workstation (e.g. LPT1).

path Net use print path in the format \\unitname\destination

(e.g. \\0_000BF5\dl pltl)

where:
unitname Will be 0-xxxxxx where xxxxxx is equal to the last six digits of
the unit's Ethernet address as noted at installation time. (Refer to page 164).
This is the default name which can be can be seen with a debug netbios
command on the unit itself.
destination Is a pre-defined destination opqueue on the print server that is
automatically mapped to an VO port. For example, destination dlpltl is
automatically mapped to the PLTl port. Please see 'Destinations' on page 84,
for a more detailed description.

Note: Destinations are case sensitive and are lowercase by default.

4 Select OK.
5 Create a printer to use this path; select Control Panel.
6 Select Printers.
7 Choose a listed printer or add one.
8 Select Connect.
9 Choose a device:path to use (e.g. LPTl:\\O-000BFS\dlpltl).
10 Select OK.

You have now configured your Windows for Workgroups workstation to print
to the print server. This completes the entire print setup unless you want to
enhance it.

For further information see:

Add to or change configuration of your print server. Please see 'Using the
command set', on page 89.
Utilize more advanced features of the print server. Please see 'Additional
options', on page 117.

80 Ethernet Print Sewer User's Manual

-
Windows 95 and Windows NT4
1 Click on the "Start" button
2 Select the Settings->Printers menu
3 Click on "Add printer"
4 Select "Network Printer server"
5 Enter the path to the printer port in the "Printer:" box.
(for example: \\0-020001\dl pltl)
6 You get a message stating that the remote device does not have a valid driver
and which proposes that you install it locally.
7 Select OK
8 Select the driver from the driver list
9 You get a message asking whether you want your Windows-based programs to
use this printer as the default printer.
10 Typically you would select "No".
11 Select Finish

You have now configured your Windows 95 or Windows NT4 workstation to

print to the print server. This completes the entire print setup unless you want
to enhance it.

NETBIOS configuration
82 Ethernet Print Server User's Manual
 Ethernet Print Server
User S Manual

This chapter will provide a more detailed description of the

internal operating architecture of the Ethernet print sewer
including:
* destinations,
* models,
* variables,
* logpaths,
* I/O ports.
 Destinations
The print server provides eight printer destinations that are used by all hosts. A
destination can be thought of as logical place on the print server to which hosts
send their print jobs. Destinations allow you the ability to configure a number
of different print setups on the print server.

Destinations map a name, with a nine-character maximum, to the UO ports and

by default, each YO port comes with two destinations mapped to it. The default
destination names are:

dlpltl d2plt2 d3pltl d4plt2

d5pltl d6plt2 d7pltl d8plt2

Any of the eight destinations can be matched to any of the two UO ports, and
each destination uses one of the defined models for processing. The destination
list is limited to a maximum of eight entries; and is configured through the npsh
interface on the print server. Default destination names can also be changed to
something more meaningful.

Destination definitions include: name, U0 port, model used, logpath, state,

service(s) supported, and alternate destination.

See also: 'list dest' on page 95 and 'set dest' on page 101 and 'Optimizing the
print server's services' on page 120.

:i
Ia
I
i
i 84 Ethernet Print Server User's Manual
i
I
 Each destination on the print server also has a model associated with it. The
eight models (one per destination) can be thought of as a series of mini-filter
that can do special processing to the print job data. These processing options
include:
banner page generation,
header string insertion,
trailer string insertion,
n tab expansion (xtab),
e carriage return insertion (onlcr),
e ASCII to Postscript conversion (a2ps),
e print job descrambling.

The default model names are ml to m8 and each comes mapped to a particular
destination. By default, the model settings are raw, that is, they simply pass
data through to the UO port untouched. This provides a clean state to begin
your configuration. Model names can be changed to be something more
meaningful.

The models are not capable of multiple copies and throughput may decrease if
onlcr or a2ps is enabled.
Each model definition includes: name, type, and some of these processing
parameters, if any. '

See also: 'set model' on page 103, 'set model' on page 103 and 'Setting up
special job processing' on page 119.

Setting Inclusions
I
raw I No content sensing. Jobs are assumed to match the printer type, or else the printer does
the autosensing and switching.
a2ps Convert ASCII jobs to Postscript or pass PostScript jobs directly to the printer.

(31 ModelTypes

Internal architecture
Variables
Variables are actually utilized within the print server's models and are useful
for defining lengthy header or trailer strings. This might be necessary for
certain printer switch strings, for example.

Variables are used to make efficient use of the limited space in these header and
trailer strings. Only nine elements can be included in these strings. Each
element can be one of the following:

letter a
code 0x40
variable $FF

Therefore, you could make up a series of variables and specify each of these
(up to nine) in the header or trailer string. Each variable could then contain up
to 14 elements of its own. \-.&

Please see 'Variable definitions' on page 150 for a description of all

pre-defined variables. You can also create your own variables to add to this list.

See also: 'list var' on page 98, 'set var' on page 109, 'list model' on page 97
and 'set model' on page 103.

86 Ethernet Print Server User's Manual

1111

Logpaths
The term logpath comes from the UNIX syslog logging system. With the print
server, each destination can report statistics on: user, page count, job name, and
printer errors. In addition, a checksum calculation can be obtained to confirm
data integrity when a job is sent to the printer.

Logging occurs through a Telnet session to a particular TCP port. A logpath

can also be configured to report statistics via email to a particular user. This can
then be saved to a file if desired. In addition, messages can be logged to
SYSLOGD on a particular TCPDP host.

Each logpath is associated with a particular destination and the eight default
logpath names range from 11 to 18. Logpath names can be changed to be
something more meaningful.

Logpath definitions include: name, log port, and log type.

See also: 'list logpath' on page 96, 'set logpath' on page 102 and 'Capturing
printer feedback' on page 120.

Internal architecture
88 Ethernet Print Sewer User's Manual
 Ethernet Print Server
User's Manual

At this point in the manual, you should have your Ethernet

print server installed and conjigured on the network and at
least one host conjigured to print to it. This section 's
purpose is to give you the basic tools to add to your print
setup by introducing the print server's command set.
 An entire command set, called npsh, allows print server parameter
configuration, display and execution. These commands can be utilized through
one of the following methods:

a Telnet session,
r a remote command (i.e. rsh/rcmd/remsh),
r npconfig (please see Table 2 'npconfig Detailed configuration options
sub-menu' on page 22),
r DOS host software (please see 'Host software' on page 54),
a terminal on the serial port (please see 'Manual configuration through the
serial port' on page 28).

The print server can support up to 256 simultaneous TCP connections and 10
simultaneousTelnet sessions. All npsh commands except lp are available to all
of the above methods. The lp command is available only to rsh/rcmd/remsh
clients. Please refer to Ip in section 8.6.

The print server's parameters can also be manipulated through the FTP
daemon and through SNMP. See 'FTP daemon' on page 131 and 'Managing
with SNMP' on page 127, for more details.

npsh prompt
When npsh is accessed through a Telnet or serial terminal session, a prompt is
displayed after login to indicate that it is ready to accept a command from the
user. The Telnet prompt is formatted ipaddress:userid> where ipaddress is the
IP address of the print server, and userid is the user ID of the currently
logged-in user.

Example: 192.75.11.32:root>
where 192.75.1 1.32 is the print server's IP address and the user is root.
The serial port's login prompt is formatted userid>.
Example: root>
where the user logged into the serial port is root.

90 Ethernet Print Server User's Manual

User accounts and permissions
When you log into the print server, you either log in as a guest or as root user.
The commands you will be able to utilize on the print server depend on which
login name you use. By default, there is one root user and one guest user; users
can then be added to this with either permission level.

Users with root permission can execute all commands; users with guest
permission cannot do any configuration and can only execute commands that
display settings on the print server. However, they can use ping and telnet as
well.

Use list user to look at current settings. As root user, refer to set user to change
these settings.

For a complete command set reference, please see 'npsh command set' on
page 93.

Redirecting output from commands

You can redirect output from any npsh command to any I/0 port with the
redirection character >.

The syntax is: command > ioportname

where command is a "alid npsh command and ioportname can be pltl or plt2.

Example: list tcpip > pltl

sends current network settings to the first parallel port.

Example: chr $FF > pltl

sends a formfeed to PLT1.

Command set
npsh basic commands
Before reading on about the print server's command set, it is important to
understand some of the basic commands involved.

Set commands affect only current settings, not stored settings in EEPROM.

The save command is used after set to save the new settings to EEPROM.

Store commands only affect stored settings in EEPROM but not the current
settings. This means the print server must be reset to make any changes take
effect. For example, if you change the current settings of the IP address and the
netmask, this will only take effect after a reset (warm boot) from EEPROM, or
after a power-on (cold boot).

92 Ethernet Print Sewer User's Manual

- --

Command syntax
The commands in this section are listed alphabetically by title and include all
commands available on the print server.

The command syntax follows the command name, where:

Arguments in italics are user-defined strings.

a Arguments enclosed by brackets [ I are optional.
Arguments separated by the or symbol ( I ) mean that a choice must be made.

An explanation of what the command does and how to use it follows the
syntax. All examples for a particular command are provided at the end of that
command's main section and when another command or other information
may be useful, a reference is given.

cancel
cancel jobid

Delete a job from the print server's internal queue.

See also lpstat.

chr
chr arguments

Used with redirection, the chr command sends output control codes to the
printer. Separate arguments with spaces. Arguments can be a combination of
words, any printable character, or the common set of $BS, $TAB, $ESC,
$DEL, $EOF, $NULL, $FF, $LF, or Oxhh (hexadecimal code for any
character).
Example: chr $LF causes an extra linefeed before the next prompt.
See also: 'Redirecting output from commands' on page 91.

Command set
debug
The debug set of commands display detailed debugging information about
memory, the network interface, and protocols.

debug ipllpqlmemlnetbioslniflnovellltcp

Display debugging information for a particular module.

disable
disable ioportnameldestname

Disable the specified UO port so jobs are queued but not printed or disable the
specified destination so any new jobs are rejected. ioportname is one of the four
VO ports and destname is the name of one of the unit's destinations.

See also: enable, list dest.

enable
enable ioportnameldestname

Enable the specified UO port so jobs queued are printed or enable the specified
destination so new jobs are processed. ioportname is one of the four UO ports
and destname is the name of one of the print server destinations.

See also: disable, list dest.

keycode
keycode escapecharacter

List the hexadecimal value of escape character.

See also: 'telnet' on page 116.

94 Ethernet Print Server User's Manual

List Commands
The list command provides three possibilities:

list choice List current settings.

list default choice List default settings.
II list stored choice List stored settings in EEPROM.

choice can refer to a number of parameters. All possible options are listed
below.

list arp
list arp

List the contents of the print server's arp table.

list date
list date

List the current date.

See also: set date.

list dest
list dest

List current print server destination definitions and their properties including:
name, 110 port, model used, logpath, state, alternate destination, and service(s).

list dest destname

List the specified print server destination's complete current settings. destname
is the desired destination.

See also: 'Destinations' on page 84 and set dest.

Command set
list diff
list diff

List the differences between current settings and EEPROM settings.

list ifc
list ifc

Display all of the Network Interface Tap (NIT) modules' physical properties
such as their interface number and Ethernet address.

See also: store ifc.

list key
list key

List the license details and license key number.

list logins
list logins

List users currently logged into the print server.

See also: 'User accounts and permissions' on page 91 and list user.

list logpath
list logpath

List the current settings of all logpaths.

See also: 'Logpaths' on page 87 and set logpath.

96 Ethernet Print Server User's Manual

list model
list model

List the current processing options for all models.

list model modelname

List the specified print server model's complete current settings. modelname is
the desired model.

See also: 'Models' on page 85 and set model.

--

list pserver
list pserver

List common print server characteristics across all protocols.

See also: store pserver.

list rprinter
list rprinter

List information about the Novel1 RPRINTER configuration. Entry will appear
if the print server has made a connection to the file server.

See also: 'Host configuration' on page 57, set rprinter and debug.

list sysinfo
list sysinfo

List the current print server system information.

This output will not include the descramble key even if you have set one.

See also: set sysinfo, set logpath, ping and telnet.

Command set
list tcpip
list tcpip

List all properties of the TCP stack.

See also: 'Getting ready for complex networks' on page 122 and store tcpip.

list test
list test

List the status of output VO port tests.

See also: start and stop.

list time
list time

List the current time.

See also: set time.

list user
list user [useridlall]

List current settings of a particular user indicated by userid, or all users.

Current settings include user ID and permissions.

See also: 'User accounts and permissions' on page 91, list logins and set user.

list var
list var

List current settings of all variables.

98 Ethernet Print Server User's Manual

load
load

Load the settings stored in EEPROM and use them as the current settings.
These settings include: destinations, models, logpaths, user, TCP, VO ports,
variables, system information, and portmaps. This does not affect network
parameters. Use this after a power failure to restore settings saved in
EEPROM.

load default
Note: Load the factory settings and use them as the current settings. Use this
in combination with store net from default when reinstalling the print servel:

See also: save and store tcpip.

lp options -d destname

Print to the print server using standardTCP1IP rsh/rcmd/remsh. destname is the

name of the print server destination. This command in default mode will show
any printer errors to the user. The options are:

-v Show incremental byte counts as the job is printing and show

the job's position in the queue as it moves to the top.
-V Show number of bytes printed.
-0n1cr Insert a CR character before LF characters.
-ttabwidth Number of spaces for the tab in the range of 1 to 16.
-off Generate a FF character at the end of the job.
-oeof Generate an EOF character at the end of the job.
-uusername The name of the user that will be printed on the banner page.
-ffilename The name of the file that will be printed on the banner page.
Note: lp can only be used with a remote command (i.e. rsh/rcmd/remsh).

Example: rsh spike lp -d dlpltl -off < testtxt

prints the file test.txt, followed by a formfeed to the print server destination
d l pltl on the print server named spike.

Command set
lpstat
lpstat

Display active and queued jobs on the print server and I/O port status.

See also: cancel.

ping
ping ipname

Ping another TCPIIP host on the network indicated by ipname.

ping [-sl ipname [packetsize[count]]

Continually ping another TCPIIP host on the network specified by ipname.

This can be an IP address or an LP name. packetsize is the datagram packet size
which defaults to 64 bytes if no size is included in the syntax. count is the
number of requests to be sent.

Note: To utilize the IP name, the DNS server's IP address must be setjrst so
the print server can resolve the IP name. See set sysinfo for more information.

reset
reset

Restore current settings to those stored in EEPROM. Performs a warm boot or

hardware reset, simulating a power-on reset. Use this after a power failure.

save
save

Save the current settings to EEPROM. These parameters include: system

information, destinations, models, logpaths, variables, I/O ports, and
portmaps. Resetting the unit is not required.

100 Ethernet Print Server User's Manual

save default
This command saves factory settings of all parameters to EEPROM, except the
factory-programmed Ethernet addresses. The changes do not affect the current
operating parameters until the print server is reset.

-
Attention: Save default overwrites e v e ~ t h i n g ,

See also: load, reset, and set commands.

Set Commands
Change the current parameters. The three command possibilities are:

set choice parameters Set some parameters.

set choice from default Set default parameters.
set choice from stored Set stored parameters from EEPROM.

choice and parameters can be any of the following options described below.

Note: Once you have set any parameters, you need to issue a save command to ,
store these new values to EEPROM.

set date
set date year month day

Set the current date. year is four digits, month is from 1 to 12, and day is the
number in the month.

See also: list date.

set dest
set dest destname ioport pltllplt2

Associate a destination with an I10 port so that jobs sent to that destination
appear on the specified port.

Command set
 set dest destname logpath logpathnanze

Associate a logpath with a destination. Please see set logpath to configure this
logpathname.

set dest destname model modelname

Associate a model with a destination. Jobs sent to the named destination are
processed according to the options defined in the named model. Please see set
model to configure this modelname.

set dest destname name newname

Change the current name of a destination to a new name. destname is the

current name and newname is the new name you wish to give the destination.
This newname must be nine characters or less. Otherwise it will be truncated.
In addition, all names are case sensitive.

Note: When you change a destination name, you may have to reconjgure the
host to reject the change.

set dest destname service [[-]socket] [[-Ilpd] [[-Ilpsched] [[-Irprinter]

[[-Ipserver] [[-]appletalk] [[-Inetbios] [[-Iftpd]

Set the destination to handle only certain print server services.

See also: 'Optimizing the print server's services' on page 120.

Example:

set dest dlpltl ioport pltl

See also: 'Destinations' on page 84 and list dest.

set logpath
set logpath logpathname name newname

Rename a set of printer logging options. logpathname is the current name and
newname is the new name you wish to give the logpath. This newname must
be nine characters or less or else it will be truncated. In addition, all names are
case sensitive.

Ethernet Print Server User's Manual

 set logpath logpathname port tcpportlemaillsyslog

Send the printer logging information either to a TCP port number, to a

particular user's email address, or to SYSLOGD on aTCP/IP host. tcpport is a
TCP port in the range 1,024 to 65,000.

If the email or syslog option is selected, please see set sysinfo for setting up IP
addresses to send to.

set logpath logpathname type Gob] [user] [pgcnt]

[cksum] [printer] [ioport]

Establish the type of printer logging. These types can be combined by placing
a space between each entry:

job Contents of job log.

user Usemame of print job.
Went Number of pages each job uses. Needs bi-directional
communication. Not completely secure from user
manipulation.
cksum 16-bit checksum value to confirm integrity of data printed.
printer Printer errors are logged. The type of errors is dependant on the
particular printer's reporting abilities. Needs bi-directional
communication.
ioport Monitors printer error and out-of-paper messages through the
port.

See also: 'Logpaths' on page 87, list dest, list logpath and 'Capturing printer
feedback' on page 120.

set model
set model modelname banner [psltextlauto] [after]

Indicate if destinations using modelname are to send a banner page. If a banner

page is to be sent, indicate the type according to the printer attached.
Specifying after will print a trailing banner at the end of the job.

Note: The banner type and the printer type must match.

set model modelname stty [[-Ionlcr] [[-Idescramble] [xtab <I - 16>lnone]

Command set 103

 Control extra job processing done by the model specified by modelname:

onlcr Indicate whether or not isolated linefeed characters should be

converted to CR LF (camage return - linefeed) pairs. Turn this
on when lines stair-step down the page, starting a new line
without returning to the original line beginning.

Note: onlcr may slow throughput perj4ormance on the unit.

descramble Set the model to automatically descramble any print jobs

passing through. These jobs must pass through the scrambling
filter, npscramble, on aTCP/IP host first. If they do not, the jobs
will pass through as is.

Note: To set thisfeature on, you must configure the descramble key first. Please
see set sysinfofor more on this requirement and for further details, please see
Host software and Scrambling/Descrambling.

xtab Sets the tabstop width within the range of 1 to 16.

set model modelname header headerstring

Set the header string for a named model. The header precedes every job that
goes to a destination using the named model. headerstring is a string with a
maximum of nine elements; each element may include a letter, code (e.g.
0x04), or variable (e.g. $FF).

set model modelname name newname

Change the name of a model to a new name. modelname is the current name
of the model and newname is the new name you wish to give the model. This
newname must be nine characters or less. Otherwise it will be truncated. I r
addition, all names are case sensitive.

set model modelname trailer trailerstring

Set the trailer contents for a named model. The trailer is appended to the end
of every job that goes to any destination associated with the named model.
trailerstring is a string with a maximum of nine elements; each element may
include a letter, code (e.g. 0x04), or variable (e.g. $IT).

set model modelname type a2ps [pageorient[pagesize[rowslwidth]]]

[cont]

104 Ethernet Print Server User's Manual

Convert text jobs from ASCII to Postscript before sending them to the printer.
PostScript jobs are not processed, but passed on without conversion. The a2ps
default settings are portrait, letter, 60 rows, and 80 columns.

pageorient Direction of page: portrait I landscape.

pagesize Size of page: letter I legal I exec I a4.
rows Number of rows in page.
width Number of characters per line.
cont Continuously senses print job for data format. For example, if
there is a Postscript banner page in front of a printjob, the print
server will sense both parts of the job separately and do the
conversion. Enabling this feature will decrease output
performance.

set model modelname type pcl-ps [pclswvarpsswvar]

Switch printer modes if the printer is not capable of doing this on its own but
is capable of printing both plot files and PostScript jobs. To do this, the model
appends a header and trailer string to each job switching the printer to and from
the appropriate mode. The switch strings must be provided to tell the printer
how to change between plot file and Postscript modes.

If no parameters are specified, the model defaults to the switching strings for ,
an OcC printer. pclswvar is the switching string to change modes to plot file and
psswvar is the switching string to change modes to PostScript.

See set var to set a new variable with a particular switch string or Variable
Definitions for the pre-defined switching variables.

set model modelname type raw

Set the model specified to no sensing and no conversion. In this mode, there is
no ASCII to Postscript processing and no switching strings appended to the
jobs.

Examples: set model m4 header $ESC \&k2

sets the header string of the model m4 with five elements. Invokes CR
insertion.

Command set
 Note: When inputting a or a "& " and you 're using RSHD to execute this
'I$"

command, you must place a '2"beforehand so the local shell interpretor

doesn P parse it out.

See also: 'Models' on page 85 and list model.

set rprinter
set rprinter add pservername printernumber destname

Initiate aconnection to a Novell PSERVER so that the print server can act as a
remote printer. A non-print server PSERVER must be pre-configured to
recognize a remote printer.

pservername Name of the PSERVER to connect to.

printernumberNumber of the printcr as defined in the PSERVER display.
destname Destination name on the print server.

set rprinter del pservername printernumber

Disable a remote printer connection.

See also: 'Host configuration' on page 57 and list rprinter.

set sysinfo
set sysinfo contact [contactstring]

Set a person to contact in case of system trouble. If contactstring is not

included in the syntax, the field is emptied.

set sysinfo descramblekey key

Set the key value used for descrambling print jobs from TCPIIP hosts. This key
is a four digit hexadecimal value obtained from the host software, npscramble.
Within the npscramb1e.c source code, there is a variable called SR-KEY
which contains the default key value. This can be changed to any four digit hex
value you'd like.

Note: Ifyou change the key value in npscramble.~, you must recompile the
source code and then use this key in the set sysinfo command.

106 Ethernet Print Server User's Manual

set sysinfo dns ipaddress

Set the DNS server's IP address so the print server can resolve names used with
ping and telnet. Please see ping or telnet.

set sysinfo email emailname@ipaddress

Set the user's email address to receive printer logging information. emailname
is the IP name of the user to send mail to. ipaddress is the IP address where the
mail is stored. See also set logpath to set printer logging to email.

set sysinfo location [locationstring]

Set the physical location of the print server. If the locationstring is not included
in the syntax, the field is emptied.

set sysinfo loginfo [sys] [tcp] [ipx] [spx]

Select the print server debugging information type. Usually this information
includes unexpected errors or exceptions from the unit and can be broken down
into:
SYS General system messages.
tcp TCP stack messages.
ipx IPX stack messages.
SPX SPX stack messages.
Note: This debugging information is from the print server only, not from the
printer: See set logpath and Capturing printer feedback for details on
acquiring printer logging.

set sysinfo logport syslog

The print server debugging information goes back to SYSLOGD on aTCP/IP

host. If the syslog option is selected, you must set the IP address of the host to
which it will send the details.

set sysinfo module [novell] [appletalk]

Set the print server to handle particular protocol modules.

See also: Manipulating the print server's services.

set sysinfo name [namestring]

Command set
 Set the name of the print server. This is just a string and is not used in the
operation of the unit. If namestring is not included in the syntax, the field is
emptied.

set sysinfo syslog ipaddress

Set the IP address of the host which will receive debugging information from
the unit and printer logging through SYSLOGD. Please see the earlier set
sysinfo commands and set logpath for further syslog configuration.

Examples: set sysinfo descramblekey ABCD

sets the descramble key to match the value found in npscramb1e.c.

set sysinfo email [email protected]

sets fred as the user to receive printer logging as long as the logport is set to
email. This printer logging just includes job information.

See also: list sysinfo.

set time
set time hour minute [second]

Set the current time. hour is based on the 24 hour system, minute and second
are from 0 to 59.

See also: list time.

--

set user
set user addldelete userid

Define a new user or delete a current one. userid is the user's login ID.

Ethernet Print Server User's Manual

 Caution:Any user can be deleted so be careful using this command. You
might delete all the root user types. If this happens, conjiguration
capability is no longer available through any of the normal methods.
Instead, you must set the unit back to defaults with the jumper settings.
Please see Restoring to factory defaults.

set user passwd userid [password

Set a password for a specific user. userid is the user's login ID. password is the
desired password for this user. password must be less than eleven characters
and if it is not included in the syntax, the user's password is cleared.

If you forget the root password, you can use a TCP/IP host and RSHD as
superuser to set the users back to factory defaults (set user from default) or you
can use the jumper method mentioned in Restoring to factory defaults.

set user type userid rootlguest

Set a user with guest or root permissions. userid is the user's login ID.

See also: list user, list logins and 'User accounts and permissions' on page 91.

set var
set var varname string

Create a named variable with a specific string. string is a space-separated list

of words, hex numbers (e.g. 0x04), and references to other variables or
constants.

Note: When inputting a "$" or a "& " and you're using RSHD to execute this
command, you must place a '1"beforehand so the local shell interpretor
doesn't parse it out.

See also: 'Variables' on page 86, 'Variable definitions' on page 150 and 'list
var' on page 98.

start
start foxlttslloopb [pltllplt2]

Command set
 Start an ASCII output test on the specified U 0 port. If no U 0 port is specified,
the command affects all of them.

These tests are for confirming that the print server is communicating properly
with connected devices. Three different types of tests can be done:

1 fox message test.

A continuous stream of text is sent to the output U 0 port as follows:

1 The quick brown fox jumps over the slow lazy dog's back 1234567890 :! @#$&0.
2 The quick brown fox jumps over the slow lazy dog's back 1234567890 :!@#$&0.
3 The quick brown fox jumps over the slow lazy dog's back 1234567890 :! @#$&O.
4 The quick brown fox jumps over the slow lazy dog's back 1234567890 :!@#$&0.

When the line counter reaches 99, it is reset to 0.

2 tts message test.

A continuous stream of Gandalf 4OOC 'ITS compatible text is sent to the output
UO port as follows:

!
THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG 1234567890 DE
THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG 1234567890 DE
THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG 1234567890 DE
THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG 1234567890 DE

,
3 loopback test.
Any input characters from the device attached to the output U O port are echoed
back as output characters.

See also: stop and list test.

I

stop
stop alllpltllplt2

Stop an output test on the specified U 0 port(s).

I

I
See also: start and list test.
Store Commands
Change critical parameters such as network, 110 port, and protocol settings.
The three command possibilities are:

store choiceparametersStore some values.

store choice from defaultstore default settings.
store choice from currentstore current settings.

choice and parameters can be any of the options listed below.

Note: Once you store any parameters, you need to switch the printer OFF/ON
to reboot the print serve4 to apply the changes. Otherwise, you will still be
using the current settings.

For the store commands, these new words are important to know:

ifnum Interface number. An index to a Network Interface Tap (NIT).

ifnum will always be 1 since there is only one network
interface, Ethernet.
NIT Network Interface Tap. A module that serves as a generic
interface between the data link protocol layer (i.e. Ethernet )
and higher network protocol layers. Each NIT is indexed by an
interface number (ifnum).
papname Printer Access Protocol (PAP) name. An AppleTalk name for
each printer defined on the host. Makes up the second half of
the name listed in the Chooser and is transparently mapped to
an print server destination. There can be a maximum of four
printers which can point to any one of eight destinations on the
print server.
Note: Although the system has four ports (at installation time you will see
four), only thejrst two ports ure available.

store ifc
store ifc ifnum utp [[-]li] [[-]rx]

Modify the NIT module's physical UTP interface properties where li enables
link integrity and rx enables the increased receive threshold.

Command set
 A "-" before either disables this feature. ifnum will always be 1 for the print
server since there is only one network interface, Ethernet.
See also: list ifc.

store pserver
I store pserver name newservername
I
i Store a new name for the print server indicated by newservername. This name
a will affect Novell, AppleTalk, and NetBIOS setups.
i
I
store pserver apple zone [zonename]
i
Store a particularAppleTalk zone on the unit. To clear the AppleTalk zone, type
store pserver apple zone and press enter.

s store pserver applepap papname dest destname

Alter the AppleTalk printer specified by papname to print to the destination

indicated by destname. This name does not appear in the Chooser.

store pserver applepap papname driver chooser-driver

Change the AppleTalk printer specified by papname to use the printer driver
name specified by chooser-driver. This driver is selected in the Chooser menu.

store pserver applepap papname name newpapname

Change the AppleTalk printer name that appears in the Chooser. papname
makes up the second half of the name and is transparently mapped to an print
server destination.

Example: store pserver applepap pltl name oce

changes the AppleTalk printer named plt 1 to oce.

See also: list pserver.

store pserver opts [[-]jobsecurity1

Allows users to cancel print jobs on the unit without having to be root users.
Disabling jobsecurity allows all users to issue the cancel command.

1 112 Ethernet Print Server User's Manual

i
3
store pserver novell frametype [ethernet2 1 802.3 1 802.2 I 802.2snapl

Store a particular frame type for the print server to adhere to in a Novell
environment. No parameter means it will automatically sense and
simultaneously support all Novell frame types upon bootup.

store pserver novell fserver add fservername

Adds a specified Novell file server as a preferred file server. This feature is
useful in a large Novell network so that the print server does not ignore
important file servers. If this feature is not enabled, the print server will only
acknowledge the first 16 file servers it senses.

store pserver novell fserver del fservername

Deletes a particular Novell file server from the print server's list of preferred
file servers.

store pserver novell opts [[-Ispxkeepalive]

Allows users to disable the keepalive packets sent by the print server to the host
in order to maintain an SPX connection. The [-I disables spxkeepalive.

store pserver novell passwd Ipassword

Store the password for the print server to use when logging in to the file server.
This password must match the password set in PCONSOLE.

store pserver novell polltime [time]

Store the time (in seconds) between polling by the unit to see if print jobs are
in the queue on the file server. This is applicable to a PSERVER setup only.

Command set
store tcpip
store tcpip lfnum addr ipaddress

Store the ipaddress for the NIT module specified by ifnum.

ifnum will always be 1 for the print server since there is only one network
interface, Ethernet1

store tcpip ijnum frametype [ethernet21 [802.2snapl

Control the frame type(s) used by the NIT module specified by ifnum.

store tcpip ifnum mask netmask

Store the netmask for the NIT module specified by ifnum.

store tcpip lfnum opts [[-Irarp] [[-Ibootp]

Enable or disable the RARP and BOOTP for the NIT module specified by
ifnum

store tcpip route addldel default routeripaddress ifnum

store tcpip opts [-]gateway

Enables the gateway (IP routing) functions of the print server. By default, the
gateway is disabled. This command must be used in conjuction with the store
tcpip proxy command below.

store tcpip proxy add [hostlnet] targetipaddress [ltargetnetmask]

Enables the print server to respond to arp requests for IP addresses that are
different than the interface configuration of the print server.

store tcpip proxy del targetipaddress

Removes this entry from the proxy arp table.

store tcpip route addldel default routeripaddress ifnum

Add or delete a default router entry in the print server's routing table for the
NIT module specified by ifnum.

114 Ethernet Print Server User's Manual

 store tcpip route add [hostlnet] targetipaddress[ltargetnetmask]
routeripaddress &urn [metric]

Add a specific route to the print server's routing table.

Example: store tcpip route add 192.75.30.11 192.75.30.3 1

stores a host with IP address 192.75.30.11 into the unit's routing table for the
first NIT module. The router's IP address is 192.75.30.3.

store tcpip route addldel default routeripaddress rfium

Add or delete a default router entry in the print server's routing table.

store tcpip route del [hostlnet] targetipaddress rfnum

Delete a specific route from the routing table of the NIT module specified by
ifnum.

store tcpip tcp access [root] addldel ipaddress [lnetmask]

Add or delete a host or network in the TCP connection access list. An empty
list allows any host to have TCP sessions with the print server.

Example: store tcpip tcp access root add 192.75.30.11

Provides the host with IP address 192.75.30.1 1 root access to the print server.

store tcpip tcp opts [-]keepalive

Enable or disable the keepalive packet usage in the TCP stack.

store tcpip tcp rxwin packetsize

Modify the receive window size property for TCP connections. packetsize is
the number of full size packets and must be in the range 1 to 8. The higher the
number, the fewer simultaneous TCP connections.

See also: list tcpip.

supervisor
supervisor

Command set
 Gives you root permissions when utilizing the Novel1 host software, npsh*exe,
to start a full session with the print server.

See also: 'Host software' on page 54 and 'User accounts and permissions' on
page 91.

telnet
telnet ipname [escapecharacter Iportnumber]]

Telnet from the print server to another host on the network specified by its
ipname. ipname can be either an IP address or an IP name. By specifying a
TCPportnumber, you can also connect to a specific socket on the target host.

If escapecharacter is used, it resets the key sequence used to exit to command

mode indicated by the telnet> prompt.

In this mode, you can execute:

quit Exit the Telnet session.

? Print the help information.

By default, Ctrl-] is the escapecharacter. To reset this value, please see

'keycode' on page 94, which will give you the hexadecimal representation of
the escapecharacter you want to use which can be substituted into this telnet
command.

Note: To utilize IP name, the DNS sewer S IP address must be setjrst SO the
unit can resolve the IP name. See set 'set sysinfo'on page 106 for more
information.

116 Ethernet Print Sewer User's Manual

 Ethernet Print Server
User 5. Manual

As of now, you will have conjigured your print sewer and

you're probably printing to it successfully. The purpose of
this chapter is to enhance your print setup by describing
some of the additional features that the print server
provides. It is broken down into the following six sections,
as described next page.
 1 General Options: network security, changing the print server's name,
manipulating the UTP interface, setting up special job processing, optimizing
ing the unit's services, capturing printer feedback, and controlling frame types.

2 TCPIIP Options: restoring to factory defaults, getting ready for complex

networks, remotely managing the unit, TCP/IP network security.

3 Novell Options: setting password security and setting preferred file servers.

4 Managing with SNMP: custom MIBs and traps, SNMP security, and SNMP
procedures.

5 FTP Daemon: FI'P file system, printing using FTP, monitoring using FTP, and
configuring parameters using FTP.

6 IP Routing: the unit's IP routing features.

118 Ethernet Print Server User's Manual

General options

Network security
The print server provides various built-in security methods to protect its
configuration. These include passwords and permission levels.

In addition, TCP/IP and Novell environments each have further security

measures. Refer to Maintaining network security and Setting password
security for more information.

Setting passwords and assigning a permission level to users eliminates the

possibility of any unwanted users from getting into the print server's command
set and manipulating the current settings. To configure passwords and to learn
more about the two different permission levels provided for users, please see
'set user' on page 108 and 'User accounts and permissions' on page 9 1. To
view the current user settings, see 'list user' on page 98.

Using different naming schemes

By default, the print server is named 0-xxxxxx where xxxxxx is the last six
digits of the Ethernet address as found on a sticker on the board. This name
affects a Novell, AppleTalk, and NetBIOS setup. To change this name to
something more suitable for your printing environment, please see 'store
pserver' on page 1 12.

Caution: If you decide to reconfigure the default name and you are using a
CONFIGJile to set print server parameters with your Novell setup, you
must remember to rename the directory containing thisjle.

Setting up special job processing

Printing with the print server adds a lot of extra job processing options to your
current print setup. No matter the environment, you now have the choice of
several helpful features including:

ASCII to Postscript conversion (a2ps),

Options
 E camage return insertion (onlcr),
tab expansion (xtab),
m banner page generation,
m printer mode switching and general printer manipulation.

You can set each feature on the host within an interface file, nprbsdif or
nprsysvif, or on the print server itself. The choice is completely up to you.
Automatically you are given the choice between eight different destinations on
the print server allowing for eight different possible print setups; each of these
print setups is defined by the extra processing specified by it's associated
model. It is the model that defines most of these extra processing options.

TOmake use of these special job processing features, please read over the
appropriate host configuration section or the full list of extra job processing
options documented in 'set model' on page 103.

Optimizing the print server's services

The print server has many features; however, the more features used, the more
memory it requires.

If you are not utilizing all of the protocols provided on the print server, you can
disable the unused ones providing more memory for the protocol(s) in use.
Please see 'set sysinfo module [novell] [appletalk]' on page 118 for the
command details.
In addition to disabling certain modules, you can also disable destination
services. Not every destination on the print server needs to have the same
features and in the case of an AppleTalk setup, you probably don't want every
destination appearing in the Chooser. Please see 'set dest' on page 101 and
'Removing excess printers from the chooser' on page 71 for further details.

Capturing printer feedback

One of the key aspects of maintaining a computing environment is monitoring
printer status and logging this information to useful places. The print server
allows just that through logpaths. In addition, the print sewer's Ip command
provides printer status and job information as a user sends a job.

Logpath method The easiest and most reliable method is to utilize the many
logpath options available on the print server. These include logging printer
feedback to:

120 Ethernet Print Sewer User's Manual

 E a particular user's email address through SMTP,
SYSLOGD on a particular TCP/IP host,
a TCP port number in the range of 1,024 to 65,000 to which you can telnet,

To configure any of these logpath options, please see 'set logpath' on page 102.

Note: SYSLOGD can be used to capture print server debugging information as

well as printer logging. See 'set sysinfo'on page I06 for more details.

Lp method

The print server provides its own version of the Ip print command. This is used
in conjunction with rsh/rcmd/remsh within an interface script or directly from
the command line on the host. By default, it provides printer status andcan also
be configured to report incremental byte counts as the job prints. It can also
show the job position in the print server's queue as it moves to the top.

Note: Using lp will provide printer error messages as well as job status.

If Ip is used from the command line, any printer status will come right back to
the screen. If used within an interface script, the messages will go to the log
file located in the spooling directory.

Since lp must be used with rsh/rcmd/remsh only, this feature is only offered
with a print setup utilizing an interface script or with a rsh/rcmd/remsh
command from the command line on the host.

Please see 'lp' on page 99 and 'rsh/rcmd/remsh' on page 3 1 for further details.

Controlling the frame types used

Various frame types can be used by the print server at any given time but each
supported protocol's frame type configuration is completely separate from
another protocol's. This frame type support is configurable.

Novell and TCP/IP are really the only protocols that offer this configuration.
The print server provides simultaneous support of multiple Novell frame types.
Please see 'store pserver' on page 112 and 'store tcpip' on page 114 to find out
which frame types are offered in each environment.

Options
Restoring to factory defaults
Occasionally, it is necessary to set the print server's network parameters back
to factory defaults whether it be because you are moving the print server, you
are changing your addressing schemes, or you just want to start from scratch.
These network parameters include: IP address, netmask, and routing table
entries.

This is done through issuing a command on the print server and the switching
the printer OFFION to reset the print server to all the network settings it came
with originally.

Through npsh

To restore the network default settings through the print server's command set:

1 Use a Telnet session or connect a terminal to the serial port of the print server.
2 Once logged in as a root user, restore factory defaults by entering:
store tcpip from default
3 Switch the printer OFFION to reboot the print server and then reconfigure its
settings according to one of the methods discussed in Print server
configuration.

Getting ready for complex networks

The default settings on the print server allow printing in a simple network
without routers. You need to add routing information to communicate or print
from hosts on other networks.

To do this, you can establish either of the following:

default routes for generic or unknown network addresses to use,

static routes to known network addresses such as a particular host or
network.

To set a default router or a static route, please see 'store tcpip' on page 114 and
to look at the current routing entries, please see 'list tcpip' on page 98.

122 Ethernet Print Server User's Manual

Remotely managing the print server
In a TCP/IP environment, various methods are available for remotely
monitoring the print server. These include:

0 through a Telnet session,

using rsh/rcmd/remsh and a command from the unit's command set,
using npconfig's Detailed Configuration Options Sub-Menu,
using the FTP daemon
through an SNMP manager.

Options
Maintaining network security
Besides the general security measures mentioned in 'Network security' on
page 119, the print server provides two more for TCPiIP environments. These
include:

a TCP access list,

scrambling/descrambling of print jobs.

Access list

The TCP access list is another method to protect the print server and its
configuration while the scrambling protects your print data from being viewed
by others as it passes over the network to the print server.

The print server has the ability tocontrol host access to printer destinations and
remote command execution services. This is done using an access list, similar
in function to the UNIX .rhosts file. If the access list is empty, any host cdn
have access to the print server's services. If there are entries in the access list,
only those hosts specified have access to these services. Although the
maximum number of entries is 10, each entry can refer to a network or a host
so more than 10 machines can be enabled.

Note: Only users that have root permission can conjigure the remote host
access entries. Users with guest permission can only display these entries.

To set up the access list, please see 'store tcpip' on page 114 and to look at the
current settings, see 'list tcpip' on page 98.

A second method of security is provided through data scrambling and

descrambling. This second TCPiIP security method protects users' print data
as it is sent across the network to the print server for printing. A binary is
provided on the host, npscramble, which scrambles the print job. Then when
it reaches the print server, it is descrambled for printing.

Note: This scrambling method will protect against casual viewing with
network analyzers. However: it is not encrypted and cannot be considered safe
from cryptographic attack.

Ethernet Print Server User's Manual

 To utilize this feature, you need to:

1 Look into the npscramb1e.c source code for a variable called SR-KEY. This
contains a four digit hexadecimal value to be used as the descrambling key on
the print server.
2 Log into the print server as root user and set this value as the key.
Enter: set sysinfo descramblekey key

3 Set descrambling on in the model you are utilizing.

Enter: set model modelname stty descramble

4 Save these new settings.

Enter: save

5 Incorporate npscramble into your print setup on your host. Scrambling can be
set within npcif or added to the command line when printing.

Example: cat test.txt I npscramble I rsh spike Ip -d dlpltl

where test.txt is piped through npscramble for scrambling and then sent for
printing on the print server spike's destination dlpltl.

Please see 'Host software' on page 20, 'Printing via the spooler' on page 32,
and 'set model' on page 103.

Using the terminal port

1 Physically attach the terminal to the serial port on the print server.
2 Press the <Break> key. The prompt will appear.
3 Login to the host.

Options
Setting password security
Besides the general security measures mentioned in 'Network security' on
page 119, a Novell setup provides further password security. A password can
be set on the print server and within your PCONSOLE setup so that when the
print server tries to login to the file server, the passwords are compared.

To configure a PSERVER setup with password protection:

1 Establish a password on the print server.

(Refer to 'store pserver' on page 1 12).
2 Switch the printer OFFION to reboot the print server and make the password
take affect.
3 Enter PCONSOLE as supervisor on your Novell host.
4 Select print server INFORMATION from the Main Menu.
5 Select the appropriate print server and press <Enten.
6 Select CHANGE PASSWORD.
7 At the prompts, type and retype the new password used on this print server
PSERVER. Press <Enten when you are finished.

Note: These steps may vary for NetWare 4 environments.

Setting preferred file servers

The print server allows you to specify a list of preferred file servers in a Novell
environment. This feature is useful in a large Novell network so that the print
server does not ignore important file servers. If this feature is not enabled, the
print server will only acknowledge the first 16 file servers it senses.

To add a preferred file server:

1 Login to the print server through an npsh session as a root user.

2 At the npsh prompt,
enter: store pserver novel1 fserver addfservername
wherefsewername is the name of the Novell file server you want to add as a
preferred file server.
3 Repeat steps 1 and 2 to add additional preferred file servers.

126 Ethernet Print Sewer User's Manual

 anaging wi
SNMP (Simple Network Management Protocol) is a protocol for internetwork
management services. This protocol provides a means for computers (or
agents) to be managed remotely by managers. The level of management
depends on the manager and agent and can go from providing information such
as statistics to providing full management capabilities of the agent.

MIB (Management Information Base) files are a description of managed

objects available in an agent. MIB files provide the data for the manager so
they can remotely manage the agent. A MIB file is simply a formal description
of the way an agent can be accessed using SNMP and what functions can be
managed.

The print server is a fully manageable SNMP agent that supports MIB-I1 ( to
monitor protocol, network, and routing statistics), custom MIBs and traps.

Custom MIBs and traps

The print server provides a custom MIB definition file which consists of 150
variables and three traps. This MIB file allows you to monitor and configure
the print server directly. In fact, the MIB file represents all of the possible
configuration options such as destination settings, network configurations,
print queue status, loading of defaults, etc.

The print server's custom MIB definition file is included on the host software
disk in a file called oce.mib.

Custom MIB variables

The variables found within the custom MIB definition file describe every type
of internal information that can be accessed on the print server by an SNMP
manager. These variables can be divided into two group: system variables and
product variables.

Options
System variables
The first grouping of variables contains general information about the print
server such as firmware version, serial number, etc. In addition to these, it
includes a trap table which defines what SNMP managers will receive the traps
generated by the print server. The trap table can have up to ten entries, but only
the first entry is saved to EEPROM.

Product variables
The second grouping of variables contains information defining all of the
remaining functionality of the print server. The product variables are divided
into:

config group All configuration components such as models,

destinations, logpaths, and users.
status group All dynamic monitoring components such as print
queues, user logins, and RPRINTER configurations.
command group This includes the commands save, load, and reset.

Note: These variables can have read, write, or read-write permissions. Along
with these permissions there are other elements that can limit the write access
to these variables. Please see SNMP security, below, and 'User accounts and
permissions' on page 91 for more information.

Custom MIB traps

A trap is an event generated by an agent to indicate a significant event to the
manager. The print server continuously generates three traps:

coldstart A generic trap generated every time the print server

is powered on or reset
authenticatioailure A generic trap generated whenever a disallowed
access is attempted
IpqIOStatusChanged The only custom trap. This trap is generated
whenever an YO port's status changes.

Ethernet Print Server User's Manual

SNMP security
SNMP does not include any formal type of security definition. However,
security can be accomplished using communities. A community is a string that
is sent with every SNMP request and is used to define a certain view of the
MIB. By doing this, you can control what parts of the MIB are accessed by
SNMP managers.

To access the print server's custom MIB, the public community string can be
used to read any variable that have read access. To restrict write access, there
is an additional security step implemented. This involves defining a user named
snmp on the print server with root privileges. The password defined for this
snmp user will then be used as the community string which allows write access.

If no snmp user is defined with root privileges, no write requests will be

accepted by the print server.

Adding an SNMP user

To add a user named snmp with root privileges, please follow the steps below:

1 Login to the print server as a root user.

2 Add a user named snmp.
set user add snmp
3 Set the user type to root.
set user type snmp root
4 Set the password for the snmp user.
set user passwd snmp snmppassword
5 Save the changes.
save
The user snmp is now created and snmppassword is the only community string
which will allow write access.

Setting the print server to send traps to an SNMP manager

The print server continuously generates traps but unless the trap table is filled
in, no SNMP manager will receive this information. To set the print server to
send traps to a particular SNMP manager, please follow the steps below:

Options 129
 Note: This example assumes that the snmp password has been dejned as
custommib, that the print sewer's ipname is spike, and that the SNMPmanager
is the Trickletspackage.

1 Set up a snmp user with root privileges on the print server, as explained in
'Adding an SNMP user' on page 129.
2 Set the following print server trap variables using your SNMP manager. The
actual syntax of the commands will depend on the particular SNMP manager
you are using.
echo "trapCommunity[l]=\"building-A\"" I snmp-set spike custmmib
where building-A is the string that you want the print server to send with the
trap information. This community string has a 14 character maximum.
echo "trapDest[1]=192.75.11.11" 1 snmp-set spike custommib
where 192.75.11.1 1 is the IP address of your SNMP manager
Note: To disable the entry in the trap table, set the IP address to 0.0.0.0

The print server will now send trap information with the community string
building-A to the SNMP manager with the IP address 192.75.11.1 1. For more
information on these trap variables, please see their description in the custom
MIB definition file.

Note: The trap table can hold up to ten entries but only thejrst entry is storrd
in EEPROM. Ifyou turn the printer 08you will lose the additional entries.

Compiling and monitoring the custom MIB

For read-only SNMP functionality, please follow the steps below:
1 Copy the print server MIB definition file from the host software disk in a file
called oce.mib.
2 Compile this MIB description file to work with your SNMP manager.
3 Using your SNMP manager, view the particular MIB variables that you wish
to monitor.
If you are using Castle Rock Computing's SNMPc package, you will need to
rename the MIB variable UInteger32 to another name such as U32.

130 Ethernet Print Sewer User's Manual

 The FlT daemon provides an additional method to access the print server.
Using the FTP daemon, users are able to submit print jobs, cancel print jobs,
monitor the print queue, and upload/download print server configuration files.
Users FTP to the print server as if it were any other computer on the network.

For the purposes of FI'P, a pseudo file system has been defined on the print
server to allow access to the unit's functions. Three types of users can access
this file system: root, guest, and anonymous. Root and guest correspond to the
entries in the print server's user list; anonymous is a special type that does not
require a password. For each directory or file within this file system, there are
access restrictions according to the type of user logged in.

Print server EiTP file system

The print server FTP file system is where you execute all ftp commands on the
unit. Please see the examples on the following pages for a complete description
of the commands and how they are executed.

The following is the structure of the file system you will see when you ftp to
the unit:

/queue Contains files with information pertaining to the print queue

associated with each of the print server's ports (i.e. pltllplt2).
These files allow you to view the current status of each queue.
Idest Contains eight subdirectories, one for each of the eight print
destination on the print server. Please see 'Destinations' on
page 84 to better understand destinations and printing. These
directories are where files are put in order to print.
/jobs Contains files representing all the print jobs currently queued.
The only command available for these files is del, which
cancels the job.
Iconfig Contains three subdirectories: current, stored, and default.
Each of the files in these subdirectory represents one data
structure of the print server. The files in the current directory
reflect the current configuration, files in the stored directory
ref ect the stored configuration, and files in the default directory

Options
 reflect the default configuration.These files are in binary
format.
/exec This directory is used as a command interpreter directory. Any
file with print server configurationcommands that is put to this
directory will be interpreted as a series of npsh commands.

Printing a file using FTP

The following example shows how to print a file using FTP:

1 Change to the local directory where the file to print resides.

2 Login to the print server using ftp.
ftp ipname
3 Login as guest, root, or anonymous.
Note: Guest and root users require the use of passwords as conjgured in the
unit5 user list. Anonymous is a special login that does not require a password.
4 Change to the /dest directory that you want to print to.
cd destldestinationname
5 Change the mode to correspond to the type of file to be printed. Choose binary
mode if the file to be printed contains both text and graphics and ASCII mode
if the file is text only. The default mode is ASCII.
bin
6 Copy the file you want to print to this directory.
put$lename
The file is spooled and printed.

7 Logout of the FP session.

quit

Removing a print job using FTP

The following example shows how to remove a print job using FTP:

1 Login to the print server using ftp.

ftp ipname
2 Login as guest, root or anonymous.
3 Change to the /jobs directory
cd jobs
4 Display a list of current print jobs.

132 Ethernet Print Server User's Manual

 Is
Displays listing of all queued print jobs by their ID number.

5 Remove desired print job from the list.

del jobname
6 Logout of the FTP session.
quit

Monitoring a print queue using FTP

The following example shows how to monitor a print queue using FTP:

1 Login to the print server using ftp.

ftp ipname
2 Login as guest, root or anonymous.
3 Change to the /queue directory
cd queue
4 Turn interactive mode off.
prompt
This enables you to copy a number of files without having to respond to
prompts by the print server.

5 Download all files in the print queue directory.

mget *
Files pltl and plt2 are downloaded to the users local directory.

6 Logout of the FTP session.

quit
7 View file with information pertaining to print queue status.
cat pltl plt2
Note: This command gives you the same information as a lpstat in npsh. cat is
a UNIX command; with DOS, use the type command.

Options
Configuring print server parameters using FTP
Users have two ways of configuring the print server's parameters using FTPD.
The first is by uploading binary files to the Iconfig directory and the second is
by uploading text configuration files to the /exec directory. We discuss each
method and give appropriate examples below.
1. lconfig directory The lconfig directory is divided into three subdirectories;
current, stored, and default. Each of the files in these sub-directories represent
one data structure regarding the configuration of the unit. These files can be
used to make a backup copy of the unit's configuration parameters or to copy
configuration parameters from one unit to another.

Note: The configurationfiles are in binary form and their format may differ
betweenfirmware versions. Users may not be able to upload a conjiguration
file that was downloaded from a previous version.
Copying a configuration using FTP

The following example shows how to copy a configuration file using FTP:

1 Login to the print server using ftp.

ftp ipname
2 Login as root.
You must be a root user in order to copy a configuration.file.
3 Change to the configlstored directory.
cd config/stored
4 Set mode to binary.
bin
5 Turn off the interactive mode.
prompt
6 Download all the files in this directory.
mget *
A copy of all files in the configlstored directory is downloaded to the user's
local directory on their host.
7 Logout of the FTP session.
quit
Now you have a copy of the print server's stored configuration parameters.
These files can be saved for archival purposes, used to reconfigure the unit to
a previous setting, or used to set a number of units to the same configuration.
Note: It is only necessary to save the files from the stored directory. Files from
the default and current directory are not required in order to restore a unit's
configuration.

Ethernet Print Server User's Manual

Restoring a configuration using FTP
FTP can be used to restore a configuration saved from the unit or restore a
configuration saved from another unit.

Note: Ifyou are restoring a configuration saved from another unit, the
conjguration must be of the same version as the unit receiving the
configuration.

1 Change to the local directory on the host where the saved configuration files
reside.
2 Login to the print server using ftp.
ftp ipname
3 Login as root.
You must be a root user in order to FTP files to the lconfig directory.
4 Change to the configlstored directory.
cd configJstored
5 Set mode to binary. Configuration files are always in binary form.
bin
6 Turn off the interactive mode.
prompt
7 Upload all the files from the user's local directory.
put *
All files are copied from the local directory to the configlstored directory.

8 Logout of the FTP session.

quit
Note: It will be necessary to reset the print serverfor the changes to take effect.

Options
2. lexec directory Using the /exec directory, users can upload a text file that
includes a number of configuration commands. When this file is placed in the
/exec directory, the commands contained in it are executed as if they were
commands entered sequentially from a telnet session using npsh. This feature
enables the user to create a single text configuration file that can be used to
quickly and easily configure a number of print servers.

Note: The command syntaxfor the text configurationjle is exactly the same as
ifyou were entering individual commands with npsh through a telnet session.
Please see 'Command set'on page 89for details regarding the commands and
their syntax.

The configuration file can be seen as simply a user-defined script that includes
a number of configuration commands to be executed. Comments describing
the configuration can also be included in this file provided they follow the
correct syntax.

The following is an example of a simple configuration file:

;These are comments for the example eonfig file.

;Note that comments have to start at the beginning of a
;line and be preceded by an ';'
9

version 5.4
;If this command is found and the current version does not
;correspond to the command parameter, the file execution
;will abort.
9

load default
set dest dlpltl name newdest
set dest d2plt2 name another
set dest newdest ioport pltl
save

Note: The above example includes a line for the version number: Because the
commands andor syntax may changefrom onejrmware version to another;an
old conjgurationjle may be incompatible with the current version. By
entering a version numbel; the transfer will be aborted and the user notified to
check if the commands are compatible with the currentjrmware version i f the
version numbers do not match.

Ethernet Print Server User's Manual

 Note: The above example includes the load default command. This is optional.
Including load default ensures that you always begin a configurationfrom the
factory default settings.

Note: It is not possible to generate a text configurationfile from an existing

binary configurationfile in the /config directory.

Executing a configuration file using FTP

The following example shows how to execute a configuration file using FTP:

1 Change to the local directory where the text configuration file resides.
2 Login to the print server using ftp.
ftp ipname
3 Login as root.
You must be a root user in order to FTP files to the /exec directory.
4 Change to the /exec directory.
ed exec
5 Copy the text configuration file to the exec directory.
put filename
The print server's parameters are now set according to the commands in the
configuration file.

Note: Depending on the specific commands in the configurationfile, it may be

necessary to reset the print server for the commands to take effect. Basically,
the same rules apply whether you are using npsh to issue commands or a
configurationfile to issue commands. For more information on the rules
regarding configuration commands and options, please see 'Command set 'on
page 89.

6 Logout of the FTP session.

quit
Note: If two FTP clients try to send configurationfiles to the exec directory at
the same time, the secondjle will fail.

Options
 IP routers allow computers connected to two (or more) separate networks to
communicate with each other. The print server IP routing capabilities allows
the print server to be Wide Area Network compatible.

For information on configuring the print server's IP routing features, please see
'store tcpip opts [-]gateway' on page 1 14 and 'store tcpip route addldel default
routeripaddress ifnum' on page 1 15.

138 Ethernet Print Server User's Manual

 Ethernet Print Server
User's Manual

This chapter will help you with various problems you may
encounter throughout your print setup or when printing.
There are four main sections in this chapter:
* TCP/IP Problems
* Novel1 Problems
* AppleTalk Problems
* NetBIOS Problems.
Communication related
You cannot ping the print server
There are a number of possible reasons for this:

a Have you switched the printer OFFION to reboot the print server?
Sometimes something this simple will solve various communication
problems.
m Is the network connector fastened tightly to the print server?
m Have you checked your network connection to the print server? Try it at a
new location on your network if possible or swap in another device.
m Have you made an entry in your host table (/etc/hosts, host nis map, or DNS
name table) for the print server?
Have you tried to ping with the IP address instead of the IP name? This will
eliminate any name-lookup issues and focus more on the communications
between the print server and your host.
m Is it possible that a duplicate IP address has been assigned?
a Did you use the correct netmask for your particular environment?
Has the print server been moved from another network? If so, it needs to be
reconfigured to integrate with its new location. This includes a new IP
address and netmask at the minimum. Please see 'Restoring to factory
defaults' on page 122 and 'Print server configuration' on page 23 for
possible configuration methods.
m Is there a router between the print server and your host? If so, adefault router
or a static route must be configured on the unit so the print server knows how
to get its response back to the originating host. Please see 'store tcpip' on
page 114 and 'Getting ready for complex networks' on page 122.
Have you set any hosts or networks in the print server's TCP access Ust? If
so, only these entries can access the unit. Please see 'list tcpip' on page 98 to
view current entries.
m Do you have a RARP or BOOTP server running on your network? By
default, the print server comes with the RARP and BOOTP request turned on
so although you may have stored a particular network configuration in the
units EEPROM, a RARP or BOOTP server may supply new network
parameters upon bootup. To turn off RARP and BOOTP on the unit, please
see 'store tcpip' on page 114.

140 Ethernet Print Server User's Manual

 If none of these help, try the following:
a Store the network parameters or view the currently stored settings via a
terminal on the serial port. This logs you into the unit's command set where
you can get a better understanding of what's going wrong. Please see
'Manual configuration through the serial port' on page 28.
I Reset the unit to default settings. Please see 'Restoring to factory defaults'
on page 122. Once the unit is in the default state, use one of the configuration
options listed in 'Print server configuration' on page 23 to reconfigure it.

You cannot telnet to the print server If you are unable to ping the print server
as well, please see 'Communication related' on page 140. If it is telnet only
that you are having problems with, these points should be considered:

Are you able to telnet to another host on your network or telnet from another
host? If not, look into your host's TELNET configuration.
Have you tried switching the printer OFFION to reboot the print server??
Does the fourth octet of the print server's given P address equal 0 or 255?
Each of the four octets in the IP address should be between 1 and 254.

Printing related
You've completed your print setup but nothing is printing
This can be the most frustrating problem since you've gone through the
configuration process and suddenly you don't know what's happening - "it's
supposed to work now." Here are some things to check over:
n Are you able to communicate with the print server? If you are having
communication problems, please see 'Communication related' on page 140.
I Is the printer online and in the correct mode for the file being sent to it?
a Is the printer spooler up and running on the host?
I Is the printjob data even getting to the print sewer? Once you've sent the job
from the host, try continuous lpstat commands on the print server. You
should see the byte count for that particular port incrementing as the job
passes through. If you are not seeing this happen, you may need to try a larger
job or else consider some of the other suggestions in this section.
If you're using npr.if to print, are the host binaries installed on your system
in a general directory such as /usrAocaYbin? Please see 'Printing via the
spooler' on page 32 for more on interface file printing.
Are there'any error messages in your email, a log file, or other standard error
files on your particular host? These messages can be very helpful in
narrowing down the problem.

Troubleshooting
 Are all permissions correct on relative directories and files? Usually the error
message files will indicate permission problems but it's still something to
confirm.
Might the destination or 110 port on the print server be disabled? Please see
'enable' and 'disable' on page 94 for more on this feature.

If you are not able to print successfully yet, try the following:

Avoid the print spooler altogether by printing directly to the print server from
your host. If you are successful, go over your host's print setup.

Example: cat test.plt I rsh spike lp -d d l p l t l

sends test.plt to the print server named spike to be remotely printed on the
printer attached to dlpltl. The print spooler is not used at all.

Note: npwrite can also be used to send printjobs without spooler intervention.
Please see 'Direct printing without the spooler'on page 30.

Your print job comes out formatted incorrectly

In aTCP/IP environment, this generally happens if no camage return insertion
has been incorporated into the printing process. The print server can handle
this task or it can be set on the host system with the use of onlcr. To set this
feature on the print server, please see set model. For the host, a variable,
ONLCR-YN, in the provided interface file, nprbsd.if or nprsysv.if, must be set
to 1. Please see 'Printing via the spooler' on page 32.

Your data comes out garbled

This tends to happen when PCs are used with a TCP/IP software package and
they are printing to a Unix system or directly to the print server where odrr is
turned on. DOS jobs have difficulty with this carriage return insertion and will
therefore, print out incorrectly.To solve this problem, make sure onlcr is turned
off in the model associated with the destination that you are printing to and it
is not set in the interface script if one is used somewhere in the print path.

Note: Any printing from PCs should have a "raw" setup.

Also, verify that the tab expansion (xtab) is set on with graphic jobs,

If you cannot eliminate the garbling, you may want to try printing using
another port (For example: Centronics). If the problem persists, see your
System Administrator.

Ethernet Print Sewer User's Manual

Novel1 proble

Communication related
No connection with the print server after you have completed the setup
Whether you have configured the print server as a PSERVER or as an
RPRINTER, there are several things to confirm:

Have you tried switching the printer OFWON to reboot the print server? Wait
about a minute before checking to see if it has logged in and attached to a
queue.
Is the network connector fastened tightly to the unit?
When going through the setup steps, did you name the print server 0-xxxxxx
where xxxxxx equals the last six digits of the Ethernet address? This is the
default format of the unit's name whether it is acting as a PSERVER or as an
RPRINTER.
Note: This 0-xxxxxx name must have six digits after the "-" so i f necessary,
pad out each byte with a zero (0).

Has the print server's name been changed from its default of 0-xxxxxx and
if so, have you incorporated this new name into your setup?
m When setting the print server up as a PSERVER, did you specify a
destination on the print server (e.g. dlpltl) for the printer name and did you
remember this name is case sensitive?
Note: Print server destinations are case sensitive so they will not be recognized
if they are typed incorrectly. By default, they are all in lowercase. Ifyou are
setting up in a NetWare 4 environment, the destination must be renamed to
uppercase to match PCONSOLE S entry. Please see set destfor information on
changing names.

In a PSERVER setup, did you ensure that you were in bindery emulation
mode? If you were, then did you do your entire print setup (i.e. queue, print
server, printer) in this mode? It is important to create all print setup elements
in this mode.
Is there a password set for the print server to utilize when it is logging in to
the file server? Make sure the print server's PSERVER password matches
that of the PCONSOLE's PSERVER setup or set both places to no password.
Is there an entry when a list rprinter is done on the print server? When the
print server is configured as an RPRINTER, this command should produce

Troubleshooting 143
 the appropriate entry. Please see 'Host software' on page 54 for details on
using the provided DOS host software, npsh.exe, to communicate with the
unit in a Novell-only environment.
Have you tried using the print server's debug novel1 command to see if it
even recognizes any file servers on the network? You can use the DOS host
software, npsh.exe, to communicate with the unit.
If you look in CURRENT QUEUE STATUS within the PRINT QUEUE
INFORMATION menu in PCONSOLE, can new servers attach to this
queue?
If you're configuring the print server as an RPRINTER, have you setup the
CONFIG file accordingly? Is SYS VOLUME correct for your particular
environment or was it configured differently upon your Novell installation?
If the print server has logged in to the file server but has not attached to the
queue, there may be a permission problem. Make sure the appropriate users
have rights to this queue (they should be in the group "everyone.") Also, YOU
may have to assign the queue to "root" so that is available to everyone.

If none of these help your situation, you may want to try the whole setup again.
Completely delete the setup that is giving you trouble and go through the setup
again following each step carefully.

Note: Be sure to switch the printer OFF/ON to reboot the print server before
beginning a new setup and after completing either a PSERVER or RPRINTER
setup. Wait at least a minutefor the print server to login and attach to a queue.

Printing related
The job goes to the queue but nothing prints
If nothing is printing, make sure you have a connection to the print server first.
Please see 'Communication related' on page 140 if you are having
connection-related problems. Otherwise, consider these points to solve any
printing problems you may be having in your Novell environment:

r Does the job leave the queue or is it stuck there indefinitely? If it leaves
properly, the problem points to the actual printing mechanism on your Novell
system (i.e. CAPTURE, NPRINT, etc.), to the print job format, or to the
printer itself. Otherwise, concentrate on the configuration steps you've taken
on your system.
Have you confirmed that you can print from the print server to the printer
ignoring the Novell setup altogether? Please see 'start' on page 109 for a
good test you can try.

144 Ethernet Print Server User's Manual

 Is the printing mechanism you are using (i.e. CAPTURE, NPRINT, etc.)
configured to service the appropriate queue?
Is the print server configured as the queue's Currently Attached Server? If
not, make sure you have associated the queue and the printer. Please see
'Host configuration' on page 57.
Is there a hold on the print job? If you select the job from PCONSOLE's
CURRENT PRINT JOB ENTRIES, change the User Wold or Operator
Hold to no.
If you look in PCONSOLE's CURRENT QUEUE STATUS within the
PRINT QUEUE INFORMATION menu, is the server configured to service
entries in this queue? It is possible to turn servicing off here.

These are just a few things to confirm. If you are still having printing problems
at this point, try switching the printer OFFION to reboot the print server and
either go over every step you took in your configuration process, or try a new
setup paying special attention to each step explained in 'Host configuration' on
page 57.

The job prints but it comes out incorrectly

This category really can be broken down into several sub-categories such as
lost characters, garbled data, extra banner pages, or blank pages at the end of
the job. However, the reason for these mishaps can generally be traced to the
printing mechanism used on your Novel1 system. These points should be
considered when configuring your print method (i.e. CAPTURE, NPRINT,
etc.):

g Did you include the No Tabs option?

g Did you specify No Banner with Postscript printers?
Did you turn off banner pages and formfeeds if this is already taken care of
within an application or on the print server? Doubling up of these types of
print features is easy to do since these options are provided both on the print
server (in a model) and within the print command.
r Are you running the latest version of PSERVER (later than 1.22)? If not,
upgrade the PSERVER software.
In a PSERVER setup, did you ensure that the printer name (e.g. dlpltl) was
set up as "Dejned Elsewhere"?
w Is the timeout option in the CAPTURE command set high enough so the
printer doesn't time out before the print processing has had a chance to
complete? This can be a problem with graphic jobs.

Troubleshooting
 Some other things to consider when garbled data persists are:

tab expansion (xtab) set on (in a model) with graphic jobs,

the right driver for the printer if printing from within Windows,

With other print methods, the only thing to remember here is to configure the
print job for Byte Stream.This will pass the data to the print server untouched.

For additional information on these suggestions or on various Novel1 printing

mechanisms, please refer to your NetWare user manuals.

146 Ethernet Print Sewer User's Manual

The Laserwriter icon in the Chooser Menu doesn't display any printer
destinations

In this situation, these things should be considered:

Are you using EtherTalk rather than LocalTalk or TokenTalk?

M Is "EtherTalk" chosen in the control panel's Network icon?
Have you checked the print server and the Apple system's Ethernet
connections?
rn Have you configured the print server to show up in the correct AppleTalk
Zone. Please see 'AppleTalk zones' on page 70 for information on doing this.

Troubleshooting
 You cannot map an LPTx device
These are some of the errors you may encounter and what they mean when
attempting Step 13 in NetBIOS 'Host configuration' on page 78:

"network path not found" The name of the print server is not correct.
"unexpected network error" The print server destination specified does not
exist.
"in use" The specified LPTx device is not available.

148 Ethernet Print Sewer User's Manual

-
Ethernet Print Server
User's Manual
1 Name / Hexadecimal 1 Description
BS 08 Backspace
I
T OC Formfeed
CR OD Carriage return
SP 20 Space

I LF I OA 1 Linefeed
TAB 09 Tab
ESC 1B Escape
DEL 7F Delete
EOT 04 End of transmission
NUL 00 NULL character
Table 3: List default varariables

150 Ethernet Print Sewer User's Manual

Software specifications
I# 1 Description
I
20 I TCP Protocol for FTPD (data)
I
21 I TCP Protocol for FTPD (control)
TCP Protocol TELNETD port
BOOTP client port
161 UDP port for SNMP
514 TCP Protocol Remote command daemon port
5 14 UDP SYSLOG client support
5 15 TCP Protocol BSD 4.3 LPD port
4000 TCP Protocol PLTl port
4010 TCP Protocol PLTl port f s logging
4200 TCP Protocol PLT2 port
4210 TCP Protocol PLT2 port for logging
4400 TCP Protocol PLT3 port (Not used)
183 TCP Protocol PLT3 port for logging (Not used)
4600 TCP Protocol PLT4 port (Bot used)
4610 TCP Protocol PLT4 port for logging (Not used)
Table 4: Port Numbers

Client application software can send raw data to PLTl or PLT2 by opening a
socket to the associated TCP port number. Such connections are queued along
with LPD and rsWrcmd1remsh print jobs so that applications must close the
socket to permit subsequent jobs that are queued to print by other methods.

Note: There can be 256 simultaneous TCP connections depending on the

current memory available. 10 simultaneous TELNETconnectionsare possible.

Specifications
152 Ethernet Print Server User's Manual
 Ethernet Print Server
User's Manual

This chapter will help you understand words,

abbreviations and acronyms used in the manual.
 a2ps ASCII to Postscript translation program.
AIX IBM's type of BSD Unix
ALS Automatic language sensing. Printer that automatically
recognizes the data format of the incoming file.
ARC Ethernet Address Control Protocol
ARP Address Resolution Protocol.
ASCII American Standard Code for Information Interchange.
A commonly used format for text files.
Autosensing printer Printer that automatically recognizes the data format of
the incoming file. Also called automatic language
sensing.
Banner page A page printed before the print job including details
about that job.
BOOTP Bootstrap Protocol
bps Bits per second. +? ,

BSD Berkley Software Distribution. A version of UNIX.

Centralized spooling Sending all print jobs to a central host for storage until
a printer becomes available.
Checksum 16-bit value to confirm integrity of the data printed. A
method of checking if a block of transmitted data is
correct. The checksum character is attached to a block
of data.
Chooser Feature within the Macintosh's operating system that
controls system devices.
Configuration file (CONFIG) File that the Ethernet print server reads
upon bootup in a Novel1 environment. This file
contains npsh commands which the Print Server
executes as if they were entered on the unit itself. This
file is necessary if the print server is configured as an
RPRINTER but optional otherwise.
CPS Characters per second.
CR Carriage return.
CTS Clear to send. Serial interface command signal.

154 Ethernet Print Sewer User's Manual

Daemon A continuously running process that handles
system-wide functions, such as network administration
or line printer spooling. It is not associated with a user.
DCD Carrier detect. Serial interface command signal.
DCE Data Communications Equipment.
Default router A device on a communications network that assists
message delivery. On a single network linking many
computers through a mesh of possible connections, a
router receives transmitted messages and forwards
them to their correct destinations over the best available
route. On an interconnected set of local area networks
(LANs) using the same communications protocols, a
router acts as a link between LANs, so messages can be
sent between them.
Destination Conceptual destination (similar to a logical queue)
within the print server firmware that defines the print
job and directs it to a specific UO port.
Note: On the host, any number of print destinations can be defined. These are
not the same as print server destinations.

DMA Direct Memory Access. A high-speed technique for

moving data into and out of memory.
DNS Domain name server
Domain ""Agroup of computers administered together.
Domain name server Host providing responses to queries for a given IP
name's IP address.
DTE Data Terminal Equipment.
EEPROM Electrically-Erasable, Programmable Read-only
Memory. Preserves data after power is removed.
ezsetup Quick and easy installation script that runs on a TCP/IP
host and configures both the print server and a host for
printing.
FCC Federal Communications Commission of the United
States of America.
FF Formfeed.

Glossary
Flash memory Allows for upgrade without replacing ROMs inside the
Print Server.
FTP daemon File Transfer Protocol daemon for uploading or
downloading files in TCP/TP.
GOSIP Government Open Systems Interconnection Profile. A
U.S. government document allowing new networks to
use OSI protocols.
Header strings Strings that precede print jobs used to control the
printer and set printing options.
Host A computer attached to a network. Location of print job
origin.
ICMP Internet control message protocol
ifnum Interface number. An index to a Network Interface Tap
(NIT). ifnum will always be 1 for the print server since
there is only one network interface, Ethernet.
Interface file Host filter that processes the print job before it is sent to
the print server.
IP Internet protocol.
IP router IP routers allow computers connected to two or more
separate networks to communicate with each other. IP
routers forward data packets that do not belong on the
local network.
%
.

IPX Inter network packet exchange

I10 port Inputloutput port. Interface.
kbps Kilobytes per second.
LAN Local area network
LF to CRLF mapping Linefeed to camage return-linefeed conversion.
Logpath Logging path. Format and location for printer logging
information.
LPD Line printer daemon. A program used for printing on
BSD systems.
MIB Management Information Base. A set of variables
(database) that a gateway running SNMP maintains.

Ethernet Print Server User's Manual

Model Specifies a destination's characteristics. Each model
includes one or more settings that act as mini-filters for
each job passing through the associated destination.
NetBIOS Network basic input output system. Standard interface
to PC networks.
Netmask A binary value used to sub-network IP inter-networks.
Netname An IP name.
Newsprint SunPics (SUN) system for open network printing.
NIT Network Interface Tap. A module that serves as a
generic interface between the data link protocol layer
(i.e. Ethernet or Token Ring) and higher network
protocol layers. Each NIT is indexed by an interface
number (ifnum).
npd NetPrint daemon. Daemon for handling bi-directional
TCP/IP printing requirements.
npconfig NetPrint setup and configuration. An in-depth
management utility allowing you to install, monitor,
change, and troubleshoot the print server.
npscramble NetPrint scramble. A program that scrambles print job
data before sending it over a TCPlIP network to the
print server where it is descrambled and printed.
npsh Command shell on the print server used for parameter
configuration and display and for print job monitoring
and troubleshooting.
npwrite NetPrint write. A program to send data directly from a
UNIX host to an print server.
onlcr A filtering program that adds camage returns to all
solitary linefeeds.
OSI Open Systems Interconnection
Output processing On the print server, this refers to camage return
insertion (onlcr), tab expansion (xtab) settings, and
print job descrambling. Referred to as "opost" in the
model.
Papname Printer Access Protocol (PAP) name. An AppleTalk
name for each printer defined on the host. Makes up the
second half of the name which appears in the Chooser.

Glossary
 There can be a maximum of two printers which are
transparently mapped to any one of eight destinations
on the print server.
Parity An error checking scheme. Parity may be even (even
number of ONE bits), odd (odd number of ONE bits) or
none. Usually used in serial communications.
Ping Command to test an IP connection.
Pio file AIX spooling system configuration file.
PLT Plot file
PS postscript
Pseudo-tty A UNIX facility for accessing network resources
through standard UNIX device interfaces.
Reverse Address Resolution Protocol. A mechanism for
a network device to discover its address dynamically
when it boots.
a.5
Rarpd daemon Server that responds to requests for address discovery.
RFC Request for comment. A set of documents that specify
the Internet protocols and provide other relevant
information about the Internet.
RON Read only memory. Used for storing the firmware.
Router A device that forwards Internet Protocol (IP) packets to
their destination. "
rsh/rcmd/remsh Executes a command on a different host.
SLIP Serial line Internet protocol. A protocol used to connect
two internet hosts using a serial line.
SMB Server message block (NetBIOS)
SMIT program AIX device administration program.
SMTP Simple mail transfer protocol
SNMP Simple network management protocol. A standard
protocol used to monitor IP gateways, hosts, and the
networks to which they attach.
Spooling Storing data in memory or in a file until it can be
printed.

158 Ethernet Print Server User's Manual

Switchable Capable of printing both plot files and Postscript files.
The print server attaches a header and trailer string to a
print job to switch printer modes.
SYSLOGD System message logger. Collects messages sent from
system processes and routes them to a common
destination.
Tab expansion Expanding a tab character in the data to its required
width in spaces (xtab).
Tar Command for archiving data onto a permanent storage
medium.
TCP Transmission control protocol used for reliable
end-to-end communication over an IP connection.
TCPmP Name given to the suite of protocols (including but not
limited to TCP and IP) that govern the transmission and
services of a network.
TCP port A logical connection point in the software on a TCPmP
host.
Telnet Command and protocol to establish a terminal
connection to a remote host over a TCPmP network.
Transcript Printing system developed by Adobe to facilitate
printing of Postscript documents. Referred to as Adobe
Transcript.
Trailer strings Strings that follow print jobs used to control the printer
and set printing options.
UDP User datagram protocol
WAN Wide area network.
WW Windows for workgroups.
xtab See tab expansion.

Glossary
Ethernet Print Server User's Manual
 Ethernet Print Server
User's Manual

This section will describe the basic steps required to:

* install the ethernet interface in your printer.
* install the print server in the various supported environments:
'w
- Unix,
- Novel1 (PSERVER and RPRINTER),
- NetBIOS over TCP/IP,
- AppleTalk.
Note: Before installing the print sewel; it may be useful to look at 'Planning
your print setup' on page 17.5,for advantages/disadvantages of various
conjguration options.
 et interface
Note: For safety reasons, this integace should be installed by qualged
personnel.

V installing the interface on an Oce 9400 plotter.

(See also 'Installing the interface on an OcC 5200 plotter.' on page 165).
1 Switch the printer power OFF and disconnect the power cable.
2 Using a screwdriver, remove the two screws (A) holding the controller drawer
(B) at the rear of the plotter.

[4] Removing the controller screws

3 Remove the screw (C) holding the panel filler ( 0 )

162 Ethernet Print Server User's Manual

4 Carefully pull out the controllerdrawer (B), taking care not to jam cables inside
the printer.

[5] Pull out the controller drawer

Installation
 Note: Before installing the print server board. note the Ethernet address, which
is on the board (or on a sticker included in the kit).
6 Position the print server board (E) on the rear mounting lugs (F) then firmly
press the board all the way into the connector (G) of the controller board. (If
the board is not seated correctly, the print server will not function).

(71Inserting the ethernet board

7 Replace the screw (C) (which was removed in step 3) to hold the Ethernet
board.
8 Slowly push the controller drawer into the printer. Take care that the cables do
not jam inside the printer.
9 Replace the two screws (A), removed in step 2.
10 Re connect the power cable.
The installation is complete.

Go to 'Connecting the printer to your network' on page 168.

Ethernet Print Server User's Manual

 Installing the interface on an OcB 5200 plotter.
(See also 'Installing the interface on an OcC 9400 plotter.' on page 162).
1 Switch the printer power (A) OFF and disconnect the power cable (B).
2 Using a screwdriver, remove the four screws (C) at the rear of the printer which
hold the cover (D).

[8] Removing the controller screws

3 Sitting behing the plotter, remove the screw (E) holding the panel filler (F).

[9] Removing the panel filler ( I )

Installation
 Remove the panel filler (F) from the inside of the controller (G). (The panel
filler will not be used again).

[lo]Removing the panel filler (2)

Note: Before installing the print sewer board, note the Ethernet address, which
is on the board (or on a sticker included in the kit).

5 Position the print server board (H) on the rear mounting lugs (I) then firmly
press the board all the way into the connector (J) of the controller board. (If the
board is not seated correctly, the print server will not function).

Ethernet Print Sewer User's Manual

6 Replace the screw (E) (which was removed in step 3) to hold the Ethernet
board.
7 Replace the four screws (C), removed in step 2.
8 Re connect the power cable.
The installation is complete.

Go to 'Connecting the printer to your network' on page 168.

Installation
Connecting the printer to your network
Ensure the printer is switched off.

Connect the tranceiver (A) to the 9 pin connector (6)on the ethemet interface
of the printer. Depending on your network type, connect the UTP cable (6)
from the tranceiver to your network. Or, connect the tranceiver directly to the
T connector (D) of the coax cable (E).

[I 21 Connecting the printer

Switching the printer on

Connect the power cable to the plotter. Switch the printer on. Then switch your
computer on.

The plotter performs its self tests, then displays:

ADY

The ethemet interface is automatically recognized and enabled when it is

installed in an OcC printer.

168 Ethernet Print S e w e r User's Manual

Unix print server installation
The following outlines the basic steps required to add the print server to a Unix
network.

Once the unit is physically attached to the network, you need to:

1 Assign an IP address, netmask, and possibly a default router to the print server.
This can be done in several ways:
(a) Automatically with ezsetup or npconfig (option 1 from the Main
Menu). Please see 'Configuration with ezsetup or npconfig' on page 24.

(b) Manually through the network using arp. Please see 'Manual
configuration with ARP' on page 25.

(c) Manually through the network using rarp. Please 'Manual

configuration with R@P' on page 26.

(d) Manually through the network using bootp. See 'Manual

configuration with BOOTY on page 27.

(e) Manually through the serial port. Please see 'Manual configuration
through the serial port' on page 28.

2 Configurer the print se-$p on the host to print to this unit. This can be done in
several ways depending on your host system.
(a) Automatically with ezsetup or npconfig (Option 2 from the Main
Menu) Please see 'Configuration with ezsetup or npconfig' on page 24.

(b) Manually for a BSD Unix environment. Please 'BSD UNIX' on

page 35.

(c) Manually for a System V Unix environment. Please see 'System V

UNIX' on page 39.

(d) Manually for a AIX Unix environment. Please see 'AIX' on

page 49.

Installation
 er installation

PSERVER setup
The following outlines the basic steps required to add a print server to a Novell
network using a PSERVER setup and applies to any Netware version. The print
server replaces a dedicated workstation running PSERVER.EXE or
PSERVER.NLM so these are no longer needed.

Once the unit is physically attached to the network, you need to:

1 Enter into a PCONSOLE session. PCONSOLE is used for the entire print
setup.
2 Create a new queue.
3 Create a new print server. The name will be is 0-xxxxxx where xxxxxx is the
last six digits of the Ethernet address as notkd during the installation. (Refer to
page 164).
4 Add a new printer and type in the name of one of the eight default destinations
on the unit. (e.g. dlpltl, d2plt2, etc.) At the prompt for the type field, select
DEFINED ELSEWHERE. If this is not available, choose PARALLEL.
5 Associate this printer with the queue defined in Step 2.
6 Switch the printer OFFION to reboot the print server.

RPRINTER setup
The following outlines the basic steps required to add a print server to a Novell
network using a RPRINTER setup and applies to any Netware version. The
print server interacts with an existing PSERVER running PSERVER.EXE or
PSERVER.NLM.

Once the unit is physically attached to the network, you need to:

1 Enter into a PCONSOLE session.

2 Create a new queue.
3 Select an existing PSERVER and define a new remote printer. The printer
name can be anything but the type must be REMOTE O T H E ~ K N O W N .
4 Associate this printer with the queue created in step 2.
5 Exit PCONSOLE.

170 Ethernet Print Sewer User's Manual

 6 Restart PSERVER (e.g. PSERVER.NLM)
7 Go to SYSALOGIN and create a directory named 0-xxxxxx where xxxxxx is
the last six digits of the Ethernet address as found on the bottom of the unit.
8 Inside this directory, create a file called CONRG.
9 Enter the line: set rprinter add pservername printernumber destname where
pservername is the existing PSERVER's name, printernumber is the defined
number for this printer in that PSERVER, and destname is a print server
destination (e.g. dlpltl, d2plt2, etc.).
10 Switch the printer OFF/ON to reboot the print server and wait about a minute
for it to connect to the file server.
For more information on Novell PSERVER or RPRINTER configuration,
please see 'Novell configuration' on page 53.

Installation
 ows configuration
The following outlines the basic steps required to add a print server to a
Windows NT Version 3.5 network using the LPR print method.

Once the unit it physically attached to the network, you need to:

1 Ensure that the appropriate network software is installed on yolx host system.
In the Network Settings dialogue box, make sure you see these in the Installed
Network Software scroll box:
w MS TCPAF' Printing
w TCP/IP Protocol
a Simple TCPAF' Service

2 Make sure you workstation has an IP address and netmask.

3 Assign an IP address and netmask to the print server. Use a PC or terminal
connected to the print server's serial port to do this. Please see 'Manual
configuration through the serial port' on page 28 for information on
completing this step.
4 On your NT workstation, select the Print Manager.
5 Select Create a Printer from the Printer menu.
6 Define the printer name and driver. In the Print to field, select Other...
7 Choose LPR port from the displayed list and select Ok.
8 Enter in the name or IP address of the print server.
9 Fill in the destination on the print server and select OK. The destination will be
the name of one of the eight default destinations on the unit. (e.g. dlpltl,
d2plt2,etc.)
For more information on NetBIOS over TCP/IP configurations, please see
'NETBIOS configuration' on page 73.

172 Ethernet Print Sewer User's Manual

asic AppleTalk configuration
The following outlines the basic steps required to add a print server to an
AppleTalk network.

An AppleTalk setup does not require any print server configuration; the
network parameters are automatically configured for you once the print server
is booted on the network.

Once the unit is physically attached to the network, you need to:

1 Select Chooser from the Apple Menu.

2 Select the Laserwriter icon.

A list of available printers will appear. By default, the format of each name is
OCEname-papname where OCEname is the name of the print server and
papname is an print server UO port. Both names are configurable.

Example: 0-000BF5-pltl is the printer associated with the print server named
0-000BF5 using the first port.

3 From the list of printers, select one to print to.

For more information on AppleTalk configurations, please see 'AppleTalk

configuration' on pages7.

Installation
Ethernet Print Server User's Manual
 Ethernet Print Server
User 's Manual

In this appendix, you willjnd information that will help

you with your print setup including the advantages and
disadvantages of your various conJiguration options.
w
 uration considerations
Setting ( Advantages
I
1I Disadvantages
TCP/IP Print Methods
lpd communications Print without an interface file. No Not available on all UNIX systems.
host software required and easy Output processing must be done on
setup. the Print Server, not on the host.
rshlrcmdlremsh Available on most UNIX systems. Requires an interface file on a BSD
communications Allows for processing on the host system.
to improve unit's performance.
npd communications Allows bi-directional Requires host software. npd may
communication. Uses standard have to be compiled for your
UNIX device interface. system.
Novell Print Methods
PSERVER Faster print process. Replaces a Takes up a NetWare user license.
dedicated workstation or frees up Requires bindery emulation if
file server resources. using NetWare 4.
RPRINTER Doesn't take up a NetWare user PSERVER must be ~ n n i n g .
license.
Processing Location
Output processing Increases print server throughput. Increases overhead on host system
performed on host and requires host software.
Output processing Interface files optional and no host Decreases throughput.
performed on print software required.
server

Ethernet Print Server User's Manual

Setting 1 Advantages
I
I Disadvantages
I

Optional Processing
Banner page Job identification at printer output. Decreases throughput. Requires an
extra page to be printed.
Tab expansion (xtab) Flexible tab widths. Decreases throughput.
Carriage return Adds carriage returns to solitary Decreases throughput.
insertion (onler) linefeeds.
ASCII to Postscript Autosenses print job type and Decreases throughput.
conversion (a2ps) converts ASCII files for printing on
PostScript printers.
Switchable printer Use one printer for both plot file Requires header and trailer strings
control and Postscript jobs. to manually switch printer between
modes.
Descrambling Some print job security as data Requires binary on host system and
travels over the network. lowers throughput.

Planning your print setup

178 Ethernet Print Sewer User's Manual
111111
Ethernet Print Server
User's Manual
Notation conventions
There are a number of notation conventions used in this manual. This
consistent style enables you to quickly become conversant with the use of this
manual and consequently the Ethernet Print Server.

Description Each section or subsection contains a description of the feature or

operation identified in the title. It might also include possible applications, as
well as any guidelines that you should bear in mind.

Procedures A description is followed by a procedure. A procedure always

begins with a phrase which briefly describes the procedure (for example,
"Select a plot to file") followed by a series of numbered steps that take you,
step by step, through all phases of performing the operation.

Attention getters There are several types of information to which we draw

your attention. This information is classified as follows:

Note: In a 'Note', information is given about matters which ensure the proper
functioning of the software, but useful advice concerning its operation may
also be given.

Attention: The information that follows 'Attention'is given to prevent

something (for instance, your original diskettes) being damaged.

180 Ethernet Print Server User's Manual

___II_ -

Reader's comment sheet

Have you found this manual to be accurate?
CI Yes
CI No

Could you operate the product after reading this manual?

B Yes
5 No

Does this manual provide enough background information?

CI Yes
5 No

Is the format of this manual convenient in size, readability and arrangement

(page layout, chapter order, etc.)?
5 Yes C-

B No

Could you find the information you were looking for?

CI Always
CI Most of the times
CI Sometimes
CI Not at all
4 %a

What did you use to find the required information?

CI Table of contents
CI Index

Are you satisfied with this manual?

CI Yes
CL No

Thank you for evaluating this manual.

If you have other comments or concerns, please explain or suggest
improvements overleaf or on a separate sheet.

465221237
Edition D

Miscellaneous
Comments:

Date:
This reader's comment sheet is completed by:
(Please do$ll in your occupation, even ifyou prefer to remain anonymous)
r;,
Name:

Occupation:
Company:
Phone:
Address:
City:
Country:
Please return this sheet to:

OcC-TechnologiesB.V.
For the attention of ITC user documentation.
P.O. Box 101,
5900 MA Venlo
The Netherlands

465221237
Edition D

Ethernet Print Server User's Manual

 -- -
Ethernet Print Server
User's Manual

Pleasejind on the next page the oflcial list of Oce' ojyices, Worldwide.
Our salesforce and technical support engineers will be pleased to
assist you whenever you need help for installing and using your
printers with the Oce' software.
AUSTRALIA CZECHOSLOVAKIA HUNGARY
Oce Australia Ltd. Oce Ceska republika s.r.0. Oce Hungaria KFT
89 Tulip Road K Rysance 16 Karpat Ut 42
Cheltenham VIC 3192 147 54 Praha 4 1133 Budapest
Tel: (61-3) 263 33 33 Tel: (42-2) 463 451 Tel: (36) 1 269 883618837
Fax: (61-3) 584 43 57 Fax: (42-2) 461 260 Fax: (36) 1 269 8835

AUSTRIA DENMARK ITALY

0ce-bsterreich GmbH Oce Danmark AIS Oce ltalia S.p.A.
Carlbergergasse38 Kornmarksvej 6 Via Cassanese, 206
A-1 230 Wien DK 2605 Broendby 20090 Segrate, Milano
Tel: (43-1) 865 36 10 Tel: (45-43) 63 00 22 Tel: (39-2) 21 63 1
Fax: (43-1) 865 33 27 Fax: (45-43) 43 06 22 Fax: (39-2) 21 63 398

BELGIUM FRANCE ALAYSIA

Oce Belgium S.A.1N.V. Oce-France S.A. Oce Systems Sdn. Bhd.
Avenue Jules Bordet, 32 32, avenue du Pave Neufk 15A, Jalan Universiti,
1140 Brussels B.P. 2 46200 Petaling Jaya,
Tel: (32-2) 729 48 11 93161 Noisy le Grand Selangor Darul Ehsan,
Fax: (32-2) 729 49 10 Tel: (33-1) 45 92 50 00 Tel: (603) 7584088
Fax: (33-1) 43 05 12 15 Fax: (603) 7556125
BRAZIL
Oce Brasil GERMANY NETHERLANDS
Av. Candido Portinari, 1174 Oce-DeutschlandGmbH, Oce Nederlandse
05114 Sao Paulo SP Solinger StraOe 5-7 Verkoopmaatschappij B.V.
Tel: (55-11) 261 64 66 45481 Mijlheim a. d. Ruhr Brabantlaan, 2
Fax: (55-11) 832 25 88 Tel: (49-208) 48 45 0 5216 TV Den Bosch
Fax: (49-208) 460 167 Tel: (31-73) 68 15 815
CHINA Fax: (31-73) 61 20 685
Oce Office Equipment Co. Ltd. HONG KONG
Xu Mu Cheng, GuangxirnenBei Oce (Hong Kong) Ltd. NORWAY
Li No 1, Hysan Avenue Causeway Oce Norge AS.
Chao Yang District Bay, Hong Kong Gjerdrums vei 8
Beijing 100028 Tel: (852) 577 60 64 0486 Oslo 4
Tel: (86) 10 6422 1622 Fax: (852) 577 89 57 Tel: (47-22) 95 05 20
Fax: (86) 10 6426 3394 Fax: (47-22) 95 05 30

Tlf.: (47-22) 02 70 00
Faks: (47-22) 02 70 04

184 Ethernet Print Server User's Manual

POLAND SWEDEN UNITED KINGDOM and
Oce-Poland Ltd. Oce Svenska AB IRELAND
02-0232 Warszawa lsafjordsgatan 5 Oce-Engineering Systems
ul. Lopuszanska 53 Box 1231 (UK) Ltd
Tel: (48-22) 467429 S-164 28 Kista 300 Park Avenue
Fax: (48-22) 467431 Tel: (46-8) 703 41 50 Aztec West, Almondsbury
Fax: (46-8) 703 99 86 Bristol, BS12 4RG
PORTUGAL Tel: (44-1454) 61 77 77
Oce-Lima Mayer S.A. SWITZERLAND Fax: (44-1454) 61 84 35
Av. Infante D. Henrique Oce (Schweiz) AG
Lote 309 Sggereistrasse 29 Oce (UK) Ltd
1900 Lisboa P.O. box 114 Langston Road
Tel: (351-1) 831 65 00 8152 Glattbrugg ZH Loughton
Fax: (351-1) 831 65 55 Tel: (41-1) 829 11 11 Essex, IG 103SL
Fax: (41-1) 829 13 48 Tel: (44-181) 508 55 44
SINGAPORE Fax: (44-181) 508 66 89
OcB (Singapore) Pte Ltd TAIWAN
1 Clementi Loop #01-01102 Oce Graphics (Taiwan) Ltd USA
Margateo Districentre No 99-24, Nan-Kang Road, Oce-Bruning Inc.
Clementi West Distripark Sec 2 1800 Bruning Drive West
Singapore 129808 Taipei, Taiwan, R.O.C. ltasca, lL 60143
Tel: (65) 467 38 66 Tel: (886-2) 651 65 16 Tel: (1-708) 351-29 00
Fax: (65) 466 67 29 F a : (886-2) 783 32 42 F a : (1-708) 351-75 49

Oce (Far East) Pte Ltd THAILAND AFRICA,

1 Clementi Loop #02-10 Oce (Thailand) Ltd MIDDLE-EAST,
Margateo Districentre B.B. Building, 16th Floor SOUTH AMERICA,
Clementi West Distripark 54 Asoke Road EASTERNEUROPE
Singapore 129808 Sukhumirt 21 Oce-NederlandB.V.
Tel: (65) 467 30 22 Bangkok 10110 Direct Export
Fax: (65) 466 74 26 Tel: (662) 260 71 33 PO .Box 101
Fax: (662) 260 71 37 5900 MA
SPAIN Venlo
Oce Espaiia S.A. The Netherlands
Poligono Mas Blau Tel: (31-77) 359 39 00
closona, 2 FX (31-77) 359 54 31
08820 Prat de Llobregat
Tel: (34-3) 484 48 00
FX (34-3) 484 48 28

Oct5 Offices
186 Ethernet Print Sewer User's Manual
Index
Port number 151
Unix 35
a2ps definition 154
Access list network security 124
Adding an SNMP user 129
Addresses 183
Adobe Transcript 47 Cancel 93
AIX 49 Cannot ping the print server, Ping error 140
AIX definition 154 Cannot telnet the print server 141
AIX spooling system 158 Capturing printer feedback 120
AppleTalk configuration 67, 173 Carriage return insertion,
AppleTalk features 13 Advantagesldisadvantages 177
AppleTalk problems 147 Centralized spooling, definition 154
AppleTalk zones 70 Changing print server name, AppleTalk 70
Applications using npd 46 Checksum definition 154
ARC definition 154 Chooser 173
ARP definition 154 Chooser definition 154
ASCII definition 154 chr 93
ASCII to Postscript 154 Commandset 89
ASCII to Postscript conversion, Command syntax 93
Advantagesldisadvantages 177 Communication problems, Novel1 143
Assign an IP address 169 Communication problems, TCPAP 140
Autosensing printer definition 154 Compiling and monitoring the custom MIB 130
Autosensing, job format 177 Compiling host software, Unix 20
Autosensing/Autoswitching, Complex networks 122
Advantagesldisadvantages 177 'L- Config directory, to configure using WP 134
Configuration
Considerations 176
Planning 175
5 Unix 19
Banner page definition 154 Configuration file, definition 154
Banner page generation, Configurationoptions, AppleTalk 70
Advantagesldisadvantages 177 Configuration with ezsetup 24
Basic Setup Sets, NetBIOS 74 Configuration with ezsetup or npconfig, Unix 24
Bi-directional communications 176 Configuration with npconfig 24
Bi-directional communications. See also npd Configure terminal settings, Unix 28
BOOTP Configure the print setup 169
definition 154 Configuring print server using FTP 134
Port number 151 Connecting the printer to your network 168
bps definition 154 Controllingthe frame types used 121
BSD Copying a configuration using FTP 134
definition 154 cps definition 154
Interface script printing, Unix 36 CR definition 154

Index
CTS definition 154
Custom interface scripts, Unix 33 F
Custom MIB compiling and monitoring 130 Factory defaults, Unix 29
Custom MIB traps 128 FCC definition 155
Custom MIB variables 127 FF definition 155
Custom MIBs and traps 127 File servers, Novell 126
Flash memory, definition 156
Format problems 142
Frame types used 121
FTP daemon 131
Daemon definition 155 FTP daemon definition 156
DCD definition 155 FTP daemon print method 52
DCE definition 155 FTP print server 131
debug 94 FTP's PC/TCP print method 5 1
Default destination names 84
Default router, definition 155
Descrambling, Advantages/disadvantages 177
Descrambling, see also Scramblingldescrambling G
Destination, definition 155 Garbled data 142, 145
Destinations 15. 84 General options 119
Print 155 loss& 153
Print server 155 GOSIP definition 156
Direct memory access 155
Direct printing without the spooler, Unix 30
Direct socket printing 52, 151
Disable 94
W
Disabling AppIeTalk 7 1
Header string definition 156
Disabling the AppleTalk 7 1
Header string, for switching 177
DMA definition 155
Host configuration, AppleTalk 69
DNS definition 155
Host Configuration, NetBIOS 78
Domain definition 155
Host configuration, NetBIOS 78
Domain name server definition 155
Host configuration, Novell 57
DTE definition 155
Host configuration, Unix 30
Host definition 156
Host software, Novell 54
Host software, Unix configuration 20
E
EEPROM definition 155
Enable 94
Error, nothing prints 144
I
EtherTalk 67
I/0 port definition 156
Exec directory to configure parameters 136
UO ports 15
Executing a configuration file using FTP 137
IBM print spooler 49
ezsetup definition 155
ICMP definition 156
ezsetup installation program, Unix 21
ifnum definition 156
In use, error message 148
Install

188 Ethernet Print Server User's Manual

 AppleTalk environment 173 List sysinfo 97
Novel1 environment 170 List tcpip 98
Unix environment 169 List test 98
Windows environment 172 List time 98
Install ethernet interface 161 List user 98
Installing the ethernet interface 162 List var 98
Interface drawer, removing 162, 165 Load 99
Interface file definition 156 Load default 99
Interface number definition 156 LocalTalk 67
Interface script advantagesldisadvantages 176 Logpath definition 156
Internal architecture 83 Logpath method, printer feedback 120
IP definition 156 Logpaths 87
IP router definition 156 Lpcommand 99
IPRouting 138 Lp method, printer feedback 121
IPX definition 156 LPD 156
avantagesldisadvantages 176
Ipd remote printing, Unix 35
LPR Client, NetBIOS 75
J LPR printing method, NetBIOS 79
Jobs, security 177 Lpstat 100
LPTx problems 148

K
kbps definition 156 M
Keycode 94 Managing with SNMP 127
Manual configuration through the serial port 28
Manual configuration with ARP 25
Manual configuration with BOOTP 27
L - Manual configuration with RARP 26
LAN definition 156 Manual, User's comments 181
Laserwriter 173 MIB 156
Laserwriter icon problem 147 MlB traps 128
LF to CRLF mapping 156 MIB variables 127
Line printer daemon definition 156 MIBs and traps 127
List arp 95 Model types, table 85
List commands 95 Model, definition 157
List date 95 Models 16. 85
List dest 95 Modifying a host to use npd, Unix 44
List diff 96 Modifying your script, Unix 33
List ifc 96 Monitoring a print queue using FTP 133
List key 96
List logins 96
List Iogpath 96
List model 97 N
List pserver 97 NCSA print method 51
List rprinter 97 Net use printing method, NetBIOS 78

EUwmet Print Server User's Manual

Net use, NetBIOS 75 Office addresses 183
NetBIOS configuration 73 onlcr definition 157
NetBIOS features 13 Operating logic, print server 17
NetBIOS problems 148 Optimizing the print server's services 120
NetBIOS, definition 157 Options 117
Netmask definition 157 OSI definition 157
Netname definition 157 Other TCP/IP print methods 51
NetWare4 58 Output processing, definition 157
NetWare 4 options 63
Network path not found 148
Network security 119, 124
Newsprint 46, 157 P
NIT 157 PAP definition 157
Notation conventions 180 Papname definition 157
Novell configuration 53 Parity definition 158
Novell features 12 Password security, Novell 126
Novell options 126 PCONSOLE session 170
Novell print methods 176 Ping 100
Novell print server installation 170 Ping definition 158
Novell problems 143 Pio file 158
npconfig 22 Planning your print setup 175
npconfig definition 157 Plot files and PostScript file printing 159
npconfig installation program, Unix 21 Poa numbers 151
npconfig method, compiling 20 Postscript option 67
npconfiglezsetup Main menu 21 Pre-Netware 4 58
npd advantagesldisadvantages 176 Print jobs, security 177
npd definition 157 Print server architecture 15
npd locks, Unix 43 Print server configuration 23
npd overview, Unix 42 Print server configuration, AppleTalk 68
npd pseudo-device interface 42 Wnt s m e r configuration, NetBIOS 77
npr.if interface script 32 Print server configuration, Novell 56
npr.if interface script, Unlx 32 Print server configuration, Unix 23
npscramble definition 157 Print server features 12
Npsh 122 Print server FTP file system 131
npsh 157 Print server operating logic 17
Basic commands 92 Print setup considerations 176
basic commands 92 Print setup, Planning 175
Commandset 93 Printer connection 168
Overview 90 Printer feedback 120
Prompt 90 Printing a file using FTP 132
npsh.exe 54 Printing both plot files and Postscript files 159
npwrite 31 Printing problems, Novell 144
npwrite definition 157 Printing related problems, TCP/IP 141
Printing via the spooler, Unix 32
Processing options
Advantagesldisadvantages 177
0 Location of 176
OcB Offices 183 Product variables 128

190 Ethernet Print Sewer User's Manual

Summary 17
Sun Newsprint 46
SunPics 157
UDP definition 159
Supervisor 115
Unexpected network error 148
Switchable 159
Unix configuration 19
Switchabledefinition 159
Unix print server installation 169
SYSLOG port number 151
User accounts and permissions 91
SYSLOGD definition 159
Using different naming schemes 119
System V Unix 39
Using npd and your own script, Unix 34
System variables 128

T v
Variable definitions 150
Tab 159
Variables 86
Tab expansion definition 159
Default settings 150
Tab expansion, Advantagesldisadvantages 177
MIS 127
Tar definition 159
Product 128
TCP definition 159
System 128
TCP port, definition 159
TCP/IP definition 159
TCPIIP features 13
TCPnP on Windows workstations, NetBIOS 74
TCPflP options 122 W
TCPIIP other print methods 51 WARNING message 25
TCPIIP port numbers 151 WfW definition 159
TCPnP print methods 176 Windows 95
TCP/IP Problems 140 Host configuration 81
TCPnP problems 140 Windows configuration 172
TCPnP Unix configuration 19 Windows for Workgroups
Telnet 116 Host configuration 80
Definition 159 Windows for workgroups, NetBIOS 76
Error 141 Windows NT
Port number 151 Host configuration 78
Terminal configuration, Unix 28 Windows NT 4
Terminal server capabilities 125 Host configuration 8 1
Testing npd 44 Windows NT Version 3.5 75
Testing npd, Unix 44
Trailer string, definition 159
Transcript 47
Transcript definition 159 X
Traps, MIB 128 xtab definition 159
Troubleshooting 139

192 Ethernet Print Sewer User's Manual