Ok, I'll keep the ipp14 with utmost care ;-)
Changing the IPP protocol in a way, that it becomes incompatible with
the previous versions I find strange.
While searching the net for a solution, I found a lot of screaming of
Apple users that had exactly the same problem.
I understood, that Apple qu
Hello
mv /usr/lib/cups/backend/ipp /usr/lib/cups/backend/ipp-orig
cp /usr/lib/cups/backend/ipp14 /usr/lib/cups/backend/ipp
It works. I can print from both machines again.
What means that something went wrong with the ipp in Wheezy.
Thank you very much for your perfect support,
Adrian.
sign
Hi,
One more thing. On ReadyNAS I activated the Bonjour discovery
service.
CUPS found the printer nearly instantly, including all the
connection parameters.
Then I chose the manufacturer and model (hp photosmart_7900_series).
However, when attempting to
Below are some diagnostics.
Soon I shall add the cups log.
The destination is a print server of the Netgear ReadyNas NV+.
ping ok,
nmap :
Host is up (0.0043s latency).
Not shown: 994 closed po
Hello,
Thanks for your light-speed response.
I have Intel Core 2 Duo Quad, which packages should I install from
http://alioth.debian.org/~odyx-guest/debian/wheezy/
and in which order?
Cheers,
Adrian.
On 16/06/13 21:08, Didier 'OdyX' R
After upgrade Squeeze --> Wheezy I have the same problem.
Get-Printer-Attributes returned server-error-internal-error.
Unable to get printer status.
This is while attempting to print via ipp.
When the printer is connected locally, CUPS sees it, allows to print one
page and then says, that the pri
After upgrade Squeeze --> Wheezy I have the same problem.
Get-Printer-Attributes returned server-error-internal-error.
Unable to get printer status.
This is while attempting to print via ipp.
When the printer is connected locally, CUPS sees it, allows to print one
page and then says, that the pri
