"Alain" <ota1998@hotmail.com> wrote in message
news:bfrs77$i5r3b$1@ID-202261.news.uni-berlin.de...
> > I need to set up multiple print queues that all print to the same
> > network HP printer (HP8000 printer) with different characteristics.
>
> See here:
>
> HP Jetdirect Print Servers - Printing Software and Firmware Upgrade
> Solutions:
>
> http://www.hp.com/cposupport/networking/support_doc/bpj07126.html
>
> Alain.
>
>
return to original page
HP Jetdirect Print Servers - UNIX(R) Troubleshooting Guide
path: Home
date: 6/29/02
document description: HP Jetdirect Print Servers -
UNIX(R) Troubleshooting Guide
document id: bpj02698
You may provide feedback on this document
--------------------------------------------------------------------------
HP Jetdirect Print Servers - UNIX(R) Troubleshooting Guide
In this document:
TCP/IP addressing
BootP and RARP
Using HP Jetdirect Printer Installer for Unix to troubleshoot
BootP
Host names
Communications
The Ping command
Telnet
Arp
Spooler operations
Using HP Jetdirect Printer Installer for Unix as a spooler
independent printing test
Testing the printing functionality of the HP Jetdirect using
Telnet
Using HP Jetdirect Printer Installer for UNIX to examine print
spooler output to verify proper PCL strings
Spooler commands
Stair Stepping in printing
HP Jetdirect Printer Installer for Unix filenames and locations
Software and firmware solutions
Contact HP?
This document is intended as a troubleshooting overview of HP
Jetdirect problems in a UNIX(R) environment. Some of the techniques used are
unsupported methods of printing through HP Jetdirect devices and are
intended only to illustrate operations and to aid in troubleshooting.
Whenever possible, troubleshooting should be done from HP software or by
using approved methods of printing to HP Jetdirect devices.
TCP/IP addressing
The following are a few questions to ask concerning TCP/IP addressing:
a.. Has the printer been assigned a TCP/IP address?
b.. How has the TCP/IP address assigned (for example, by BootP,
front panel, telnet, etc.)?
c.. Can the IP address and status be verified by the Configuration
page?
d.. Is there a host name assigned?
Telnet/Front Panel
Telnet is an application that provides an interactive login to a
remote system via TCP/IP:
syntax:
telnet "IP address"
Minimum firmware to set an IP address via Telnet:
a.. 03.03
b.. 03.16
c.. 03.16
d.. 04.03
e.. 04.20
f.. Or most any firmware higher than those listed.
g.. The 150X and 170X Jetdirects are not supported in Unix.
The default IP address of an HP Jetdirect device, having the
appropriate firmware, will be 192.0.0.192. In some environments, the address
192.0.0.192 will have to be a resolved IP address on the network before a
Telnet session will be possible. A route add command may have to be run,
depending on the environment, to connect to an IP address on the network.
Refer to the man pages for route or route add for more information
If Telnet is successful, type:
a.. return twice
b.. "?" to provide a menu listing of current parameters and
commands for modifying these parameters
c.. "quit" to exit and save changes
d.. "exit" to exit without saving changes
The IP address may also be changed using the front panel of most HP
printers. The method of front panel configuration will vary depending on the
model of HP printer (consult the User's Guide for the front panel
instructions on a particular printer).
NOTE: When a front panel configuration is not possible, you can move
the HP Jetdirect device into a printer capable of front panel configuration
and then move it back into the original printer after setting the
parameters.
See documents regarding configuring the HP Jetdirect TCP/IP Address
through the front control panel of the printer or plotter for more
information on front panel configuration.
Using HP Jetdirect Printer Installer for Unix to verify IP
configuration data
If the UNIX platform you are using has HP's Jetdirect Printer
Installer utility installed, IP parameter configuration can be verified
using the following steps:
1.. Log in as root and enter the HP Jetdirect Printer Installer
for Unix utility.
2.. Select option 3: Diagnostics.
3.. Select option 5: View HP Jetdirect interface's current
configuration.
4.. Enter the IP/Host name at the prompt, and the following data
will appear:
Config Source, Card IP Address, Network Mask, Default Gateway,
Idle Timeout
NOTE: You will also be given the options of printing the data or
saving it to a file.
BootP and RARP
BootP (Bootstrap Protocol) and RARP (Reverse Address Resolution
Protocol) are each used for the central administration and distribution of
IP addresses and other boot process information. BootP and RARP are normally
used on large networks where IP management is an issue and where IP devices
need to acquire IP parameters at power up. For these processes to take
place, a BootP or RARP server on the UNIX system must be established. This
server is fully dependent on the OS and must be functional before an HP
Jetdirect device can be initialized using it.
There are several differences between BootP and RARP, but the two
primary differences are the number of connections required for boot and the
communication layer that they use. RARP servers provide only the IP address
in the first connection. Additional information must be retrieved by
subsequent requests/responses between the host and client. After an initial
BootP request by a client, all boot process information can be supplied by
the host in a single response. RARP uses the data link layer (DLC/ 802.2)
and, therefore, will not work across routers. On the other hand, BootP is a
high-level protocol that uses UDP and can work across routers. These
differences make BootP a better choice for keeping network traffic to a
minimum and for being able to work on multiple subnets.
BootP is a reliable method of setting IP parameters when the BootP
service is established and maintained. HP Jetdirect implementation of BootP
conforms to RFC 951 and RFC 1048. BootP requires that an administrator know
how to use and maintain BootP independent of HP Jetdirect product issues.
Front panel or Telnet configuration may be a desirable method of setting IP
parameters for those who are not experienced with BootP.
In order for an internal HP Jetdirect device to use BootP, set
BootP=YES at the printer's front panel. If a BootP server does not respond
within five minutes, HP Jetdirect products with the appropriate firmware
will default to the IP address of 192.0.0.192.
According to RFC 951, depending on the implementation of BootP,
"gateways listening to broadcast BOOTPREQUESTs may decide to forward or
rebroadcast these requests when appropriate."
Using HP Jetdirect Printer Installer for Unix to troubleshoot BootP
If the UNIX platform you are using has HP's Jetdirect Printer
Installer utility installed, BootP operations can be verified using the
following steps.
1.. Log in as root and enter the HP Jetdirect Printer Installer for
UNIX utility.
2.. Select option 3: Diagnostics.
3.. Select option 6: Check BOOTP and TFTP operations (super-user
only).
4.. A list of currently available hardware addresses will appear.
5.. Enter the printer's LAN hardware address.
6.. After a "Passed! "bootpd" is functional and responding" message
appears, you are prompted to view the response or continue.
7.. Upon continuing, you should see the following message: "Testing
TFTP operations... RESULT: Passed."
8.. After continuing, the message: "Completed the BOOTP/TFTP
simulation tests" appears, and the BootP and TFTP operations test is
completed.
The steps listed assume that the HP Jetdirect device is working
correctly. If any errors are encountered during the diagnostic test, the HP
Jetdirect Printer Installer software should prompt the user for the
appropriate actions. The user may also need to reference HP's and/or the OS
provider's BootP software documentation for further troubleshooting.
Other BootP troubleshooting
Errors relating to TFTP:
Check to make sure that the /etc/inetd.conf does not have # or
comment marks at the beginning of the following lines:
a.. tftp dgram udp wait root /etc/tftpd tftpd
b.. bootps dgram udp wait root /etc/bootpd bootpd
Errors relating to the BootP process:
Check to make sure that the /etc/services file does not have # or
comment marks at the beginning of the following lines:
a.. bootps 67/udp # Bootstrap Protocol Server
b.. bootpc 68/udp # Bootstrap Protocol Client
For more information on troubleshooting BootP server, see "HP
Jetdirect Print Servers - Application Note for Troubleshooting BOOTP."
Host names
A host name is an alias or nickname assigned to an IP address. Some
users will configure print queues using the host name instead of the IP
address. Troubleshooting in UNIX includes using the IP address and host
name. Host name data is not resident on the HP Jetdirect card unless it is
configured through BootP. In a UNIX host file, there can be an entry that
ties the IP address to a host name without the host name being part of the
HP Jetdirect card configuration. In HP-UX, a user can enter the following
command to verify that a host entry is present:
grep "IP-address" /etc/hosts
The response line should show the alias name associated with the IP
address. Troubleshooting using the IP address should always be done first to
prove the functionality of an HP Jetdirect product.
Using HP Printer installer for Unix to verify host name
If the UNIX platform that you are using has HP's Printer Installer
for UNIX utility installed, IP parameter configuration (such as the host
name) can be verified using the following steps.
1.. Log in as root and enter the HP Printer installer for UNIX
utility.
2.. Select option 3: Diagnostics.
3.. Select option 5: View HP Jetdirect interface's current
configuration.
4.. Enter the IP/Host name at the prompt and the following data
will appear:
a.. Config Source, Card IP Address, Network Mask, Default
Gateway, Idle Timeout
b.. The "Card IP Address" should be in the format: Host name (IP
address).
The host name can be tested using the following method:
1.. Login as root and enter the HP Printer Installer for Unix
utility.
2.. Select option 2: Diagnostics.
3.. Select option 3: Test network printer's accessibility.
4.. The Host name or the IP address can be entered as a test.
Other parameters
Valid IP addresses as well as subnet mask information should be
resolved within a particular environment before the HP Jetdirect solution is
viable. Log server and default gateway IP addresses may also have to be
defined, depending on the environment.
Communications
Good troubleshooting of printing problems in a UNIX or any TCP/IP
environment starts at the basic communication level. Communication can be
tested using Ping, Telnet, and HP Jetdirect Printer Installer for Unix.
Using HP Jetdirect Printer Installer for UNIX to Verify HP Jetdirect
connectivity
If the UNIX platform that you are using has HP's Jetdirect Printer
Installer for UNIX utility installed, IP communications to the HP Jetdirect
device can be verified using the following steps.
1.. Log in as root and enter the HP Jetdirect Printer Installer
for UNIX utility.
2.. Select option 3: Diagnostics.
3.. Select option 3: Test network printer's accessibility.
4.. The Host name or the IP address can be entered as a test.
The following message should appear: "RESULT: `IP address' is a
network printer; `UNIX-HOST' is allowed access to `IP address.'"
A test page can be printed using the following steps:
1.. Log in as root and enter the HP Jetdirect Printer Installer
for UNIX utility.
2.. Select option 2: Diagnostics.
3.. Select option 4: Print a test page to printer.
4.. The Host name or the IP address can be entered as a test.
5.. Enter the network printer name or IP address.
6.. Select which print type should be sent: text, PostScript (R),
or HPGL2.
The following message should appear: Result: The file has been
successfully sent to "IP/ Host name." Check output!
7.. The test page should print.
The Ping command
Example:
ping 100.101.102.103
On Solaris or SunOS computers use the -s switch to display the ping
time in milliseconds. For example:
ping -s 100.101.102.103
Ping is a low level IP communication that verifies if an IP device is
"alive" on the network by sending an echo request packet once per second to
that device. Each packet echoed back from the device is reported on the
screen. Messages such as "Request timed out" or "Destination unreachable" or
no response from ping could indicate a communication or hardware problem.
Troubleshooting Ping
1.. Check hardware; is the printer or HP Jetdirect powered on?
2.. Check the HP Jetdirect configuration page. Is the I/O Card
Ready?
3.. Check the HP Jetdirect configuration page. Is the TCP/IP
Status Ready?
4.. Check the HP Jetdirect configuration page. Is there a
duplicate IP address on the network? The Jetdirect configuration page
reports a duplicate IP address under the TCP/IP Status. Usually the MAC
address of the network device with the duplicate address will appear below
the error on the configuration page. Ping can be used to prove a duplicate
IP address problem. Disconnect the HP Jetdirect device from the network and
then ping the IP address that was configured on that HP Jetdirect. If there
is a reply, another device on the network has the same IP address IP
address.
5.. Check the HP Jetdirect configuration page. Verify the IP
addresses. Compare them with the IP address of the computer to see if they
are on the same network.
6.. Can you ping other devices? Ping the loopback IP of 127.0.0.1
or the computer's own IP address to test the functionality of ping from that
computer.
7.. Is there a router between the computer and the HP Jetdirect?
If another computer can ping the HP Jetdirect, you could have router-related
problems on the network. HP Jetdirect devices need to have the default
gateway address (the router) configured to return an echo back through the
router to the origin of a ping.
Telnet
Used as a communications test, Telnet will establish a connection with
an HP Jetdirect from the application layer. For example, at a command prompt
type:
telnet 101.102.103.104
After establishing a Telnet connection to an HP Jetdirect device,
press the return key twice and type a question mark or a forward slash. The
Jetdirect should respond with a help menu or information.
A Telnet can also be a valid test for a host name. If HP cannot Telnet
to a host name but can Telnet to an IP address, a host name conflict or a
missing host name entry check for problems in the particular environment has
occurred.
Troubleshooting Telnet
1.. Make sure you can ping the HP Jetdirect. Follow the
troubleshooting above if you cannot.
2.. Check hardware; is the printer or HP Jetdirect powered on?
3.. Check the HP Jetdirect configuration page. Is the I/O Card
Ready?
4.. Check the HP Jetdirect configuration page. Is the TCP/IP
Status Ready?
5.. Check the HP Jetdirect configuration page. Is there a
duplicate IP address on the network? The HP Jetdirect configuration page
reports a duplicate IP address under the TCP/IP Status. Usually the MAC
address of the network device with the duplicate address will appear below
the error on the configuration page. Ping can be used to prove a duplicate
IP address problem. Disconnect the HP Jetdirect device from the network and
then ping the IP address that was configured on that HP Jetdirect. If there
is a reply, another device on the network has the same IP address IP
address.
6.. The message "connection refused" indicates a busy HP Jetdirect
device or the HP Jetdirect may not have Telnet capability. The firmware
revision on the configuration page should be x.03.06 or higher.
7.. If you are trying to telnet to the host name, use the IP
address instead. The nameservers may not be properly configured.
Arp
The command arp will display characteristics of TCP/IP. It can test
whether or not a certain IP address or host name has been resolved within an
operating system. Arp is more easily understood if time is taken in
experimenting with some test IP addresses or host names on a system.
Troubleshooting with arp is only recommended after a certain amount of time
is taken in practicing the command and interpreting output dialogue.
Arp displays the Internet to Ethernet address translation tables used
by Address Resolution Protocol. Arp can be used after attempts have been
made to communicate with a host name for a particular HP Jetdirect device.
Each arp entry will reflect the IP address associated with a host name and
the MAC address of the HP Jetdirect device. If an arp entry based on host
name data is not reported by UNIX, it is evident that communications to the
HP Jetdirect device via a host name are not possible. The same tests can be
attempted with an IP address rather than a host name; these tests can point
out problems with host name resolution and/or IP address resolution.
Syntax:
arp -a | grep "Host Name"
Or:
arp -a | grep "IP Name"
Response:
"Host Name" ("IP address") at "MAC address" ether
No response indicates that an entry does not exist. Retry arp after a
ping test; the Internet to Ethernet address translation tables are dynamic
and will change according to the activity associated with that device.
Spooler operations
The spooling system in any given UNIX platform can be confusing. Many
questions should be asked to extract as much information about the
environment as possible. A few questions to ask concerning spooler
operations are:
a.. What is the operating system?
b.. Is the HP Jetdirect Printer Installer for UNIX utility being
used?
c.. Is LPD printing being used?
d.. Is the LPD configuration method, manual printcap entries, or an
administration utility used?
e.. Does the LPR/LPD solution meet RFC1179 requirements?
NOTE: In many cases, end users will have to be referred to their OS
support provider because HP will only provide limited support for
environment-related issues.
Using HP Jetdirect Printer Installer for Unix as a spooler independent
printing test
If the UNIX platform that you are using has HP's Jetdirect Printer
Installer for UNIX utility installed, a print out from HP Jetdirect Printer
Installer for UNIX can test the HP Jetdirect (independent of the UNIX
spooling system) using the following steps.
1.. Log in as root and enter the HP Jetdirect Printer Installer for
UNIX utility.
2.. Select option 3: Diagnostics.
3.. Select option 3: Test network printer's accessibility."
4.. The Host name or the IP address can be entered as a test. Use
the IP address if you are unsure about the name resolution on your network.
5.. The following message should appear: "RESULT: `IP address' is a
network printer: UNIX-HOST' is allowed access to `IP address."
Print a test page using the following steps:
1.. Log in as root and enter the HP Jetdirect Printer Installer for
Unix utility.
2.. Select option 3: Diagnostics.
3.. Select option 4: Print a test page to printer.
4.. Enter the network printer name or IP address. The hostname or
the IP address can be entered as a test. Use the IP address if you are
unsure about the name resolution on your network.
5.. Select which print type should be sent: text, PostScript, HPGL2.
6.. The following message should appear: "Result: The file has been
successfully sent to 'IP/ Host name.' Check output!" and the test page
should print.
HPNPF testing HP-UX or Solaris with the HP Jetdirect Printer
Installer for UNIX
Testing the functionality of the HP Jetdirect (independent of the
Solaris, SunOS, or HP-UX spooling systems) can be accomplished by using
hpnpf. Hpnpf is a specialized TCP driver that provides connectivity to
network printers. It will, by default, connect to port 9100 of a given IP
address and transfer a file to the HP Jetdirect connected printer.
The common syntax for this command is:
hpnpf -x "IPaddress" filename
NOTE: Use the -n option if the print job is an ASCII file.
At an HP-UX prompt, an ASCII text file can be sent with the full
path string:
/usr/lib/hpnpl/bin/hpnpf -n -x "IPaddress"
/usr/lib/hpnp/testfiles/text
At a Solaris 2.x prompt, an ASCII text file can be sent with the
string:
/opt/hpnpl/bin/hpnpf -n -x "IPaddress" /opt/hpnp/testfiles/text
The ASCII file test for SunOS 4.1.2 is:
/usr/lib/hpnp/hpnpf -n -x "IPaddress" /usr/lib/hpnp/testfiles/text
The filename listed in the example above is text. This is a simple
ASCII string in the testfiles subdirectory of the hpnpl subdirectory. There
is also a PostScript file and an HPGL2 file located in this subdirectory:
a.. HP-UX:(/opt/hpnpl/testfiles):
hpgl2 ps text
b.. Solaris:(/opt/hpnp/testfiles):
hpgl2 ps text
c.. SunOS:(/usr/lib/hpnp/testfiles):
hpgl2 ps text
A user-provided file can be tested using the hpnpf method, and the
results can be compared to a test using one of these three test files. These
test strings may only work in the operating system versions listed here and
only when the HP Jetdirect Printer Installer software for that operating
system has been installed.
Testing the printing functionality of the HP Jetdirect using Telnet
When trying to bypass spooling on any non-HP Jetdirect Printer
Installer equipped UNIX system, a Telnet can be used to transfer data to the
HP Jetdirect device:
Telnet "IP-name" 9100 < "filename"
Or:
cat filename | Telnet `IP-name" 9100
Or:
Telnet "IP-name" 9100; then, type test characters and end Telnet
session. Characters should now print.
Telnet porting may differ in the variety of environments that include
Telnet as an application. One of the examples above should work.
The CTRL+] entered will end the Telnet connection; then, type "quit"
to end Telnet. Another way to terminate the Telnet connection would be a
CTRL+Z.
Other sources of communication/functionality troubleshooting
techniques can be found in KB Document: BPJ02710.
Using HP Jetdirect Printer Installer for UNIX to examine print spooler
output to verify proper PCL strings
If the UNIX platform that you are using has HP's Jetdirect Printer
Installer utility installed, print output from HP Jetdirect Printer
installer can prove or disprove the viability of the HP Jetdirect solution
with the UNIX spooling system using the following steps.
1.. Log in as root and enter the HP Jetdirect Printer Installer for
UNIX utility.
2.. Select option 3: Diagnostics.
3.. Select option 2: Examine spooler operations.
4.. Enter the name of the lp queue (print queue name created in HP
Jetdirect Printer Installer).
5.. The following message should appear: Spooler: OK (running);
"queue name" OK (accepting jobs).
6.. Enter the file name(s).
7.. Enter options (in -o<option> -o<option> format); type return for
none.
8.. The following prompt will appear: "Do you want to examine the
output?"
You may now examine the code that the UNIX spooling system is
generating to be sent to the HP Jetdirect device. After answering yes to the
prompt, the output can be examined through a more function. An example of
this output could look like this:
a.. @PJL ENTER LANGUAGE=PCL
b.. ^[&k2Gtest test test
The output is indicating that the string <ESC>&k2G is present in the
print job. This print job should not stair step.
The rest of the steps listed here will continue the diagnostic process
and send print output to the HP Jetdirect device.
1.. Enter y at the following prompt: "Continue?"
2.. The following message should appear: "Printer (Host name) is OK
(alive and accessible)."
3.. Enter y at the following prompt: "Do you want to send this job
to it?"
4.. The following message should appear: "File has been sent to
printer. Check /tmp/hpnpflog and printer output."
For more information on the stair stepping problem, see documents
bpj02744 HP Jetdirect Print Servers - Fixing Stair-stepping in UNIX(R) Print
Jobs
and bpj02668 HP Jetdirect Print Servers - Model Scripts Availability
and Usage for a Non-HP Printer.
Spooler commands
In some situations, a customer may report the presence of jobs in a
queue that cannot be deleted. The printer may be printing a partial copy and
then start the whole job again from the beginning. These problems could be
caused by timing parameters like the idle timeout in the HP Jetdirect card.
A spooler issue or an older revision of HP Jetdirect Printer Installer may
also cause print jobs to terminate prematurely. In any case, a few commands
can help us to handle print jobs "stuck" in queue.
The command:
disable "QUEUE_NAME"
This command will put the queue on hold and printing will stop. The
response should be:
printer "QUEUE_NAME" now disabled
Obtain a listing of jobs in queue with the command:
lpstat "QUEUE_NAME"
The response should be:
a.. "QUEUE_NAME-JOB_NUMBER" "user_id" priority # TIME_DATE on
"QUEUE_NAME"
b.. "FILE_NAME" QTY bytes
The job(s) can be eliminated using the command:
cancel "QUEUE_NAME-JOB_NUMBER"
The response should be:
request "QUEUE_NAME-JOB_NUMBER" canceled
A disabled queue can be reenabled using the command:
enable "QUEUE_NAME" will re-enable a disabled queue
A queue cannot be deleted when jobs are queued. After disabling a
queue and canceling its jobs, a queue can be deleted and, if needed,
recreated. This procedure may vary depending on the OS. Specific spooler
operations are supported by the OS provider and are only listed here for the
purpose of demonstration.
Stair Stepping in printing
Stair Stepping symptoms are: first line prints normally, second line
prints partially, third line prints partially or not at all, and no other
lines print. This problem can be caused by a variety of situations. But,
usually, stair stepping is printer-related and the way it handles carriage
returns and line feeds. When ASCII files are created in UNIX, at the end of
each line, the line feed is used as a terminator character and a way for a
display to format what is viewed. Many printers will need an additional
character, the carriage return, to format a printed page so that it looks
the same as the displayed data on a CRT. The HP LaserJet printer will, at
default, treat a line feed as a line feed in the page formatting and, thus,
the symptoms of stair stepping occurs. The carriage return element is needed
at each occurrence of a line feed, or the printer needs instructions that
tell it how to handle a line feed.
The command that the printer needs for formatting or, adding carriage
returns to line feeds, is the PCL string:
<ESC>&k2G
Inserted at the beginning of the ASCII text file, this will eliminate
stair stepping.
HP Jetdirect Printer Installer or software like HP Jetdirect Printer
Installer will configure a spooling system to send this PCL string to a
printer through model scripting. A way to "fool" the system is by inserting
the following string at the beginning of an ASCII text file:
<ESC>E
This string will reset the printer to defaults and effectively
eliminate any PCL instructions previously sent through model scripting. This
proves that a PCL string, as shown above, will generate by model scripting.
LPD or line printer demon is resident on HP Jetdirect devices that
have a firmware revision of x.03.03 or greater. LPD gives the HP Jetdirect
device the ability to emulate a remote LPD host with two printers attached
to it. The names of these printers are raw and text. In situations where
BSD-like printing is taking place, make sure that the remote printer
designated is named text when ASCII files are to be sent. An example of this
would be in a manually configured printcap file entry:
"Printer_Name":\
a.. :lp=:\
b.. :rm="IPname/Hostname":\
c.. :rp=text:\
d.. :lf=/usr/spool/lpd/ERRORLOG:\
e.. :sd=/usr/spool/lpd/"Printer_Name":
If :rp is found to be raw, the stair stepping effect will occur when
ASCII files are printed. When rp:=text, the HP Jetdirect device will insert
the instruction: <ESC>&k2G to the beginning of the print job, thus telling
the printer how to handle line feeds. Again, the string: <ESC>E can "fool"
our HP Jetdirect card, as it will reset any previously sent commands. In
SunOS 4.1.3, these entries are found in /etc/printcap. This filename and
location will vary depending on the OS.
If an admin. tool is used to configure an LPD print queue, the printer
on that remote machine must be designated as text within that admin. or
configuration utility when ASCII files are printed.
If hpnpf is in use, the -n option must be used to set carriage return
functions and eliminate stair stepping.
HP Jetdirect Printer Installer for Unix filenames and locations
HP-UX 10.X and 11.X
a.. /usr/spool/lp/request/"printer_name" - The location of
spooling print jobs
b.. /opt/hpnpl/testfiles - The location of the
testfiles:ps,hpgl2,postscrIPt
c.. /opt/hpnpl/bin - The location of all the executable HP
Jetdirect Printer Installer files; hpnpf
d.. /opt/hpnpl/man - The location of HP Jetdirect Printer
Installer man page entries, should be part of MANPATH
e.. /usr/spool/lp/model - The location of HP Jetdirect Printer
Installer model script templates
f.. /usr/spool/lp/interface/model.orig/"printer_name" -
PERSONALTY="AUTO" change to personality = RELAY *
g.. /usr/lib/hpnp/examples - The location of example model script
files
Solaris 2.5
a.. /etc/lp/interfaces/model.orig/"printer_name" -
PERSONALTY="AUTO" change to personality = RELAY *
b.. /opt/hpnpl/man - The location of HP Jetdirect Printer
Installer man page entries, should be part of MANPATH
c.. /opt/hpnpl/testfiles - The location of the
testfiles:ps,hpgl2,postscrIPt
d.. /opt/hpnpl - The location of all the executable HP Jetdirect
Printer Installer related files; hpnpf
e.. /opt/hpnpl/examples - The location of example model script
files
Software and firmware solutions
Click here for links to download HP software solutions.
(http://www.hp.com/cposupport/networking/support_doc/bpj07126.html)
Click here to download HP Download Manager software to upgrade the
Jetdirect firmware.
(http://www.hp.com/cposupport.swindexes/hpjetdirec4628_swen.html)
Contact HP?
Find the nearest service center
Buy HP (United States)
Buy HP (Outside the United States)
UNIX (R) is a registered
trademark of the Open Group.
HP-UX release 10.20 and later and
HP-UX Release 11.00 and later
(in both 32 and 64-bit configurations)
on all HP 9000 computers are
Open Group UNIX 95 branded products.
PostScript (R) is a trademark
of Adobe Systems Incorporated.
Copyright (C) Hewlett-Packard Co. 1998
This information is subject to change without notice and
is provided "as is" with no warranty.
Hewlett-Packard shall not be liable for any direct,
indirect, special, incidental or consequential damages
in connection with the use of this material.
Solve
privacy statement using this site means you accept its terms � 1994 -
2002 hewlett-packard company
|
Search |
Post Question |
Groups |
Stream |
About |
Register
naraht
4392 articles. 
5 followers. 
3 Replies
1734 Views
