----------
X-Sun-Data-Type: text
X-Sun-Data-Description: text
X-Sun-Data-Name: text
X-Sun-Charset: us-ascii
X-Sun-Content-Lines: 25
Original Question:
>
> Has anyone tried to set it up so that you can print to a printer
> attached to a Novell network from a SC2000 running 2.3 (i don't
> think the machine matters, it's the OS)? I would prefer to add the
> printer as if it was on a remote machine.
> Summary if there's interest.
>
Many thousands and millions of thanks to Darcy Partridge at novell
for pointing me to the attached document. the title is:
NetWare NFS Bidirectional
Printing: A Configuration Tutorial
DECEMBER 1992
john
===============================================================================
John Stelling (Computer Scientist) | Anyone can act,
Naval Warfare Assessment Division | But turn out the lights and
Corona, CA | ain't no one gonna see ya
| do it ;-)
ivan@krynn.nwac.sea06.navy.mil |
===============================================================================
----------
X-Sun-Data-Type: default
X-Sun-Data-Description: default
X-Sun-Data-Name: nfsprt.txt
X-Sun-Charset: us-ascii
X-Sun-Content-Lines: 1775
NetWare NFS Bidirectional
Printing: A Configuration Tutorial
DECEMBER 1992
Milton Howard - Technical Marketing Manager
Connectivity Product Marketing
Marty Collins - Product Support Engineer
Novell Technical Support
This AppNote deals with the bidirectional printing subsystem in NetWare
NFS. This subsystem allows for printing from NetWare clients to UNIX
printers, and from UNIX clients to NetWare printers. After giving an
architectural overview of the major components, the AppNote presents a
tutorial on how to configure the NetWare NFS and UNIX host software.
Copyright ~ 1992 by Novell, Inc., Provo, Utah. All rights reserved.
No part of this document may be reproduced, stored in a retrieval system,
or transmitted in any form or by any means, electronic, mechanical,
photocopying, recording, or otherwise, without express written permission
from Novell, Inc.
Disclaimer
Novell, Inc. makes no representations or warranties with respect to the
contents or use of these Application Notes (AppNotes) or of any of the
third-party products discussed in the AppNotes. Novell reserves the right
to revise these AppNotes and to make changes in their content at any time,
without obligation to notify any person or entity of such revisions or
changes. These AppNotes do not constitute an endorsement of the third-party
product or products that were tested. Configuration(s) tested or described
may or may not be the only available solution. Any test is not a
determination of product quality or correctness, nor does it ensure
compliance with any federal, state, or local requirements. Novell does not
warranty products except as stated in applicable Novell product warranties
or license agreements.
Contents
Introduction . . . . . . . . . . . . . . . . . 5
Architectural Overview of the Printing Subsystem 6
Configuring UNIX-to-NetWare Printing . . . . . 8
Configuring the NetWare Server. . . . . . . 9
Making NetWare Print Queues Available
to UNIX Hosts. . . . . . . . . . . . . 10
Specifying Trusted UNIX Hosts. . . . . . 11
Mapping UNIX Users to NetWare Users. . . 11
Creating a NetWare Print Server. . . . . 12
Configuring the UNIX Host . . . . . . . . . 12
SunOS and Ultrix. . . . . . . . . . . . . . 13
Printcap File Format . . . . . . . . . . 13
SCO UNIX. . . . . . . . . . . . . . . . . . 15
Manually Editing the /etc/printcap File. 15
Using RLPCONFIG. . . . . . . . . . . . . 16
AIX . . . . . . . . . . . . . . . . . . . . 16
NeXT. . . . . . . . . . . . . . . . . . . . 19
HP/UX v8.07 . . . . . . . . . . . . . . . . 20
SVR4.4. . . . . . . . . . . . . . . . . . . 23
Configuring NetWare-to-UNIX Printing . . . . . 24
Configuring the Netware Server. . . . . . . 24
Naming the NetWare LPR Print Server. . . 25
Configuring UNIX Printers. . . . . . . . 25
Configuring the UNIX Host . . . . . . . . . 26
SunOS and Ultrix. . . . . . . . . . . . . . 26
SCO UNIX. . . . . . . . . . . . . . . . . . 27
Manually Editing the /etc/printcap File. 28
Using RLPCONFIG. . . . . . . . . . . . . 28
AIX . . . . . . . . . . . . . . . . . . . . 28
NeXT Mach . . . . . . . . . . . . . . . . . 30
HP/UX . . . . . . . . . . . . . . . . . . . 34
USL SVR4.4. . . . . . . . . . . . . . . . . 34
Frequently Asked Questions . . . . . . . . . . 34
Acknowledgements
We give special thanks to Keith Brown, Henry Leung, Radhika Padmanabhan,
and our Technical Publications staff for contributing to the examplers
contained in this AppNote.
Introduction
This Application Note deals with the bidirectional printing subsystem in
NetWare NFS. It starts with an architectural overview and discussion of
the major components. The remainder of the AppNote is a tutorial on how
to quickly configure the NetWare NFS software for printing between
NetWare and UNIX machines running the following UNIX variants:
- Sun's SunOS
- IBM's AIX
- DEC's Ultrix
- SCO's UNIX
- USL's UNIX System V
- NeXT's Mach
- Hewlett-Packard's HP/UX
This tutorial should be used in conjunction with the NetWare NFS
Supervisor's Guide. We assume that you have read the printing sections in
the guide and have some understanding of NetWare NFS printing. The
tutorial information in this AppNote leads you through specific examples
which show you how to configure UNIX-NetWare bidirectional printing.
The tutorial examples that follow can be analogously applied to
configuring the NetWare FLeX/IP product, but configuration within the
NetWare FLeX/IP product won't be specifically addressed in this
AppNote.
Architectural Overview of the Printing Subsystem
NetWare NFS includes a set of NLMs which, among other things,
implements the Berkeley Line Printer Daemon (LPD, RFC 1179) protocol.
LPD was developed as part of the Berkeley Software Distribution (BSD)
UNIX operating system at the University of California at Berkeley. It has
become the de facto standard remote printing protocol in a distributed
UNIX environment. LPD is implemented on top of TCP/IP and is
supported on virtually every BSD and BSD-derivative UNIX system, as
well as many AT&T System V-derived UNIX systems.
Three NetWare Loadable Modules (NLMs) make up the core component
of the bidirectional printing function within NetWare NFS:
- PLPD (LPD server)
- LPR_PSRV
- LPR_GWY (LPD client)
These NLMs allow the NetWare file server to accept print jobs from and
send print jobs to any system which supports the LPD protocol.
Configuring UNIX-to-NetWare Printing
When configuring UNIX-to-NetWare printing, you must perform actions
on both the NetWare server and the UNIX host. In this section, we will
lead you through a detailed account of how to achieve the setup depicted
in Figure 1. Example names are used for the host, printer, queue, and
directory objects. You may substitute names appropriate to your
configuration in their place.
Once you have completed the following sections entitled "Configuring the
NetWare Server" and "Configuring the UNIX Host", the UNIX host sparky
will be able to place print jobs in the NetWare print queue named
UNIX2NW on the NetWare NFS server, sjf-mktg. The print job can then
be routed to any NetWare printer. (See Figure 1 for an overview of this
setup.)
Configuring the NetWare Server
Prerequisites. Before you configure the NetWare server, make sure the
following prerequisite tasks have been performed:
- The TCPIP.NLM is loaded and configured properly.
(For information on how to do this, read the TCP/IP Transport
Supervisor's Guide included with the NetWare v3.11 documentation
set, or read a technical note entitled "NetWare TCP/IP Installation and
Configuration on a NetWare 3.11 Fileserver", published in October
1992. The latter document is available as an ASCII file named
NWTCP.TXT on NetWire in NOVLIB Lib 8.)
- The NetWare NFS software has been installed and loaded on the
NetWare file server.
(You should have completed "Section 2: Installing and Updating
NetWare NFS" in the NetWare NFS Supervisor's Guide).
- Sjf-mktg has an entry in its sys:\etc\hosts table for the UNIX host
sparky.
Procedure. There are four steps to configuring UNIX-to-NetWare
printing on the Netware server:
- Making NetWare print queues available to UNIX hosts.
Each NetWare print queue that will accept print jobs from remote
UNIX hosts must be explicitly declared. These are called exported
queues.
- Specifying trusted UNIX hosts.
Each UNIX host that will have access to NetWare print queues must be
added to the Trusted Hosts List. The PLPD NLM only accepts print
jobs from authorized remote UNIX hosts that are included on the
Trusted Hosts List.
- Mapping UNIX users to NetWare users.
Each UNIX username must be mapped to a NetWare username so that
NetWare can enforce NetWare print queue access controls.
- Creating a NetWare print server.
Each job in a print queue must be pulled out of the queue by a
NetWare print server and sent to a NetWare printer.
Making NetWare Print Queues Available to UNIX Hosts. The task
for this step is to create a NetWare print queue named UNIX2NW and
export it (that is, make it available) to UNIX hosts.
1. At the NetWare file server (sjf-mktg) console, start the PLPDCFG
utility by typing:
load plpdcfg <Enter>
The utility displays the Main Menu.
2. Highlight "Select Print Queues for use by LPD" and press <Enter> to
view the list of exported print queues. The utility displays the "Print
Queues Selected" window, which lists any print queues you have
already exported.
3. Press <Insert> to add a queue to the "Print Queues Selected" window.
The utility displays the "Available Print Queues" window.
4. Press <Insert> to create a new print queue.
The utility displays the "Create A Queue" window.
5. Type "UNIX2NW" for the name of the queue, and then press
<Enter>.
This creates a NetWare print queue (alleviating the need to use
PCONSOLE to create this queue). The queue name UNIX2NW
appears in the "Available Print Queues" window.
6. Transfer the queue name UNIX2NW from the "Available Print
Queues" window to the "Print Queues Selected" window by
highlighting UNIX2NW and pressing <Enter>.
The utility displays the "Print Queues Selected" window with
UNIX2NW included in the list.
7. Press <Esc> and save changes to return to the Main Menu. Proceed to
the next section entitled "Specifying Trusted UNIX Hosts".
Note: Instead of pressing <Esc> and returning to the Main Menu, you
could have selected UNIX2NW in the "Print Queues Selected"
window and pressed <Enter> to set printer-related job attributes
for the queue. Setting these attributes is outside the scope of this
document. For further details, refer to the section entitled
"Managing NFS Print Services: Making print queues available" in
the NetWare NFS Supervisor's Guide or the section entitled
"Managing Print Services: Making print queues available" in the
NetWare FLeX/IP Supervisor's Guide.
Specifying Trusted UNIX Hosts. Our task for this step is to authorize
the UNIX host sparky to print to any of the exported print queues~in this
case, the UNIX2NW queue.
1. If the PLPDCFG NLM is already running, go to Step 2; otherwise,
start the PLPDCFG NLM from the NetWare server console by typing
"LOAD PLPDCFG" <Enter>.
2. Choose the "Select Trusted Hosts" option and press <Enter> to specify
the UNIX systems that will be spooling print jobs to NetWare print
queues.
The utility displays the "Trusted Hosts List" window.
3. Press <Insert> to add UNIX host sparky to the list.
The utility displays the "Available Hosts" list. Available hosts are
those that are defined in the HOSTS table and that do not already
appear in the "Trusted Hosts List" window.
4. Highlight sparky and press <Enter>.
The utility removes the "Available Hosts" window and adds sparky to
the "Trusted Hosts List" window.
5. Press <Esc> to return to the Main Menu.
The utility displays a confirmation box asking if you want to save the
changes you have made.
6. Select "Yes" to save the changes you have made.
The utility displays the Main Menu. Proceed to the next section
entitled "Mapping UNIX Users to NetWare Users".
Mapping UNIX Users to NetWare Users. Our task for this step is to
set the mapping mode to convert all UNIX usernames sent with the print
job from the remote UNIX host, to the NetWare username GUEST.
1. If the PLPDCFG NLM is already running, go to Step 2; otherwise,
start the PLPDCFG NLM from the NetWare server console by typing
"LOAD PLPDCFG" <Enter>.
2. Choose the "Select Username Mapping Mode" option and press
<Enter>.
The utility displays the "Current Mode is" menu with the current
mode shown in the menu heading.
3. Select the "All Clients use same NetWare Account" option.
The utility displays the "Selected Username" window.
4. Press <Insert>.
The utility displays the "Available Usernames" window showing
available usernames.
5. Highlight Guest and press <Enter>.
The utility displays the "Selected Username" window listing the
username Guest.
6. Press <Esc> to return to the mapping mode menu.
The utility displays a confirmation box asking if you want to save the
changes you made.
7. Select "Yes" and press <Enter> to save the changes.
The utility displays the "Current mode..." menu.
8. Press <Esc> twice to exit the program.
Creating a NetWare Print Server. Our task for this step is to create
and configure a NetWare print server using PCONSOLE. We will
configure the print server to take print jobs from the UNIX2NW queue
and send them to a NetWare printer. Finally, we will start the print server
by loading the PSERVER NLM.
1. Refer to the Print Server manual included in the NetWare v3.1x
documentation set to complete the following tasks using the
PCONSOLE utility:
a. Log in to sjf-mktg and create a print server called
UNIX2NW_PSERV.
b. Add a printer to UNIX2NW_PSERV.
c. Assign the UNIX2NW queue to the configured printer.
d. Authorize the UNIX2NW_PSERV print server to service the
UNIX2NW queue.
2. To start the print server, type the following command at the file server
console:
load pserver UNIX2NW_PSERV
Configuring the UNIX Host
The NetWare NFS server uses the LPD protocol to transmit/ receive
printing-related commands and data to/from remote UNIX hosts.
Therefore, you must first determine whether your host has support for the
LPD protocol. Consider these general guidelines when determining
whether your host supports the LPD protocol:
- Berkeley Software Distribution (BSD) and BSD-hybrid UNIX
platforms will almost always have LPD support.
- System V or System V-like operating systems may or may not have
LPD support. They will occasionally have LPD support in addition to
their native network printing support.
- Non-UNIX platforms such as VMS, MVS, or VM are not likely to
have built-in support for the LPD protocol. However, there may be
third-party software that will add LPD support to these systems.
Each of the UNIX operating systems covered in this AppNote (SunOS,
HP/UX, NeXT Mach, SCO, Ultrix, AIX, and USL System V) have
support for the LPD protocol. If you do not have one of these platforms,
consult with your operating system vendor or read the network printing
section of your system administration manuals to determine whether your
host supports LPD.
Prerequisite. After satisfying the prerequisite listed below, locate the
heading for your operating system and follow the steps in that section.
- Add the name and IP address of the NetWare NFS server sjf-mktg to
the /etc/hosts file on sparky.
SunOS and Ultrix
This section assumes you are running SunOS v4.1.x or Ultrix v4.2. Any
earlier versions may not contain the same functionality as described below.
Before you proceed, verify that the LPD daemon is running on the UNIX
host by issuing the following command:
%ps aux | grep lpd
If the LPD daemon is running, you should see output similar to:
root 8389 0.0 0.0 52 0 ? IW 02:37 0:01 /usr/lib/lpd
If the LPD daemon is not running, start the daemon by logging in to the
UNIX host as root and issuing the following command:
#/usr/lib/lpd
Verify that the daemon is running by using the ps command described
above.
To start the LPD daemon automatically when the system boots, make sure
that lines similar to these exist in the /etc/rc file:
if [ -f /usr/lib/lpd ]; then
rm -f /dev/printer /var/spool/lpd.lock
/usr/lib/lpd; echo -n ' printer'
fi
Printcap File Format. Many operating systems, including SunOS and
Ultrix, use a printcap (printer capability) file, found in /etc/printcap,
to configure local and remote printing. The file has an entry for each
printer in the following format (for information on additional options, type
"man printcap" at the UNIX prompt):
printer_name1|printer_name2|printer_nameN|printer_description:\
:lp=print_device_name:rm=netware_server_name:\
:rp=netware_print_queue_name:sd=/usr/spool/spool_directory:\
:mx#file_size:rs:
- printer_name1, printer_name2, ... printer_nameN are
arbitrary names used by UNIX users to refer to this printer.
- printer_description is an arbitrary text string used to describe the
printer in more detail (for example, "Laser printer on first floor").
- print_device_name is the name of a print device on the local UNIX
machine (for example, "lp=/dev/lp"). When printing to a printer on a
remote machine, print_device_name should be the null character (for
example, "lp=").
- netware_server_name is the name of the NetWare NFS server
accepting print jobs. This should be the same name that is listed in the
/etc/hosts file on the UNIX host for the NetWare NFS server.
- netware_print_queue_name is the name of the remote NetWare
print queue. This entry is not case sensitive.
- spool_directory is the name of the spool directory on the local
UNIX machine. This is where print jobs are temporarily stored before
they are printed. You must manually create this directory (for example,
as root, type at the UNIX prompt "mkdir /usr/spool/ spool_directory").
It is customary to give spool_directory the same name as the
netware_print_queue_ name.
- file_size is the maximum file size (measured in blocks) which can
be spooled to the printer. If file_size = 0, a file of unlimited size may
be spooled to the printer.
- rs indicates that remote users may use this printer only if they have a
local account on the system. The absence of the "rs" parameter in the
printcap entry indicates that any remote user on a "trusted host" has
permission to use this printer.
Procedure. To configure sparky so that users can spool print jobs to the
UNIX2NW print queue on the NetWare NFS server (sjf-mktg), do the
following:
1. Login to sparky as root.
2. Using a text editor, add this entry to the /etc/printcap file:
batman|robin|Printer in the marketing lab:\
:lp=:rm=sjf-mktg:\
:rp=unix2nw:sd=/usr/spool/unix2nw:
3. At the UNIX prompt, type "mkdir /usr/spool/unix2nw".
4. Try printing to the NetWare printer by issuing the following
command:
lpr -Pbatman filename
or
lpr -Probin filename
5. Examine the UNIX2NW queue on sjf-mktg by issuing the following
command:
lpq -Pbatman
or
lpq -Probin
SCO UNIX
SCO's TCP/IP versions prior to 1.2 do not have LPD printing support and
therefore you must use an alternative method for spooling print jobs to
NetWare queues. Here are a couple of workarounds to this limitation:
Make "rsh" calls from the SCO machine to a UNIX machine that
supports LPD. (See Appendix F of the NetWare NFS Supervisor's
Guide for a full explanation of this method.)
Run scripts on the SCO machine which provide fundamental printing
support for spooling jobs to NetWare print queues. These scripts and
associated documentation are provided by Novell and are located on
NetWire in a downloadable file named NFS117.ZIP in the 08 forum.
These scripts only allow printing from SCO UNIX to NetWare, not
from NetWare to SCO. If you need NetWare to SCO printing, you will
have to upgrade your SCO UNIX system to the level that supports
LPD.
Neither of these alternative methods is recommended. We suggest that you
upgrade to SCO's TCP/IP v1.2 implementation which supports the LPD
protocol. If you have TCP/IP v1.2, you can use the following procedure
for spooling jobs to NetWare print queues.
Prerequisites. Before you proceed, see that the following prerequisites
are met:
- Install SCO TCP/IP v1.2.
- Configure Remote Line Printing.
As root, type "mkdev rlp" at the UNIX prompt and follow the on-line
instructions. (Refer to SCO documentation for more information on
"mkdev rlp").
- The name and IP address of the NetWare NFS server sjf-mktg is in the
/etc/hosts file on sparky.
Procedure. There are two ways to configure UNIX-to-NetWare printing
on the SCO operating system. One method is to edit the /etc/printcap
file manually. The other method is to run the RLPCONFIG utility which
prompts for input and then updates the appropriate entries in the
/etc/printcap file. Instructions for both methods are given below.
Manually Editing the /etc/printcap File. For an explanation of the
format of the /etc/printcap file, see "Printcap File Format" in the previous
section.
1. Login to sparky as root.
2. Using a text editor, add this entry to the /etc/printcap file:
batman|robin|Printer in the marketing lab:\
:lp=:rm=sjf-mktg:rp=unix2nw:\
:sd=/usr/spool/unix2nw:
3. At the UNIX prompt, type "mkdir /usr/spool/unix2nw".
4. Try printing to the NetWare printer by issuing the following
command:
lp -dbatman filename
or
lp -drobin filename
5. Examine the UNIX2NW queue on sjf-mktg by issuing the following
command:
lpstat batman
or
lpstat robin
Using RLPCONFIG. Complete the following steps to configure the
printcap file using the RLPCONFIG utility.
1. Login to sparky as root.
2. At the UNIX prompt, type "rlpconf". Answer the program's prompts
as follows:
a. "Remote Printing Configuration"
Enter information for remote printers or local printers accepting
remote printing requests.
b. "Please enter the printer name (q to quit):" <-- unix2nw
c. "Is unix2nw a remote printer or a local printer (r/l)?" <-- r
d. "Please enter the the name of the remote host that unix2nw is
attached to:" <-- sjf-mktg
e. "Printer unix2nw is connected to host sjf-mktg.
Is this correct? (y/n)" <-- y
f. "Would you like this to be the system default printer? (y/n)" <-- n
g. The program displays information similar to this:
Make sure your host name appears in sjf-mktg's
/etc/hosts.equiv or /etc/hosts.lpd file
Make sure that unix2nw appears in sjf-mktg's
/etc/printcap file (BSD format)
Make sure that unix2nw has a spool directory on
sjf-mktg
Putting unix2nw in printer description file and
creating spool dir...done
Updating LP information...done
3. Try printing to the NetWare printer by issuing the following
command:
lp -dunix2nw filename
4. Examine the UNIX2NW queue on sjf-mktg by issuing the following
command:
lpstat unix2nw
AIX
This section assumes you are running IBM's AIX v3.x. Any earlier
version may not contain the same functionality as described below.
Prerequisite. Before you proceed, make sure the name and IP address
of the NetWare NFS server sjf-mktg is in the /etc/hosts file on sparky.
Procedure. AIX supports LPD. Instead of using the /etc/printcap
file for configuration, AIX uses an interactive utility called SMIT to
configure printing. To configure printing using SMIT, do the following:
1 Login to sparky as root.
2. Invoke the SMIT utility by typing:
AIX> smit <Enter>
3. To add a remote queue, select the following options from the SMIT
menu:
Spooler (Print Jobs and Printers)
Manage Remote Printer Subsystem
Client Services
Remote Printer Queues
Add a Remote Queue
A form appears asking you to define a remote print queue.
4. Enter information into the following fields as described. All other
fields should use the default value.
a. "NAME of queue to add" <-- batman
This is the name of the local print queue. Print jobs sent to this
queue are passed to the NetWare print queue. Must be seven
characters or less.
b. "DESTINATION HOST for remote jobs" <-- sjf-mktg
This is the name of the NetWare Server. This hostname must also
be contained in the /etc/hosts file.
c. "Name of QUEUE on remote printer" <-- unix2nw
This is the name of the NetWare queue exported by using the
PLPDCFG.NLM. Must be seven characters or less.
d. "NAME of device to add" <--Give an arbitrary name (for
example, lpdev)
This is a device name required by AIX, but this name has no
affect on the UNIX-to-NetWare print service. Enter any name of
seven characters or less. The name does not need to be an
existing device, nor does it need to be unique.
5. Start the lpd subsystem with SMIT:
Spooler (Print Jobs and Printers)
Manage Remote Printer Subsystem
Server Services
lpd Remote Printer Subsystem
Start Using the lpd Subsystem
Start BOTH Now and at System Restart
6. Start the qdaemon by typing:
AIX> startsrc -s qdaemon
7. Try printing to the NetWare printer by issuing the following
command:
AIX> lpr -Pbatman filename
8. Examine the UNIX2NW queue on sjf-mktg by issuing the following
command:
AIX> lpq -Pbatman
or
AIX> enq -q -Pbatman
Troubleshooting. If you have any problems printing to a NetWare
printer, try the following procedures.
1. Check the local QUEUE setup with SMIT as follows:
AIX> smit <Enter> (start smit)
Spooler (Print Jobs and Printers)
Manage Local Printers, Queues, and Queue Devices
Manage Local Printer Subsystem
Local Printer Queues
Change / Show Characteristics of a Queue
Highlight "batman" and press <Enter>. Check the names assigned to
the following items:
Current name of queue <-- batman
DESTINATION HOST for remote jobs <-- sjf-mktg
Name of QUEUE on remote printer <-- unix2nw
2. Stop and start the local QUEUE.
AIX> enq -Pbatman -D(stop QUEUE)
AIX> enq -Pbatman -U(start QUEUE)
3. Stop and start the lpd remote printer subsystem.
AIX> stopsrc -c -s lpd (stop lpd)
AIX> startsrc -s lpd (start lpd)
4. Verify that qdaemon is running by typing:
AIX> lssrc -s qdaemon
If "Status" is "active," go to Step 5. If "Status" is "inoperative," start
qdaemon by issuing the following command:
AIX> startsrc -s qdaemon
5. Check /usr/lpd/stat for device creation. You should see a file
with a name similar to "s.batman.(device name)".
6. Check /usr/lpd/qdir for queued files.
7. Check /usr/spool/qdaemon for temporarily spooled files.
8. Check /usr/lpd/qconfig for correct remote printer creation and
configuration. You should see an entry in this file that looks like this:
batman:
device = lpdev
up = TRUE
host = sjf-mktg
s_statfilter = /usr/lpd/aixshort
l_statfilter = /usr/lpd/aixlong
rq = unix2nw
NeXT Mach
You can configure the NeXT workstations that are connected to printers in
one of two ways: either as standalone machines or as part of a NetInfo
domain network.
- For a standalone machine, you need to configure the printcap file and
printcap NetInfo database on each NeXT machine. This applies to each
client (DOS, Windows, OS/2, or Macintosh).
- For a NetInfo network, you only need to configure the master printcap
NetInfo database for each pertinent domain.
Procedure. Login as root and complete these steps either on the
standalone workstation or on the server in each NetInfo domain, depending
upon the applicable setup:
1. Add the NetWare server name and IP address to the NeXT's hosts
database. You can accomplish this in one of two ways:
a. Use the NeXT "NetManager" application.
1) Select the "new" option from the "host" menu.
2) Complete the form presented on screen. Do not click the
"Host Runs NetInfo" check box for the NetWare server entry.
3) Select "save" from the "host" menu.
b. Or, edit the hosts file and update the NetInfo database.
1) Edit the /etc/hosts file manually by typing in the server
name and IP address.
2) Update the local NetInfo database by typing the following
command:
niload hosts . < /etc/hosts
Note: The NetInfo database for the master would be the entire
domain.
2. Using a text editor, add this entry to the /etc/printcap file (for an
explanation of the format of the /etc/printcap file, see the section for
SunOS and Ultrix above):
batman|robin|Printer in the marketing lab:\
:lp=:rm=sjf-mktg:rp=unix2nw:sd=/usr/spool/unix2nw:
3. At the UNIX prompt, type "mkdir /usr/spool/unix2nw".
4. Update the NetInfo printcap database for either the local machine, or
(if this is a NetInfo master) the entire domain, by executing the
following command:
niload printcap . < /etc/printcap
5. Type the names and IP addresses of the workstations from one of the
following categories into the NetWare server's hosts file:
- Each standalone NeXT workstation that you have configured.
- Every NeXT workstation in the domain(s) of every master
NetInfo server that you have configured.
6. Add the name of each NeXT workstation to the list of LPD trusted
hosts by following the instructions in the previous section entitled
"Specifying Trusted UNIX Hosts".
7. You can now spool print jobs from all of your configured NeXT
workstations or every NeXT workstation in configured domains to the
NetWare server.
8. Try printing to the NetWare printer with the following command:
lpr -Pbatman filename
or
lpr -Probin filename
9. Examine the UNIX2NW queue on sjf-mktg by issuing the following
command:
lpq -Pbatman
or
lpq -Probin
HP/UX v8.07
This section assumes you are running HP/UX v8.07. Any earlier version
may not contain the same functionality as described below.
Prerequisites. Before you proceed, make sure the following
prerequisites are met:
- The name and IP address of the NetWare NFS server sjf-mktg is in
the /etc/hosts file on sparky.
- Make sure the rlp process is not running by typing:
%ps -e | grep rlp
If rlp is not running, you will not see any output after executing this
command.
If rlp is running (that is, if you see output after executing this
command), kill the process with the command:
#kill -15 process_number
- Make sure the following entry is in the /etc/inetd.conf file:
printer stream tcp nowait root /usr/lib/rlpdaemon
rlpdaemon -i -1
If the rlp daemon is not running when a print request is made, this
entry in /etc/inetd.conf "tells" inetd to auto-start the rlp
daemon to service the pending print request. This is helpful if the
daemon died or was terminated for some reason. For more
information on inetd or /etc/inetd.conf, type "man inetd" or
"man inetd.conf".
- Make sure the following entry is in the /etc/services file:
printer 515/tcp spooler
- Start inetd by typing:
#/etc/inetd -c
Procedure. HP/UX uses an interactive utility called SAM to configure
printing. To configure printing using SAM, do the following:
1. Login to sparky as root.
2. Invoke the SAM utility by typing:
HP> sam <Enter>
3. Select the following options from the SAM menu:
Peripheral Devices ->
Printers and Plotters ->
Add a Remote Printer ...
A form appears asking you to define a remote printer.
4. Enter information into the following fields as described.
a. "Printer name" <-- batman
This is the name of the printer as referenced by the local HP
machine. Print jobs sent to this printer are passed to the NetWare
print queue.
b. "Remote system name" <-- sjf-mktg
This is the name of the NetWare Server. The name must also be
in the /etc/hosts file.
c. "Remote printer name" <-- unix2nw
This is the name of the NetWare queue exported by
PLPDCFG.NLM. The HP/UX LPD directs all print jobs to this
queue.
d. "Remote cancel model" <-- rcmodel
Used for remote printer job removal.
e. "Remote status model" <-- rsmodel
Used for remote printer queue status.
f. "Make this the system default printer? (y or n)" <-- n
g. "Printer class" <-- (optional)
h. "Restrict cancel? (y or n)" <-- (optional)
i. "Remote printer on a BSD system? (y or n)" <-- y
Tells the HP/UX system that it is communicating with a Berkeley
style remote printer (such as LPD).
5. Select "Perform Task" from the SAM menu.
6. Enable the printer you just created using SAM.
Peripheral Devices ->
Printers and Plotters ->
Enable a Printer ...
A form appears asking you to enter the name of the printer to enable.
7. "Printer name:" <-- batman
8. Start the LP request scheduler by typing:
#/usr/lib/lpsched
9. Try printing to the NetWare printer with the following command:
lp -dbatman filename
Or, to print the file without the banner page:
lp -dbatman -onb filename
10.Examine the UNIX2NW queue on sjf-mktg by issuing the following
command:
lpstat batman
SVR4.4
This note assumes you are running System V version 4 release 4 from
either AT&T, UNIX System Laboratories (USL), or from some other
vendor that supports SVR4.
Prerequisites. Before you proceed, make sure the following prerequisites
are met:
- The name and IP address of the NetWare NFS server sjf-mktg is in
the /etc/hosts file on sparky.
- Make sure the port monitor is running by typing:
pmadm -l -p tcp -s
If the port monitor is ready to accept printer service requests over
your network, you should get output similar to the following:
PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC>
tcp listen 0 - root\x02000ACE823904D5 - c -
/usr/lib/saf/nlps_server
#NLPS SERVER
tcp listen lp - root- - - - /var/spool/lp
/fifos/listenS5
#NLPS SERVER
Verify that there is a SVCTAG="0" and a SVCTAG="lp". If this is
not the case, consult the system administrator's manual for instructions
on how to start the port monitor.
Procedure. To configure printing for SVR4.4, complete the following
steps.
1. Login to sparky as root.
2. Register the remote system, sjf-mktg, with the local LP print service
and define the way they will communicate. Configure LP to print to a
BSD-type printer on the NetWare server sjf-mktg with retry set to 5
and timeout set to 10:
lpsystem -t bsd -R 5 -T 10 sjf-mktg
(For more information on the -R and -T options, type "man lpsystem"
at the UNIX prompt.)
3. Create a UNIX queue called batman that points to the NetWare host
sjf-mktg with the NetWare queue UNIX2NW. The "-I" parameter
allows PostScript, simple and troff file formats.
"lpadmin -p batman -s sjf-mktg!unix2nw -I
simple,postscript,troff"
4. Enable queuing by typing:
enable batman
5. Accept print requests by typing:
accept batman
6. Stop and start the LP scheduler.
#/usr/sbin/lpshut (stop the scheduler)
#/usr/lib/lp/lpsched(start the scheduler)
7. Try printing to the NetWare printer with the following command:
lp -d batman filename
Or, to print the file without the banner page:
lp -d batman -o nobanner filename
8. Examine the UNIX2NW queue on sjf-mktg by issuing the following
command:
lpstat batman
Troubleshooting. If you have any trouble printing, look in the
following LP log files for clues:
/var/lp/logs/lpNet
/var/lp/logs/lpsched
Configuring NetWare-to-UNIX Printing
When configuring NetWare-to-UNIX printing, you must perform actions
on the NetWare server and the UNIX host. This section leads you through
a detailed account of how to achieve the setup depicted in Figure 2.
Example names have been used for the host, printer, queue, and directory
objects. You may substitute the names appropriate to your configuration in
their place.
After completing the following sections entitled "Configuring the NetWare
Server" and "Configuring the UNIX Host", NetWare users will be able to
print to the printer named "penguin" attached to the UNIX host sparky.
(See Figure 2 for an overview of this setup.)
Configuring the Netware Server
Prerequisites. Before you configure the NetWare server, make sure the
following prerequisite tasks have been performed:
- The TCPIP NLM is loaded and configured properly.
(For information on how to do this, read the TCP/IP Transport
Supervisor's Guide included in the NetWare v3.11 documentation set,
or read a technical note entitled "NetWare TCP/IP Installation and
Configuration on a NetWare 3.11 Fileserver", published in October
1992. The latter ASCII document is available as an ASCII file named
NWTCP.TXT on NetWire in NOVLIB Lib 8.)
- Sjf-mktg has an entry in its sys:\etc\hosts table for sparky.
Procedure. There are two steps to configuring NetWare-to-UNIX
printing on the Netware server:
- Naming the NetWare LPR Print Server.
You must assign a descriptive name to the NetWare LPR Print Server.
- Configuring UNIX printers.
For each UNIX printer you intend to use, you must give its descriptive
name, the name of the UNIX host that the printer is attached to, the
name of the printer as referenced by the UNIX host, and a list of
NetWare print queues which are to be serviced by this printer.
Naming the NetWare LPR Print Server. Our task for this step is to
assign an arbitrary but descriptive name to the NetWare LPR Print Server.
If this was done during NetWare NFS installation, complete Steps 1
through 3 and proceed to "Configuring UNIX Printers".
1. At the NetWare file server console, type:
load nfsadmin <Enter>
The utility displays the Main Menu
2. Select "Configure NFS Tables" from the main menu. The
Configuration menu appears.
3. Select "Print Gateway" from the menu. If a print server has not been
defined for use with the LPR_SRV.NLM on the NetWare server, the
utility displays a window in which you can type a name for the print
server.
4. Type "NW2UNIX_PSERVER" for the name of the Print Server and
press <Enter>. The utility displays the "Configured UNIX Printers"
table to show the UNIX printers that have been configured. Proceed to
the section entitled "Configuring UNIX Printers".
Configuring UNIX Printers. Our task for this step is to configure the
LPR Print Server to route print jobs from the NW2UNIX queue to the
printer named penguin attached to sparky.
1. Press <Insert> to add an entry to the list of configured printers. The
utility displays the Printer Name entry box with a unique printer name
filled in.
2. Type "UNIX printer attached to sparky" as the name for the UNIX
printer and press <Enter>. The name you type overwrites the unique
name that the utility filled in. The utility displays the "UNIX Printer
Setup Options" form. The items you need to configure are identified
with the entries <not configured> and <none>.
3. Highlight the "UNIX Host Name" field and press <Enter>. The utility
displays a list of UNIX hosts that have been entered into the HOSTS
table.
4. Highlight "sparky" and press <Enter>. The utility adds "sparky" to the
"UNIX Host Name" field.
5. Type "penguin" in the "UNIX Printer Name" field and press <Enter>.
The utility moves to the "NetWare Queues" field.
6. Press <Enter> to select the NetWare queues that will receive print jobs
for this printer. The utility displays the "Assigned NetWare Queues"
list; the list is empty.
7. Press <Insert>. The utility displays a list of available NetWare print
queues.
8. Press <Insert>. The utility displays the "Create Queue" window.
9. Type "nw2unix" for the name of the new print queue and press
<Enter>. The name of the queue appears in the "Available NetWare
Queues" window.
10.Highlight "nw2unix" and press <Enter>. NW2UNIX now appears in
the "Assigned NetWare Queues" window.
11.Press <Esc> five times to exit from the NFSADMIN utility. The
utility asks you to confirm that you want to exit.
12.Select "Yes" to exit the utility.
Important: After completing the next section, "Configuring the UNIX
Host", you will need to unload and then reload the LPR_PSRV and
LPR_GWY NLMs. This makes LPR_GWY aware of the changes you
just made and causes it to establish a connection with sparky. To
accomplish this, type "unload lpr_gwy" and "unload lpr_psrv" at the
file server console; then type "load lpr_psrv" and "load lpr_gwy".
Alternatively, you can type "nfsstop" to unload all NetWare NFS
NLMs (this will interrupt NFS services); then type "nfsstart" to reload
the NLMs.
Configuring the UNIX Host
The NetWare NFS server uses the LPD protocol to transmit/ receive
printing related commands and data to/from remote UNIX hosts.
Therefore, you must first determine whether your host has support for the
LPD protocol. See the general guidelines listed previously under
"Configuring UNIX-to-NetWare Printing: Configuring the UNIX Host" to
determine whether your host supports the LPD protocol.
Prerequisite. After satisfying the prerequisite listed below, locate the
name of your operating system and follow the steps in that section.
- Add the name and IP address of the NetWare NFS server sjf-mktg to
the /etc/hosts table on sparky.
SunOS and Ultrix
This section assumes you are running SunOS v4.1.x or Ultrix v4.2. Any
earlier versions may not contain the same functionality as described below.
Prerequisites. Before proceeding, you need to verify that the LPD
daemon is running on the UNIX host. Follow the instructions given under
the previous "SunOS and Ultrix" subheading earlier in this AppNote.
Also review the format of the printcap (printer capability) file, as explained
under the subheading "Printcap File Format" earlier in this AppNote.
Procedure. To configure sparky so that NetWare users can spool print
jobs to the UNIX printer (penguin), do the following:
1. Login to sparky as root.
2. Using a text editor, add this entry to the /etc/printcap file.
penguin|joker|Printer on the second floor:\
:lp=/dev/lp:sd=/usr/spool/nw2unix:
3. At the UNIX prompt, type "mkdir /usr/spool/nw2unix".
4. Using a text editor, add the following entry to the /etc/hosts.lpd
file:
sjf-mktg
This entry allows the NetWare NFS server, sjf-mktg, to spool print
jobs to sparky.
5. Login to the NetWare NFS server and try printing to the UNIX printer
with the following command:
nprint filename /q=nw2unix
SCO UNIX
This section assumes you are running TCP/IP v1.2 on the SCO machine.
You must have TCP/IP v1.2, which supports LPD, to do
NetWare-to-UNIX printing. Prior versions of TCP/IP do not support LPD
and do not allow Netware-to-UNIX printing.
Prerequisites. Before you proceed, see that the following prerequisites
are met:
- The name and IP address of the NetWare NFS server sjf-mktg is in the
/etc/hosts file on sparky.
- Install SCO TCP/IP v1.2.
- Configure Remote Line Printing.
As root, type "mkdev rlp" at the UNIX prompt and follow the on-line
instructions. (Refer to SCO documentation for more information on
"mkdev rlp").
Procedure. There are two ways to configure NetWare-to-UNIX printing
on the SCO operating system. One method is to edit the /etc/printcap
file manually. The other method is to run the RLPCONFIG utility which
prompts for input and then updates the appropriate entries in the
/etc/printcap file.
Manually Editing the /etc/printcap File. For an explanation of the
format of the /etc/printcap file, see "Printcap File Format" in the
previous section for SunOS and Ultrix.
1. Login to sparky as root.
2. Using a text editor, add this entry to the /etc/printcap file.
penguin|joker|Printer on the second floor:\
:lp=/dev/lp:sd=/usr/spool/nw2unix:
3. At the UNIX prompt, type "mkdir /usr/spool/nw2unix".
4. Using a text editor, add the following entry to the /etc/hosts.lpd
file:
sjf-mktg
This entry allows the NetWare NFS server (sjf-mktg) to spool print
jobs to sparky.
5. Login to the NetWare NFS server and try printing to the UNIX printer
with the following command:
nprint filename /q=nw2unix
Using RLPCONFIG. Complete the following steps to configure the
printcap file using the RLPCONFIG utility.
1. Login to sparky as root.
2. At the UNIX prompt, type "rlpconf". Answer the program's prompts
as follows:
a. "Remote Printing Configuration"
Enter information for remote printers or local printers accepting
remote printing requests.
b. "Please enter the printer name (q to quit):" <-- penguin
c. "Is penguin a remote printer or a local printer (r/l)?" <-- l
d. "Please enter the name of the device for penguin:" <-- lp
e. "Printer penguin uses device lp.
Is this correct? (y/n)" <-- y
The program displays information similar to this:
Putting penguin in printer description file and
creating spool dir...done
3. Using a text editor, add the following entry to the /etc/hosts.lpd
file:
sjf-mktg
This entry allows the NetWare NFS server (sjf-mktg) to spool print
jobs to sparky.
4. Login to the NetWare NFS server and try printing to the UNIX printer
with the following command:
nprint filename /q=nw2unix
AIX
This section assumes you are running AIX v3.x. Any earlier version may
not contain the same functionality as described below.
Prerequisites. Before you proceed, see that the following prerequisites
are met:
- The name and IP address of the NetWare NFS server sjf-mktg is in the
/etc/hosts file on sparky.
- A NetWare user must have an account on AIX before the user can
print to printers attached to AIX. Also, the AIX username must be the
same as the corresponding lowercase, converted NetWare username.
For example, AIX username = "milton" and NetWare username = "MILTON".
Procedure. AIX supports LPD. Instead of using the /etc/printcap
file for configuration, AIX uses an interactive utility called SMIT to
configure printing. To configure printing using SMIT, do the following:
1. Login to sparky as root.
2. Invoke the SMIT utility:
AIX> smit <Enter>
3. To add a local queue, select the following options from the SMIT
menu:
Spooler (Print Jobs and Printers)
Manage Local Printers, Queues, and Queue Devices
Manage Local Printer Subsystem
Local Printer Queues
Add a Local Queue
A form appears asking you to define a local print queue.
4. Enter information into the following fields as described. All other
fields should use the default value.
a. "NAME of queue to add" <-- penguin
This is the name of the local print queue. This name was also
assigned to the UNIX printer when you configured the
NetWare-to-UNIX print gateway. The name must be seven
characters or less.
b. "NAME of device to add" <--Local device name (for
example, lp0)
This is a device name required by AIX for the local print queue.
You should specify the local device that is connected to your
local printer. The name must be seven characters or less.
5. Allow sjf-mktg to spool print jobs to sparky:
Spooler (Print Jobs and Printers)
Manage Remote Printer Subsystem
Server Services
Host Access for Printing
Add a Remote Host
Name of Remote HOST <--- sjf-mktg
6. Try printing to the UNIX printer with the following command
(some_AIX_username is a valid login name on the AIX host):
nprint filename /q=nw2unix /name=some_AIX_username
Note: When printing to AIX printers from NetWare, you must specify
the use of banners. This implies that you should not use the /NB
option with either CAPTURE or NPRINT. Also, you should
specify an AIX username with the /NAME= option when using
CAPTURE or NPRINT. Otherwise, the print jobs will queue up
on the AIX machine in the /usr/spool/qdaemon directory,
but the lpq command will not show these jobs and they will not
be printed.
Troubleshooting. If you have any problems printing to a NetWare
printer, try the following procedure.
1. Stop and start the local queue.
AIX> enq -Ppenguin -D(stop queue)
AIX> enq -Ppenguin -U(start queue)
2. Stop and start the lpd remote printer subsystem.
AIX> stopsrc -c -s lpd (stop lpd)
AIX> startsrc -s lpd (start lpd)
3. Stop and start the qdaemon.
AIX> stopsrc -s qdaemon(start qdaemon)
AIX> startsrc -s qdaemon(stop qdaemon)
4. Try the troubleshooting techniques listed under "AIX" for configuring
UNIX-to-NetWare printing.
If you need additional help configuring the local printer subsystem using
SMIT, consult your IBM support representative.
NeXT Mach
You can configure the NeXT workstations that are connected to printers in
one of two ways: either as standalone machines or as part of a NetInfo
domain network.
- For a standalone machine, you need to configure the printcap file and
printcap NetInfo database on each NeXT machine. This applies to each
NeXT system with a printer to be made available to any NetWare
client (DOS, Windows, OS/2, or Macintosh).
- For a NetInfo network, you only need to configure the master printcap
NetInfo database for each pertinent domain.
Procedure. Login as root and complete these steps either on the
standalone workstation or on the server in each NetInfo domain, depending
upon the applicable setup:
1. Add the NetWare server name and IP address to the NeXT's hosts
database.
You can accomplish this in one of two ways:
a. Use the NeXT "NetManager" application.
1) Select the "new" option from the "host" menu.
2) Complete the form presented on screen. Do not click the
"Host Runs NetInfo" check box for the NetWare server entry.
3) Select "save" from the "host" menu.
b. Or, edit the hosts file and update the NetInfo database.
1) Edit the /etc/hosts file manually by typing in the server
name and IP address.
2) Update the local NetInfo database by typing the following
command:
niload hosts . < /etc/hosts
Note: The NetInfo database for the master would be the entire domain.
2. Run the NeXT "PrintManager" application.
The application displays a list of configured printers along with their
corresponding types and the host name of the NeXT workstation to
which it is attached.
Note: If the printer is locally attached, this name is the same as that
of the workstation from which you are running the
"PrintManager" application. You can tell if a printer is local
or remote by clicking on each printer in turn and observing
the notice on the form. For example, for a local printer, the
words "Note: This is a local printer" appear.
3. If you are configuring a standalone NeXT workstation and printer, go
to Step 7. Otherwise, continue.
4. If you are making printers within a NetInfo domain available to
NetWare clients, you can set up the print gateway software in one of
the following two ways:
a. Configure the print gateway to send all print jobs to the master
NetInfo server machine. The server then forwards the job to the
correct printer within its domain. If you choose this method, go to
Step 5.
b. Configure the print gateway to send print jobs directly to the
NeXT workstation that has the printer specified to receive the
print job. If you choose this method, go to Step 6.
5. Run the "PrintManager" utility on the NeXT machine that is the
NetInfo master server for the domain. Write down the names of all the
printers displayed to which you wish to send print jobs. These printers
may be either locally attached to the master NetInfo server machine or
located on NeXT workstations within its domain. The "PrintManager"
utility displays the long names of each printer by default. If the
names displayed are very long or contain spaces, use the command
line utility "nidump" to see the raw printcap entries for each
configured printer, as in the following example (the trailing period is
important):
nidump printcap .
Ensure that every printer not physically attached to the master NetInfo
server, that you wish to make available to NetWare, has a printcap
entry specifying the remote machine and printer name, for example:
rm=<some_name>:rp=<some_name>
Use the NFS administration utility NFSADMIN.NLM to add each
printer in turn to the Print Gateway's list of configured printers (see
the previous section on "Configuring the NetWare Server") using the
name of the NetInfo master server as the UNIX hostname.
For example, if the NetInfo master system is called "sparky" and you
want to add two printers called "penguin" and "salmon" to the
gateway, assign the printer names as "penguin" and "salmon". The
"UNIX Host Name" should be assigned as "sparky" for both printers.
Finally, add the name of the NetWare server, sjf-mktg, to the
/etc/hosts.lpd file on the master NetInfo server machine.
Skip to Step 8.
6. Run the "PrintManager" application on the machine that is the NetInfo
master for the domain. Write down the name of the printers that you
wish to access from NetWare and the names of the NeXT
workstations on which they reside. Add the names and IP addresses of
all the workstations that have printers you wish to access to the
NetWare server's hosts database.
You can find out the IP addresses of workstations by typing the
following command (the trailing period is important):
nidump hosts .
Use the NFS administration utility NFSADMIN.NLM to add each
host-printer combination in turn to the Print Gateway's list of
configured printers (see the previous section on "Configuring the
NetWare Server"). Suppose you wish to access a printer called
"penguin" on host "sparky" and another printer called "salmon" on
host "shrimp" from NetWare. For host "sparky" and printer "penguin",
you would configure a UNIX Host Name of "sparky" and a UNIX
Printer Name of "penguin". For host "shrimp" and printer "salmon",
you would configure a UNIX Host Name of "shrimp" and UNIX
Printer Name of "salmon".
Finally, add the name of the NetWare server, sjf-mktg, to the
/etc/hosts.lpd file on every NeXT workstation that has a printer
to be made available to NetWare ("sparky" and "shrimp" in this
example).
Skip to Step 8.
7. Run the "PrintManager" application on the standalone NeXT
workstation. You will see a list of both the printers that are locally
attached and the printers that the workstation can use on remote UNIX
machines.
Examine the configuration of the locally attached printer(s). If a local
printer that you wish to access is configured as "private" then change
the access to "public" by clicking in the appropriate place. Fill in the
"Remote Name" field of the form. This is the printer name that you
will use for configuring the Print Gateway software. Make sure that
the domain of the printer is at the root level (/) so that any host can
access it. Click "OK" to save the print configuration.
Enter the name and IP address of the stand-alone NeXT workstation
into the NetWare servers host's database using the NFS administration
utility NFSADMIN.NLM. Then, use the same NLM to configure the
print gateway. If you used "penguin" as the remote name of the NeXT
printer and the stand-alone workstation is called "sparky", you would
would use a UNIX host name of "sparky" and a UNIX printer name
of "penguin".
Note: It is also possible but not "proper" to use the name by which
the NeXT workstation refers to its printer(s).
Finally, add the name of the NetWare server, sjf-mktg, to the
/etc/hosts.lpd file on the standalone NeXT workstation.
8. Login to the NetWare NFS server and try printing to the UNIX printer
with the following command:
nprint filename /q=nw2unix
HP/UX
This section assumes you are running HP/UX v8.07. Any earlier version
may not contain the same functionality as described below.
Prerequisites. Before you proceed, make sure you have satisfied the
prerequisites listed in the previous HP/UX section for UNIX-to-NetWare
printing.
Procedure. HP/UX uses an intereactive utility called SAM to configure
printing. To configure a local printer named "penguin," do the following:
1. Login to sparky as root.
2. Invoke the SAM utility by typing:
# sam <Enter>
3. Select the following options from the SAM menu:
Peripheral Devices ->
Printers and Plotters ->
Add a Local Printer ...
A form appears asking you to define a local printer.
4. Enter information into the following fields as described.
a. "Printer name" <-- penguin
b. Fill in the rest of the fields with values appropriate for your
printing environment.
5. Select "Perform Task" from the SAM menu.
6. Enable the printer you just created using SAM.
Peripheral Devices ->
Printers and Plotters ->
Enable a Printer ...
A form appears asking you to enter the name of the printer to enable.
7. "Printer name:" <-- penguin
8. Start the LP request scheduler by typing:
#/usr/lib/lpsched
9. Using a text editor, add the following entry to the
/usr/adm/inetd.sec file:
printer allowsjf-mktg
This entry allows the NetWare NFS server, sjf-mktg, to spool print
jobs to sparky.
10.Login to the NetWare NFS server and try printing to the UNIX printer
with the following command:
nprint filename /q=nw2unix
USL SVR4.4
USL SVR4.4 does not allow any machine other than another USL host to
print to its locally attached printers. Therefore you cannot do
NetWare-to-UNIX printing when the UNIX host is running USL System V.
Frequently Asked Questions
Q. How do I suppress the Banner page when doing UNIX-to-NetWare
printing using NetWare NFS v1.2?
A. If you have NetWare NFS v1.2 Rev. A, download the NFS114.ZIP
file from NetWire and apply this patch to the NetWare NFS product.
Do not apply this patch to versions after Rev. A. Specify the -h or -
J/nb switch when using the lpr command; for example, "lpr -h
filename" or "lpr -J/nb filename".
Q. How do I suppress form feeds when doing UNIX-to-NetWare printing
using NetWare NFS v1.2?
A. If you have NetWare NFS v1.2 Rev. A, download the NFS114.ZIP
file from NetWire and apply this patch to the NetWare NFS product.
Do not apply this patch to versions after Rev. A. Specify the /nff
switch in the -J option for the lpr command. For example, "lpr -J/nff
filename".
Q. How do I simultaneously suppress banner pages and form feeds when
doing UNIX-to-NetWare printing using NetWare NFS v1.2?
A. If you have NetWare NFS v1.2 Rev. A, download the NFS114.ZIP
file from NetWire and apply this patch to the NetWare NFS product.
Do not apply this patch to versions after Rev. A. Specify the /nff/nb
switch in the -J option for the lpr command; for example, "lpr
-J/nff/nb filename".
Q. When trying to print from my SCO UNIX machine, I get a message
something like "network unreachable" or "no LPR access (unknown
type)". What I have done wrong?
A. Troubleshoot using the chart below:
Q. I am successfully using Netware NFS v1.2 to do Unix-to-NetWare
printing. To date, I have only been exporting one print queue.
However, I need to add another. My initial configuration was to use
the single account mode, which is what I need for that particular
queue. Now, though, I need to set up another queue which I only want
certain UNIX users to be able to use. It seems to me that mapping
usernames is done only once, not once for each queue. Am I right? If
so, how can I get around this restriction?
A. Yes, you are right. However, there is a way to restrict use of exported
NetWare queues. You need to create a group on your UNIX host and
add the restricted group (rg) field to the printcap definition for your
NetWare printer. Only members of this group will have access to your
NetWare printer. Read your operating system documentation for more
information on the printcap file (for example, type "man printcap").
Q. I am running NetWare NFS v1.2 Rev. A. When I try to remove a
print job from a NetWare queue using the lprm command, it causes
the NetWare server to abend. How do I prevent this?
A. Download the NFS114.ZIP file from NetWire and apply this patch to
the NetWare NFS v1.2 Rev. A product.
/ \ ___________________
/ Can \ | |
/you ping \ NO | Check the TCP/IP|
\the N/W f/s ------> | configuration on|
\ from / | the NetWare |
\SCO?/ | server. |
\ / __________________
|
| YES
V
/ \ ___________________
/ Do \ | |
/ you have\ NO | Purchase it |
\ TCP 1.2 / -------> | from SCO. |
\ from / | |
\ SCO?/ | |
\ / ___________________
|
| YES
V
/ \ ___________________
/ Have\ | |
/ you \ | Read the |
/correctly set\ NO | appropriate |
\ up printing /------> | section of this |
\ on SCO? / | AppNote. |
\ / | |
\ / ___________________
|
| YES
V
___________________
| |
| Start from |
| Scratch |
| |
___________________
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:23 CDT