1. First, make sure that you have the correct connectivity to your
HP Printer or Print Server:
- Make an entry in your /etc/hosts file or DNS configuration for
your printer or print server.
- Verify connectivity by pinging the printer or print server:
# ping print_server_name
Note: This functionality is also available in option #4 of the
hpnpcfg menu included below.
- To test that you can contact the printer port(s) of the print
server that have printers physically attached:
# telnet print_server_name 9100
which should return:
Trying IP_address...
Connected to print_server_name.
Escape character is '^]'.
At this point, you can type characters that will be sent directly
to the printer on port 1. Type:
Port 1 is working
followed by "^L" and "^]"(the <Ctrl> key + L and <Ctrl> key + ])
^L
^]
telnet> quit
Note: Some printers may require an alternative form feed sequence,
"\033E". Try the following if you see the form feed button lit up
on your printer after the first attempt.
^L
\033E
^]
telnet> quit
You should see the line "Port 1 is working" printing on the JetDirect
printer or the printer attached to port 1 of the print server.
If this did not work, check your HP print server's configuration and
test your printer.
You can repeat this test for ports 2 and 3, if applicable, by using
the port numbers 9101 and 9102 in the example above.
Note: This functionality is also available for port 1 only in option 5
of the hpnpcfg menu included below.
2. Next, configure the printer(s) using either the hpnpcfg utility
or the SCOadmin Printer Manager.
hpnpcfg method:
# cd /usr/lib/hpnp
# ./hpnpcfg
This will bring up the following menu:
HP NETWORK PRINTER CONFIGURATION TASKS
MAIN MENU
1) Verify installation of software
2) Configure a printer with BOOTP/TFTP
3) Verify BOOTP/TFTP configuration
4) Verify network printer connectivity
5) Verify network printer operation
6) Add printer to spooler
7) Remove printer BOOTP/TFTP configuration
8) Remove printer from spooler
?) Help q) Quit
Please enter selection:
It is recommended to use options 4) and 5) first to verify the
printer's connectivity and operation.
Select "6" to add printer to spooler.
Enter the lp spooler destination name:
Enter the queue name you want for your printer.
Enter the network peripheral name (default= ):
Enter the name given to the print server in /etc/hosts or in your
DNS configuration.
Enter printer type: (default=unknown):
or
Enter model script name ('*' to see choices):
If you don't know the model to use for the interface name, you can
press <Enter> to accept the default for now, and select the printer
type from the SCOadmin Printer Manager later.
It is recommended to do this using the charm, not GUI, version.
The choices presented are from /usr/spool/lp/model, for example:
HPLaserJet
Another example model is /usr/lib/hpnp/hpnp.model and this can be
copied to /usr/spool/lp/model so it can be selected.
Enter context-type for printer (default=simple)
Press <Enter> to accept the default.
Enter the spooler class for the peripheral to join (optional):
If you want to add the printer to a spooler class, you may enter
the name now or configure it later with lpadmin(1M).
Will this be the default printer? (y/n/q default=n)
Enter your choice.
Ready to shut down the spooling system, configure the new
destination, and start the spooling system again. When the
spooling system is shut down all printing will stop. Any print
requests that are currently printing will be reprinted in their
entirety when the spooling system is restarted.
Ok to continue? (y/n/q default=y)
Enter "y" to restart the spooler.
Repeat this process if there are other ports on the print server
device that will be used. You can specify the port numbers in the
final step below. When finished you can select "q" to quit hpnpcfg.
At this point, you may want to change the printer interface through
the SCOadmin Printer Manager if you did not know it previously.
# scoadmin printer
- Highlight the printer that you want to change the interface.
- Select "Properties" from the "Printer" pull-down menu.
- Select the interface from the "Make/Model" list.
- Select "OK" to complete the changes.
Scoadmin Printer Method:
# scoadmin printer
- From the "Printer" pull-down menu, select "Add TCP/IP Printer".
- Enter the spool name of the printer in the "Name" field.
- Select the "Protocol Type" to be "System V(Legacy)".
- Select the appropriate interface from the "Make/Model" list.
- The "Printer Connection Type" will be "On Network".
- Enter the DNS name of the printer, or print server, in the "Remote
Printer" field or select it from the "Select" list.
- Select "OK" to complete the installation.
Repeat this process if there are other ports on the print server
device that will be used. You can specify the port numbers in the
final step below.
3. The final step is to edit the interface scripts for the second
and/or 3rd ports if applicable (HP print server).
# cd /etc/lp/interfaces
Use your favorite text editor to modify the file named the same
name as your printer on either the second or third ports. For the
example included below, port 2's interface will be modified.
Add the following changes to the printer interface:
echo "$1\t$REALMODEL | $HPNPF -x $PERIPH -p 9101" >> $LPLOG
^^^^^^^
The above line would be found on or about line 48.
if $REALMODEL "$@" | $HPNPF -x $PERIPH -p 9101 2> $LOG > /dev/null
^^^^^^^
The above line should be found on or about line 64.
Repeat this process for the third port (9102) if necessary.
There is no need to restart the spooler after editing these scripts.
NOTES:
For three-port print servers, you must have a working printer on port
1 before the printer(s) on ports 2 and/or 3 will work. Similarly, you
must have working printers on ports 1 and 2 before the printer on port
3 will work. If you notice a problem printing to ports 2 or 3, check
the lower-numbered port's printing capabilities.
With the single-port models, you do not need to be concerned with the
concept of the additional port numbers 9101 and 9102.
SEE ALSO:
Technical Article 114442, "While adding a printer using the Print Manager and it fails with an error, "General failure occurred in processing the request, etc...""
|