[cups.general] CUPS 1.3.6, Linksys PSUS4, jobs never complete

[Johannes Meixner]

Hello,

On Apr 16 23:12 Ace wrote (shortened):
> I still do not understand why IPP hangs, you said Windows clients do not
> implement IPP/1.1, but the fact remains Windows clients can print normally
> under IPP protocol, and CUPS cannot.
> Also, I have noticed while watching CUPS through it's web interface, that
> CUPS first tries to use IPP/1.1, which fails, then falls back to IPP/1.0,
> and then the job starts printing, but never finishes.

I do not understand why you do not understand that the hardware
is broken because it simply does not correctly implement the
IPP protocol and why you insist that this is a CUPS problem?

The fact remains that Windows clients cannot print normally
under IPP protocol simply because Windows has not a correct
IPP protocol implementation so that strictly speaking Windows
cannot do IPP at all - it does something like IPP but not
full IPP.

I do not understand why you do not ask the manufacturer
or vendor of those broken hardware for a fix.
The manufacturer or vendor sold you a piece of hardware
which claims to support the IPP protocol but seems
to fail for both IPP/1.1 and IPP/1.0.

Have a look at
http://www.cups.org/documentation.php/network.html
-----------------------------------------------------------
The AppSocket protocol (sometimes also called the
JetDirect protocol, owing to its origins with the
HP JetDirect network interfaces) is the simplest,
fastest, and generally the most reliable network
protocol used for printers.
....
IPP is the only protocol that CUPS supports natively
and is supported by some network printers and print
servers. However, since many printers do not implement
IPP properly, only use IPP when the vendor actually
documents official support for it.
....
LPD is the original network printing protocol and is
supported by many network printers. Due to limitations
in the LPD protocol, we do not recommend using it
if the printer or server supports one of the other
protocols.
-----------------------------------------------------------

I do not understand why you seem to insist that you must
use the most complicated protocol (IPP) to just send
the prtinting data to the printserver box instead
of using what is recommended?

Only because an incomplete IPP implementation in Windows
works by chance with the broken IPP implementation in
this broken hardware?

Or perhaps because IPP is "state of the art"?
Even if in your case the "state of the art" implementation
is plain broken in this broken piece of hardware crap?


By the way:

Do not assume that you can get device status for your
HP PhotoSmart 7350 via the HPLIP hp-toolbox program
when the device is "hidden" behind a non-HP printserver box.

See
http://hplip.sourceforge.net/supported_devices/photosmart.html
----------------------------------------------------------------
Photosmart 7350: Network or JetDirect: No

Network support indicates built-in ethernet and/or wireless
networking. Alternatively, many devices may be operated on
the network using an external JetDirect print server.
Not all network configurations are supported. Please 
refer to the HPLIP FAQs for more information. 
----------------------------------------------------------------
and the HPLIP FAQ reads:
----------------------------------------------------------------
Question: Does HPLIP support networked printers?
Answer: Yes, HPLIP supports printers that are directly network
connected (via a built-in Ethernet port) or connected to a
network via a JetDirect.

Question: What network print servers are supported?
Answer: Currently we have only tested HP JetDirect devices
with HPLIP. No other network print servers are supported.
----------------------------------------------------------------

The reason is that device status query requires a bidirectional
communication or certain SNMP support which works with a HP
built-in Ethernet port or certain HP JetDirect printserver boxes
but does usually not work with other printserver boxes.


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
AG Nuernberg, HRB 16746, GF: Markus Rex