Some odd printing problems with networkprinter Please Help
W.E.D
Message from lp on myhost (???) [ So Sep 1 21:22:05 ] ...
Subject: Problem with printer HP1100A
The printer HP1100A has stopped printing for the reason given below.
Fix the problem and bring the printer back on line
to resume printing.
The reason(s) it stopped (multiple reasons indicate repeated attempts):
Usage: netpr -I request_id -p printer -d destination -U
username [ -f type ] [ -T title ] [ -P protocol ] [-t
timeout] [ -c ] [ -b ] files<EOT>
What is misconfigured here?
I did:
bash-2.03# lpadmin -p HP1100A -v /dev/null
bash-2.03# lpadmin -p HP1100A -m netstandard
bash-2.03# lpadmin -p HP1100A -o protocol=tcp
bash-2.03# accept HP1100A
destination "HP1100A" now accepting requests
# enable HP1100A
bash-2.03# lpadmin -p HP1100A -D "HP1100A an printserver"
bash-2.03# lpstat -p HP1100A
printer HP1100A is idle. enabled since Sonntag, 1. September 2002,
21:14:15 Uhr CEST. available.
And after lp testfile:
bash-2.03# Sep 1 21:15:47 myhost write: /dev/dtremote in utmpx is not a
tty
I can ping to the device in my printers.conf which is:
# # cat /etc/printers.conf
#
# If you hand edit this file, comments and structure may change.
# The preferred method of modifying this file is through the use
of
# lpset(1M)
#
HP1100A:\
:bsdaddr=myhost,HP1100A,Solaris:\
:description=HP1100A an printserver:
_default:\
:use=HP1100A:
Can someone help me?.
Greg Andrews
>Following error i got after trying to print with lp:
>
> Message from lp on myhost (???) [ So Sep 1 21:22:05 ] ...
>Subject: Problem with printer HP1100A
>
>The printer HP1100A has stopped printing for the reason given below.
>Fix the problem and bring the printer back on line
>to resume printing.
>
>The reason(s) it stopped (multiple reasons indicate repeated attempts):
>
>Usage: netpr -I request_id -p printer -d destination -U
>username [ -f type ] [ -T title ] [ -P protocol ] [-t
>timeout] [ -c ] [ -b ] files<EOT>
>
>What is misconfigured here?
>
You probably have a netstandard interface script that's more recent
than the netpr binary, and netstandard is trying to use a command
line option that the older netpr doesn't support.
This kind of thing can happen if you tar up the /etc/lp directory
tree on one machine and untar it on a second machine, when the
second machine is not up to date on the printing patch.
The way to fix this is to apply the current Solaris lp patch so
the netstandard and netpr versions are synchronized. Unfortunately,
you didn't mention which version of Solaris you're using. I don't
know which patch to recommend.
-Greg
--
Do NOT reply via e-mail.
Reply in the newsgroup.
Martha Starkey
As Greg indicates, make sure you have the latest lp patch for your version of Solaris, remove and readd the printer with the missing info.
W.E.D
> You probably have a netstandard interface script that's more recent
> than the netpr binary, and netstandard is trying to use a command
> line option that the older netpr doesn't support.
>
> This kind of thing can happen if you tar up the /etc/lp directory
> tree on one machine and untar it on a second machine, when the
> second machine is not up to date on the printing patch.
I did nothing like this, it is a standardinstall of Solaris 8 (INTEL)
>
>
> The way to fix this is to apply the current Solaris lp patch so
> the netstandard and netpr versions are synchronized. Unfortunately,
> you didn't mention which version of Solaris you're using. I don't
> know which patch to recommend.
see above.
W.E.D
> A couple of things stick right out here. First, is where is your -o dest= command? You have to indicate who/where the printer is with -o dest=<ip addy or hostname of printer> Furthermore, you indicated protocol=tcp but you didn't change the port number. By default, you get bsd and port 515, which you rarely have to change. If you need to indicate tcp, you have to indicate the it in the -o dest= portion of the command, which you didn't use, i.e. protocol=tcp -o dest=printerhostname:9100.
Thank you, i thought protocols and ports are fixed defaults, e.g. 9100 for tcp
>
>
> As Greg indicates, make sure you have the latest lp patch for your version of Solaris, remove and readd the printer with the missing info.
Do i really have to patch? It is a Solaris 8 release , original from CD from August 2001.
My knowhow just was enough to disable it. (the printer)
How to remove and what to remove?
I will try with some new names until it works and then remove the not working one`s :-)
Thank you for your advice.
Greg Andrews
>Martha Starkey wrote:
>
>> A couple of things stick right out here. First, is where is your -o
>dest= command? You have to indicate who/where the printer is with -o
>dest=<ip addy or hostname of printer> Furthermore, you indicated
>protocol=tcp but you didn't change the port number. By default, you get
>bsd and port 515, which you rarely have to change. If you need to
>indicate tcp, you have to indicate the it in the -o dest= portion of the
>command, which you didn't use, i.e. protocol=tcp -o
>dest=printerhostname:9100.
>
>Thank you, i thought protocols and ports are fixed defaults, e.g. 9100 for tcp
>
Nope. The default port number is 515. There is no default destination,
as I'm sure you can understand. (i.e. for the same reason there's no
default destination for the 'telnet' and 'ftp' commands) It's the lack
of destination that produced the error.
>
>Do i really have to patch? It is a Solaris 8 release , original from CD
>from August 2001.
>
You should have the patch. For one thing, it fixes three or four
security vulnerabilities in various parts of the printing system.
>
>My knowhow just was enough to disable it. (the printer)
>How to remove and what to remove?
>
lpadmin -x printer-name
The current Solaric 8 x86 printing patch can be found by searching for
"lp" and "5.8" in the "patch descriptions" section of sunsolve.sun.com.
I.e. 109321-05
W.E.D
> >
> >Thank you, i thought protocols and ports are fixed defaults, e.g. 9100 for tcp
> >
>
> Nope. The default port number is 515. There is no default destination,
> as I'm sure you can understand. (i.e. for the same reason there's no
> default destination for the 'telnet' and 'ftp' commands) It's the lack
> of destination that produced the error.
ok. I thought the name i mentioned i the device because it is also to be found in
the hostfile.
>
>
>
> >
>
> lpadmin -x printer-name
>
>
# lpadmin -x HP1100A
UX:lpadmin: ERROR: There are jobs currently queued for destination
"HP1100A"
TO FIX: Use the /usr/sbin/lpmove command to
assign them to another destination,
or wait for them to finish printing.
I cannot move to any other destination because there is no.
I there no caommand to flush/clean the queue?
Greg Andrews
>Greg Andrews wrote:
>
>> Nope. The default port number is 515. There is no default destination,
>> as I'm sure you can understand. (i.e. for the same reason there's no
>> default destination for the 'telnet' and 'ftp' commands) It's the lack
>> of destination that produced the error.
>
>ok. I thought the name i mentioned i the device because it is also to be
>found in the hostfile.
>
Solaris does not assume the name you specified for the -v option is
the hostname of the printer. The hostname (or IP address) of the
printer is specified in the "-o dest=hostname" option.
>> lpadmin -x printer-name
>
># lpadmin -x HP1100A
>UX:lpadmin: ERROR: There are jobs currently queued for destination
> "HP1100A"
> TO FIX: Use the /usr/sbin/lpmove command to
> assign them to another destination,
> or wait for them to finish printing.
>
>I cannot move to any other destination because there is no.
>I there no caommand to flush/clean the queue?
>
Cancel the print jobs with the /usr/bin/cancel or /usr/ucb/lprm command.
Then you can delete the printer queue.
W.E.D
Thank you for this commands. I feel rather uncomfortable now because such a
silly situation (and silly questions from me?)
But:
All this commands complain with:
# lpmove HP1100A HP
HP1100A: unknown printer
#lprm -P HP1100A
HP1100A: unknown printer
And then this NOTEXISTING printer is mentioned here. Very inconsequent, isn`t
it?
Message from lp on myhost (???) [ Di Sep 3 22:09:05 ] ...
Subject: Problem with printer HP1100A
The printer HP1100A has stopped printing for the reason given below.
Fix the problem and bring the printer back on line.
Printing has stopped, but will be restarted in a few minutes;
issue an enable command if you want to restart sooner.
Unless someone issues a change request
lp -i HP1100A-1 -P ...
to change the page list to print, the current request will be reprinted from
the beginning.
The reason(s) it stopped (multiple reasons indicate repeated attempts):
Failed to open the printer port. (No such file or directory)<EOT>
---
I must delete this thing.
W.E.D
> All this commands complain with:
> # lpmove HP1100A HP
> HP1100A: unknown printer
> #lprm -P HP1100A
> HP1100A: unknown printer
>
> And then this NOTEXISTING printer is mentioned here. Very inconsequent, isn`t
> it?
>
> Message from lp on myhost (???) [ Di Sep 3 22:09:05 ] ...
> Subject: Problem with printer HP1100A
>
> The printer HP1100A has stopped printing for the reason given below.
> Fix the problem and bring the printer back on line.
> Printing has stopped, but will be restarted in a few minutes;
> issue an enable command if you want to restart sooner.
> Unless someone issues a change request
>
> lp -i HP1100A-1 -P ...
>
> to change the page list to print, the current request will be reprinted from
> the beginning.
>
> The reason(s) it stopped (multiple reasons indicate repeated attempts):
>
> Failed to open the printer port. (No such file or directory)<EOT>
> ---
> I must delete this thing.
Done!
I readded the printer with the admin-gui and then lpmove worked and i could
remove this thing.
Greg Andrews
>>
>> Cancel the print jobs with the /usr/bin/cancel or /usr/ucb/lprm command.
>> Then you can delete the printer queue.
>>
>
>silly situation (and silly questions from me?)
>But:
>All this commands complain with:
># lpmove HP1100A HP
>HP1100A: unknown printer
>#lprm -P HP1100A
>HP1100A: unknown printer
>
>And then this NOTEXISTING printer is mentioned here. Very inconsequent, isn`t
>it?
>
You've already fixed it, but the usual cause for this kind of problem
comes from editing the /etc/printers.conf file by hand, or using
Admintool to delete the printer (and it's not fully successful).