The information in this guide may change without notice. The manufacturer assumes no responsibility for any
errors which may appear in this guide.
OKI, OkiLPR and OkiLAN are registered trademar ks of Oki Ele ct ric Ind ustry Company, Ltd. DEC,
thickwire, thinwire, VMS, VT100, and ULTRIX are trademarks of Digital Equipment Corporation. UNIX is
a registered trademark of The Open Group. Ethernet is a trademark of XEROX. NetWare is a trademark of
Novell Corp. AppleTalk, Chooser, and Macintosh are trademarks of Apple Computer Corp. Windows NT
and Windows for Workgroups are trademarks of Microsoft Corporation. Portions copyright 1989, 1991, 1992,
1993 Regents of the University of California. All rights reserved. Used with permission. Portions of this work
are derived from the Standard C Library, copyright 1992 by P.J. Plauger, published by Prentice-Hall, and are
used with permission.
Copyright 2002. All rights reserved. No part of the contents of this book may be transmitted or reproduced
in any form or by any means without the written permission of the manufacturer.
About this Manual
This manual is organized in the following chapters and appendices:
Chapter 1Introduction
This chapter describes the functionality and physical characteristics of the Ethernet Network Interface Card
(NIC).
Chapter 2Ethernet Network Interface Configuration
This chapter will familiarize you with the configuration requi rements for your NIC in a variety of different
environments to include AppleTalk, Local Area Transport (LAT), Netware and TCP/IP.
This chapter describes the functionality and physical characteristics of the Ethernet Network Interface Card
(NIC).
Product Description
The Ethernet Network Interface Card (NIC ) is an internal multiprotocol print server that provides shared
network access to the printer for a variety of network protocols and operating systems. The NIC supports
the following protocols: TCP/IP, AppleTalk (EtherTalk), Local Area Transport (LAT), and IPX (NetWare).
The NIC can queue multiple pending jobs and service those jobs in the order that they are received from the
hosts.
Physical Characteristics
The front panel of the Ethernet NIC has a TEST/RESET button and four LEDs. The NIC supports
10BasetT and 100BaseT using an RJ45 connector for shielded and twisted pair standard Ethernet cabling.
3
2
4
1
5
6
NumberDescription
1TEST/RESET button - when pressed briefly while powering up the unit, returns
the NIC to its original factory default configuration.
2NIC LED - blinks yellow quickly at power on and slowly during normal operation
to show unit is functioning.
3BNC - Lights solid green to when a valid BNC network is attached to the NIC.
4RJ45 port - for 10Base-T or 100Base-T network connections.
5NET LED - blinks yellow to reflect network activity.
6BASE-T LED - lights solid green to indicate a valid 10Base-T or 100Base-T
connection.
NOTE:Once installed, the Ethernet NIC will automatically sense the network connection and will
automatically configure the RJ-45 connection accordingly.
Protocols Supported
The following protocols are supported by your Ethernet NIC:
This chapter will familiarize you with the configuration requirements for your NIC in a variety of different
environments to include AppleTalk, Local Area Transport (LAT), Netware and TCP/IP.
Control Panel Settings
When you install network options in the network card slots 1 and 2, the Network 1 and Network 2 control
panel submenus appear within the Interface Menu. The interface submenu contains the settings relevant to
the data input sources, interpreter selection, etc.
Menu
Paper Menu
Interface Menu
Port
Parallel Setup
Serial Setup
Network 1 Setup
Network 2 Setup
PS Menu
PCL Menu
System Menu
Quality Menu
Functions
Flash Menu
Disk Menu
Net 1 Setup
This menu selection is used to configure the printer’s Net 1 port.
NOTE:This entire Net 1 Setup menu tree is only visible when an optional network interface is installed in
the Net 1 slot.
AVAILABLE SELECTIONSINTERPRETER
AUTO SWITCH (see Notes 1 and 3 below)
PCL
POSTSCRIPT 3
3. If AUTO SWITCH is selected the FORMAT selection will automatically be RAW.
4. This is the MAC—the factory-set network address.
5. This is a free format entry that requires your input.
•The NIC’s IP address must be configured before any TCP/IP functionality is available. See “Setting
the IP Address” on page 2-11.
•There are two important passwords on the NIC: the privileged password and the login password.
Changing any server, service, or port setting requires privileged user status. The default privileged password
is system.
The login password is required for remote console logins. The default login passw ord is access.
NOTE:If you would like to change either the privileged or login password, use EZWebCon.
EZWebCon Configuration
The EZWebCon configuration software is the recommended way to configure the NIC. EZWebCon is a
graphical user interface which guides first time users through the initial configuration process and allows
experienced users to update and change any configurable parameters.
The EZWebCon software is located on the CD-ROM that came with your printer and is installed from the
Menu Installer. For assistance once EZWebCon is running, refer to the EZWebCon on-line help.
Incoming Logins
Incoming logins made via EZWebCon can be used to configure the server. Incoming LAT and TCP/IP logins can also be made using LAT and TCP/IP commands.
Incoming Telnet connections are enabled by default. To change this setting, use the Define Server Incom-ing command.
Incoming logins do not prompt for a login password; therefore, you may wish to disable them. If it is undesirable to disable incoming logins, the Server can be configured to prompt for a password with the Define Server Incoming Password Enabled command.
Services
With few exceptions, a service must be created before print queues can be configured on the NIC. A service
is a resource accessible to network hosts. The following 2 default services are available once the NIC has
booted:
PRQ_xxxxxx_TEXTUsed for text print jobs
PRQ_xxxxxx_BINUsed for binary print jobs, such as plotter, PCL or PostScript files.
NOTE:The default service names based on the NIC’s server name (PRQ_xxxxxx), with the x’s being the
last six digits of the NIC’s Ethernet address. The se rvice names m ust b e no more than 13 ch arac ters.
For LPR the default queue names of PRQ_TEXT, PRQ_BIN can be used.
Identifying the EtherNet Host Name
T o identify the EtherNet host name , you m ust print a prin t server printout. Using a paper -clip, press the print
server test button (See “Physical Characteristics” on page 1-2). The host name appears under Service as:
PRQ_xxxxxx_BIN. This name is factory set and cannot be changed.
AppleTalk Configuration
The EZWebCon configuration software is the easiest way to configure the NIC. The following sections
cover other print configuration methods for AppleTalk hosts.
NOTE:The NIC needs an IP address before you can use EZWebCon. See “Setting the IP Address” on page
2-11.
NOTE:Macintosh systems that do not support EtherTalk will need either an Ethernet card or a
LocalTalk-to-EtherTa lk router to use the NIC.
NOTE:MacOS 8.1 can also print via LPD.
Macintosh Services
Before attempting to print from a Macintosh, ensure that AppleTalk and PostScript are both enabled on at
least one service. Once the service is configured, it will appear in the Chooser in the same zone as the NIC.
Select the service in the Chooser and complete the appropriate setup options. Then close the Chooser window and print a test page of text to the Macintosh service.
AppleTalk Zones
If there is a router on the network, the NIC will appear in the default zone specified by the router. T o c hange
the default zone, enter the Define Protocol AppleTalk Zone command and reboot the printer.
If the NIC is attached to a network without an AppleTalk router, all AppleTalk devices (including the NIC)
will appear in the default zone in the Chooser.
NOTE:If no router is present on the network, the NIC will not accept AppleTalk print jobs for 60 seconds
after booting.
AppleTalk Host Troubleshooting
Area to CheckExplanation
LAT Configuration
The EZWebCon configuration software is the easiest way to configure the NIC. The following sections
cover other print configuration methods for LAT hosts.
NOTE:The NIC needs an IP address before you can use EZWebCon. See “Setting the IP Address” on page
LAT print queues can be created by printing to a port or printing to a service. Printing directly to a port
requires no NIC configuration.
NOTE:Printing directly to a port is the easiest method for printing to the NIC.
Printing Directly to a Port
1. Create a LAT application port that references the NIC port.
2-11.
The printer is available to be
Make sure the printer is in the right zone.
selected in the Chooser
$RUN SYS$SYSTEM:LATCP
LATCP> CREATE PORT LTAnnn/APPLICATION
LATCP> SET PORT LTAnnn/NODE=PRQ_xxxxxx/PORT=Port_n
LATCP> EXIT
2. Create and start a print queue that uses the LAT application port.
By default, the LA T error message codes on the host are not t ranslated i nto text error messages . If a LA T job
fails and appears in the queue with an eight-digit hex result code, the code can be translated by issuing the
following commands:
The EZWebCon configuration software is the easiest way to configure the NIC. The following sections
cover other print configuration methods for NetWare hosts.
NOTE:The NIC needs an IP address before you can use EZWebCon. See the “Setting the IP Address” on
page 2-11 for instructions.
This chapter explains creating NDS print queues with NetWare Administrator and with the PCONSOLE
Quick Setup option. To create NDS print queues, you must be running NetWare version 4.x with NDS capabilities.
If you are running NetWare versions 2.x, 3.x, or v ersion 4.x with bindery emulation, yo u ma y configure bindery print queues using QINST (bindery only) or PCONSOLE.
Configuring Your NIC
1. Define the directory service tree in which the NIC is located.
The specified node name matches the
server’s node name
The specified port name matches the port’s
name
Use the Show Server command.
Use the List Port 1 command.
Local>> DEFINE PROTOCOL NETWARE DSTREE foodco
NOTE:For an explanation of the structure of the NetWare Directory Service tree, see your host
documentation.
2. D efi ne th e di rectory service context in which the NIC is located.
4. If desired file server is not in the access list, add it.
Local>> DEFINE PROTOCOL NETWARE ACCESS fileserver
Creating Print Queues Using NetWare Administrator Quick Setup
The NetWare Administrator management utility allows you to manage network resources, suc h as
queue-based print services, in a tree structure. You can either use the Quick Setup option or individually create printing-related objects.
To create a print queue with the Quick Setup option.
NOTE:NetWare Administrator can be used for both NDS and bindery print queues.
1. Start NetWare Administrator.
2. In the Directory Tree windows, navigate to and select the context in which you want to install the
printer.
3. From the Menu B ar, select Tools: Print Services Quick Setup.
4. In the Print Server Name field, enter the name of your NIC (viewable by entering the Show Server
command at the Local> prompt).
5. In the Printer Name field, enter the name of the desired print service configured on your NIC.
6. In the Print Queue Name field, enter the name of the print queue to create. The name should be
meaningful to you; it will not affect the NIC’s configuration.
7. Click Create.
Creating NDS Print Queues Using PCONSOLE
1. Log in as Admin on the file server you will be changing.
2. Type PCONSOLE at the F: prompt to start the utility.
3. From the main menu choose Quick Set-Up.
4. PCONSOLE will prompt you for information with which to configure the print queue.
5. The print server name is the name of your NIC (PRQ_xxxxxx). The new printer nam e is the service
name (PRQ_xxxxxx_yy). The new print queu e can be any name. The print queue volume is the name
of the file server from which the printer receives print requests. The remaining fields can be left in
their default settings.
6. Press the F10 key to save the print queue information.
Use PCONSOLE to check.
match the print server and service
name
NetWare access tableScanning too many file servers can cause a delay
between jobs.Configure the access list to only scan
for jobs on the file servers of interest.
Netware Host Troubleshooting (NDS)
Area to CheckExplanation
NetWare access tableBy default, only local (non-routed) file servers are
scanned for queues.
The login password on the NIC
and the queue password on the
The passwords must match or the NIC will not be
able to log into the file servers to scan for jobs.
file server
The print server has successfully
attached to the queue
Type NETSTAT at the Local> prompt. This will
display information about fileservers, printers, and
queues that the print server has found. If a queue is
in JobPoll, the print server has successfully
attached to the queue.
The DSTree, DSContext, and
DSLicense
Type Show Protocol NetWare NDS. This command shows the tree and the context that you have
configured, a failure code, and an NDS error code
for each server.
DSTree is the directory service tree on which the
print server is located. DSContext is the context
where the print server is located; it must match the
context on the file server (The DSContext must be
of the following form: ou=fruit.0=exotic). DSLicensed should be yes.
Printer and queue changes have
propagated through the NDS tree
It may take a few minutes for the changes to propagate. If the print server doesn’t attach, reboot the
server.
NDS Printing Errors
Failure Code
Bit
Meaning
Remedy
1NIC out of memoryCycle power. Disable unused protocols and/or remove
fileservers without print queues from the NetWare
access list.
The EZWebCon configuration software is the easiest way to configure the NIC. The following sections
cover other print configuration methods for TCP/IP hosts.
The NIC provides two major methods of printing via TCP/IP: Berkeley remote LPR and RTEL host software.
4No printers found for
the NIC
5No printer queue found Ensure that the printers have associated queues.
6Login failedEnsure there is a print server object configured with the
7Authentication failedEnsure the print server login password is the same as the
8NIC cannot attach to
queue
Ensure that there are printers for the print server, and the
printer names match the service names on the print
server.
same name as the print server.
print server object password. If the print server is using
the default password (access) then there should be no
password for the print server object.
Check the NDS partitions, replicas, and volumes to
ensure the file server where the queue lives has the correct information about the NIC and printers.
To Identify the NIC’s IP Address
A configuration summary lists the server’s IP address. To print a configuration summary:
1. Press the MENU button on the printer control panel.
2. Press the NEXT button until the text “Functions” is shown on the second line of the display.
3. Press the SELECT button to enter the functions submenu.
4. Press the NEXT button until the text “Print Summary” is shown on the second line of the display.
5. Press the SELECT button to print the configuration summary page(s).
The IP address appears in column 1 under Interface Menu.
Setting the IP Address
The NIC’s IP address must be configured before any TCP/IP functionality is available.
T o set the IP address, use one of the following methods: printer’s control panel, EZW ebCon, a directed Ping
packet, a BOOTP, DHCP, or RARP reply, or commands entered at the command line (Local>) interface.
Some of these options are discussed in the following sections.
Printer’s control panel
Refer to the printer User Manual for setting the IP address via the control panel.
1. Create an entry in the host’s ARP table that contains the NIC’s IP and hardware addresses.
2. Ping the NIC. If no other node is using the IP address, the NIC will use it.
3. To save the IP address, Telnet to the NIC and use the Define Server IP address command.
Using a BOOTP, DHCP, or RARP Reply
At boot time a host-based DHCP, BOOTP, or RARP server can respond to an NIC request for an available
IP address. For information about configuring the DHCP, BOOTP, or RARP server, see the host documentation.
Notes About LPR
There are four important things to note about the LPR printing method:
1. Because of the wa y the LPR protocol is typically implemented on the host, the processing options and
banner page are sent after the job data itself. The NIC will print a banner page at the end of a job,
and cannot support most of the LPR options. If it is necessary to have the banner page at the
beginning of the printout, install and use the RTEL software. If banners are not needed, they can be
disabled.
2. The NIC cannot print multiple copies of the print job when using the “-#x” lpr option.
3. If two queues on the print host refer to two services on the same NIC, they must use separate spool-
ing directories.
4. No special purpose input or output filters can be used when printing via LPR. If this functionality is
necessary, use the named pipe interface program in the RTEL print queue configuration software.
LPR on Generic UNIX Hosts
The Berkeley remote printing system is supported on many machines, and is simple to configure.
This section describes how to configure LPR print queues on generic UNIX hosts such as SUN hosts . There
are slight variations in LPR configuration for AIX, HP, SCO, Solaris, ULTRIX, and Windows NT hosts.
After reading this section, refe r to the following sections for further configuration information.
1. Start by adding the NIC name and IP address to the
/etc/hosts file:
xxx.xxx.xxx.xxx PRQ_xxxxxx
2. Add the host print queue name into /etc/printcap, and then specify the remote node name (the host
name of the NIC) and the service name on the NIC. For example:
The punctuation shown is required, and no extra spaces should be added. This will create a host queue
named prq_prt. The rm parameter is the name of the NIC in the host's address file , the rp parameter
is the name of the service as it exists on the NIC, and the sd parameter specifies the name of a directory used to hold temporary spooling files.
4. If desired, use the mx option to allow unlimited size files to be printed and the sh option to prevent
header pages from being generated. See the host's documentation or man pages for more information
on the format of the printcap file and how to create the spool directory.
5. Print to the queue using normal lpr commands:
% lpr -Pprq_prt /etc/hosts
LPR on AIX Hosts
LPR has only been tested on AIX versions 3.2 and higher. The System Management Interface Tool (SMIT)
allows you to enable LPD printing and create print queues.
To create a print queue:
1. At the host prompt type smit.
2. Choose Print Spooling.
3. Choose Manage Print Server and Start the Print Server Subsystem (lpd
daemon).
4. In the Start the Print Server Subsystem dialog box, type both in the first field.
The message “The lpd subsystem has been started” will appear. Click Done.
To add a print queue:
1. From the main window choose Print Spooling.
2. Choose Manage Print Server and Manage Print Queues.
3. Choose Add a print queue.
4. From the dialog box that appears choose remote.
5. From the next dialog box choose Remote Printing.
6. The Add a Standard Remote Print Queue dialog box will appear. Enter the information in each
field.
A dialog box will appear with the message “Added print queue prq_prt.”
7. Print to the queue using normal lp syntax.
% lp -dprq_prt filename
LPR on HP Hosts
The System Administration Manager (SAM) allows you to create print queues.
To create a print queue:
1. At the HP prompt type sam.
2. From the main application window choose Printers and Plotters.
10. If applicable, choose Shared and select the type of operating system that the printer will be working
with. (This is not recommended until the print queue is confirmed to be working.)
11. Test the printer.
RTEL Functionality
If the LPR method of printing is not adequate for an application (for example, if you need banners before
jobs, or more flexibility), configure the RTEL software on the host. After installing the software configuring
the connections to the NIC, you can use normal UNIX print commands and queue utilities such as lpc and
lpstat.
NOTE:RTEL binaries are provided for many systems. Source code is also provided for use on
non-supported systems.
To print using special formatting or using third-par ty software packages, you may have to create “print
pipes” on the host. The RTEL software provides this functionality by providing a UNIX named-pipe
interface.
To recreate the RTEL source files:
1. Copy the file RTEL_SRC.TAR from the distribution media to the UNIX host. Ensure that a binary
copy is performed.
2. Untar the archive.
3. See the README files in the created directories that describe the contents of the RTEL distribution
and man pages that describe the actual software functionality.
Unix Host Troubleshooting
TCP Troubleshooting
Area to CheckExplanation
The NIC’s IP address and name
are entered in the host file
Jobs that appear in the host queue
reach the NIC
Telnet to the NIC using the name in the host file
and verify that the NIC name is resolvable and
that the NIC is reachable via the network.
From within the LPC administrative utility, enter
these commands to clear and reset the host
queue:
This chapter explains the procedure for installing the Ethernet Network Interface option in your printer.
Connection of the Ethernet network source cable is also discussed.
Ethernet Network Connectivity
1. Carefully review the safety precautions in the front of this guide before starting this installation proce-
dure.
2. Locate the recessed area near the top of the rear of the printer and pull on the recessed area to open
the rear cover.
3. Ensure that the printer power switch is set to the OFF [ O ] position and disconnect the power cord
Installing the Ethenet Network Interface on the Controller Assembly
NOTE:It is not necessary to remove the controller from your printer to complete the installation. For
clarity, the following illustrations depict a controller removed from the printer. When facing the
front of the controller as shown below, network port 1 is on the right and network port 2 is on the
left. However, when installed in the printer, network port 1 is on the bottom and network port 2 is on
top. In the following few steps, an Ethernet network interface is being installed in network port 2.
1. Turning thumbscrews counter-clockwise, remove the blank metal plate covering one of the available
network ports on the controller bracket.
2. While aligning the front brack e t of the NIC assembly to the two respective thumbscrews on the con-
troller assembly bracket, firmly seat the 80-pin male connector on the underside of the NIC to the
80-pin female connector on the controller assembly.
•See “PrintView Job Accounting for OKI” on page 4-3.
4-2Network Utility Software
About this Chapter
This chapter provides information on network utility software included with your printer. Load these programs from the Menu Installer on the CD.
•OkiLPR
•PrintSuperVision
•PrintView Job Accounting for OKI
Oki LPR
The Oki LPR Utility allows you to print directly to a printer on the network without a print server. It creates
an Oki Printer Port, and installs a pop-up status box so you can monitor printer status.
Oki LPR operates in Windows Me/98/95, Windows NT 4.0, Windows 2000, and Windows XP operating
systems.
How to Install
The Oki LPR Utility supports TCP/IP. Your network administrator will first need to set up an IP address
and TCP/IP properties for your printer.
1. To install the utility, insert the Oki CD1 into the CD-ROM drive.
(If CD does not AutoPlay, click Start → Run → Browse. Browse to your CD-ROM driver and d ouble-click
Install.exe, then click OK.)
The Oki LPR Utility Status Box displays the following information:
•Printers: Names of added printers (You can add up to 30 printers)
•Status: LPR Utility status (empty, connecting, sending, paused, checking status, not connected)
•Finish: Number of completed jobs.
•Queue: Number of jobs waiting to be printed.
Additional Information
For help using the Oki LPR Utility, click on HELP in the program.
PrintSuperVision
PrintSuperVision is a web-based application for managing printing devices connected to a network. PrintSuperVision provides access to networked printer data for monitoring, reporting and managing networked
printers. It provides a full range of management functions for Oki printers, and for other brands of printers
as well.
Features
•Provides real-time status of all your printers to monitor and report printer usage, manage consumables
usage and replenishment.
•Administrator interface to the system is via a standard web browser enabling you to check on printer
status and compatible multi-function devices from anywhere on the web.
•Performs initial discovery and configuration of printing devices connected to network.
•View groups of printers by list, floorplan or maps.
•Monitors devices over time, including maintenance data, and saves data for statistical reports.
•Sends mail alerts of events affecting device functionality.
•Generates reports on-screen or in XHTML, Excel and XML formats, plus Text and CSV formats.
•Integrates with Oki Data’s on-line web support.
Network Utility Software4-3
Types of Users
•Guest users, without username, can get basic information about devices, such as type, status and location of printing devices.
•Standard users, in addition to guest user information,
standard users can get information about printing resources, configure e-mail alerts, and get basic statistics reports.
•Administrators can manage devices, maps, alerts, user accounts, maintenance data, and create comprehensive
statistics reports.
PrintView Job Accounting for OKI
PrintView Job Accounting Software provides powerful job accounting features including:
•PostScript mono/color page tracking and cost accounting
•User mono/color restriction
•Paper tracking/cost
•Pre-formatte d reports
•Client/group/project charge back
Before installing PrintView, check the target computer for minimum hardware and software requirements.
The installation and configuration procedure assumes administrator security access on the server and a basic
knowledge of the Microsoft Windows
®
2000/NT 4.0 operating systems.
4-4Network Utility Software
Server
Hardware Minimum
•Intel Pentium CPU or equivalent, 266 MHz
•128 MB RAM
•1 GB free HDD space (Required to support tracking database and storage for spooled print jobs.)
•CD-ROM Drive
•SVGA 1024 x768 display adapter and monitor
Hardware, Recommended
•Intel Pentium CPU or equivalent, 500+ MHz
•256 MB RAM
•5 GB free HDD space
•CD-ROM Drive
•SVGA 1024 x768 capable display adapter and 16-bit color monitor
Operating System
1. Microsoft Windows Server NT 4.0 with Service Pack 6 and Internet Explorer 4 or later
or
2. Microsoft Windows 2000 Server with Service Pack 2 or later
or
3. Microsoft Windows XP Professional
Installed Applications
•Adobe Acrobat® 4.x or greater - full version required (Required for Print Job Accounting.)
•Microsoft Access® 2000 (Required for custom reports.)
•Internet Explorer 4.0 or later
Client
Hardware
Any hardware sufficient for the supported client environments and their requirements are listed below.
Operating System
Microsoft Windows clients
98/Me/NT 4.0 Workstation/2000/ XP
Macintosh clients
•Requires services for Macintosh installed at Server.
Network Utility Software4-5
•May require additional software/configuration to support Server authentication.
Unix clients
•Configured for print jobs using Samba or equivalent in PostScript format (using server.PPD).
•May require additional software/configuration to support Server authentication.
Other clients
Any client platform capable of submitting print jobs to, and receiving authentication from the Server.
Installing PrintView
Standard Installation
NOTE:If you are installing under Windows NT4, skip to “Windows NT4 Installation.”
1. Insert the CD that came with your printer into the CD-ROM drive. If AutoPlay is not activated, or
setup does not start automatically: Click Start/Run/Browse. Browse to your CD-ROM drive, then
double-click the file Install.exe.
2. When the Menu Installer appears , click Network Softw are/Administrativ e Tools/Job Accounting.
Follow the on-screen instructions.
3. Read all installation notes in the Readme Information dialog box before proceeding.
PrintView does not need to be on the boot drive; however, some components are installed in the system’s
registry.
When the installation process is complete, a folder named PrintView is created on the target hard drive and
shortcuts are in the Start menu.
Windows NT4 Installation
Active Directory Services
PrintView makes extensive use of Microsoft’s Active Directory technology. Windows NT4 systems do not
provide these services by default. For PrintView to run Active Directory service on a Windows NT4 legacy
system, an additional component, Active Directory Client Support, is required.
To install Active Directory support for Windows NT4 legacy systems, locate and launch the installer DSCli-
ent.exe on the PrintView CD-ROM. Follow the on-screen instructions.
Access Database Support
The Microsoft Access database may be used to create customized reports. On a Windows NT 4.0 system, an
additional component, MDAC 2.5, is required.
4-6Network Utility Software
The following dialog box appears during the installation.
1. Click OK and follow the installation process. Restart the server when the installation is complete.
2. Launch mdac_typ.exe on the CD-ROM.
NOTE:To install this component later, launch the MDAC installer manually from the installation
CD-ROM.
Launching Printview
To run the application, click Start/Programs/PrintView for OKI/Printview.
NOTE:To see the User Manual for additional information, click Start/Programs/Printview for OKI/User
Area to CheckExplanation
Physical connectionTo test a non-PostScript printer use the Test Port 1
Count 100 command. This command will send 100
lines of test data to the printer.
Service characteristicsUse the Show Service Local Characteristics
command from a network login to see if the desired
service is available and to verify that the appropriate
protocols are enabled on the service.
The IP addressThe IP address must be unique on the network. Many
problems will occur when there are duplicate IP
addresses on the network.
Queue Status and Port countersUse the Monitor Queue command to ensure queue
entries appear in the job list. If an entry does not appea r ,
refer to the appropriate host section in this Appendix.
Use the Monitor Port n Counters command to verify
that the counter is incrementing with each job. If it is
not, verify the connection between the NIC and the
printer.
BOOTP Troubleshooting
If the BOOTP request is failing and you have configured your host to respond to the request, check these
areas:
Area to CheckExplanation
BOOTP is in your system’s
/etc/services file
The NIC’s name is in the
loadhost’s
/etc./hosts file
The download file is in the
correct directory and is
world-readable
The NIC and host are in the same
IP network
BOOTP must be an uncommented line in the /etc/services
file.
The NIC’s name must b e in this file for th e host to a nswer a
BOOTP or TFTP request.
The download file must be in the correct directory and
world-readable. Specify the complete pathname for the
download file in the BOOTP configuration file or, a add a
default pathname to the download filename.
Some hosts will not allow BOOTP replies across IP
networks. Either use a host running a different operating
system or put the NIC in the same IP network as the host.
DHCP is enabled on the NIC.Use the Define Server DHCP Enabled command.
If you manually enter an IP address, DHCP is
automatically disabled.
RARP Troubleshooting
PostScript Problems
Make sure the DHCP server is
operational.
Did the NIC get its IP address from
the DHCP server?
Area to CheckExplanation
The NIC’s name and hardware
address in the host’s /etc/ethers file
The NIC’s name and IP address in
the /etc/hosts file
The operating systemMany operating systems do not start a RARP server
Check to see that the DHCP server is on and is
functioning correctly.
Refer to the DHCP Manager on your Windows
DHCP server for information about addresses
currently in use. If the DHCP server does not list
your NIC’s IP address, there many be a problem.
The NIC’s name and hardware address must be in
this file for the host to answer an RARP request.
The NIC’s name and IP ad dress must b e in this fil e
for the host to answer an RARP request.
at boot time. Check the host’s RARPD
documentation for details, or use the ps command to
see if there is an RARPD process running.
PostScript printers will silently abort jobs if they detect an error.
Area to CheckExplanation
The NIC is communicating
with the printer
To test a PostScript printer use the Test Port 1 PostScript Count 2. This command will send 2 pages of PostScript data
out the parallel port. Watch the indicators on the printer to
verify that the NIC is communicating with the printer.
If the printer is capable of bidirectional communication, use the
Test Service PRQLPSEPS_xxxxxx_PS PostScript Count 5
command. This will transfer data both to and from the printer.
Autoselection must be disabled and the printer must be
configured as a PostScript printer for this test to succeed.
Bitmap Graphics
If files that contain embedded bitmap graphics print incorrectly, it is because the bitmaps are being sent as
actual binary data and binary data cannot be printed via serial or parallel interfaces.
Most major application packages have provisions to print using either “binary postscript” (for printers connected to the network via LocalTalk) or “hex postscript” (for printers connected to the network via a serial
port or parallel port). If your application does not have this provision, ask the application vendor for an
upgrade version or “patch” that will add the “hex postscript” function.
Service CharacteristicsIssue the Show Service Characteristics command. If the
service rating is zero, the parallel port is in use. Verify
that the PostScript characteristic and appropriate
protocols have been enabled on the service.
Port CountersIf PostScript jobs appear to print but nothing comes out of
the printer, verify the amount of data sent from the host.
Issue the appropriate print command from the host
system. After the job has completed, use the Show Port 1
DEFINE SERVER BOOTP {EN|DIS}Enables or disables querying for a BOOTP
host at system boot time.
DEFINE SERVER DHCP {EN|DIS}Enables or disables querying for a DHCP host
at system boot time.
DEFINE SERVER GATEWAY ipaddressSpecifies the host to be used as a TCP/IP
gateway to forward packets between
networks. Enter an IP address.
DEFINE SERVER
INCOMING option
DEFINE SERVER IPADDRESS ipaddressSets the Server’s network IP address.
DEFINE SERVER LOADHOST ipaddressSpecifies the TCP/IP host from which the
DEFINE SERVER LOGIN PASSWORDSets a new password that will be required
DEFINE SERVER NAME “newname”Specifies a new name for the Serv er. Names
DEFINE SERVER NETWARE LOADHOST
“server”
BOTHEnables incoming LAT and Telnet
connections.
LATEnables only incoming LAT connections.
NONEDisables incoming connections.
TELNETEnables only incoming Telnet connections.
PASSWORDCauses the server to prompt for a password
for all incoming connections.
NOPASSWORDAllows connections to be established without
prompting for a password.
Server requests its run-time code.
before incoming logins are accepted. You will
be prompted for the new password (up to 6
alphanumeric characters, case-insensitive).
are restricted in length; generally a name of 11
or fewer characters is permissible.
Specifies the NetWare host from which the
Server requests its run-time code. Enter a file
server name of up to 11 characters.
DEFINE SERVER PRIVILEGED PASSWORDSets a new password that will be required for
privileged user status. You will be prompted
for the new password (up to 6 alphanumeric
characters, case-insensitive).
DEFINE SERVER RARP {EN|DIS}Enables or disables querying for a RARP host
at system boot time.
DEFINE SERVER SOFTWARE “filename”Specifies the name or path (TCP) of the