Printing with a print server now fails since installing updates

English Network/Internet
1

I have been using a D-Link print server on my LAN for many years and have been able to print with 13.2 with the printer set up to be accessed using CUPS with the address

lpd://dlink-6D7033/LPT2

and a PPD file specifying its properties.

Yesterday I installed the latest updates and after rebooting, the previously installed printers were not listed as available. As previously, I used my web browser and address 127.0.0.1:631 to set up the printers again, but and the printer properties are shown correctly when I attempt to print a document, but the spooled file is never removed from the queue, it does not print, and the printer shows no sign of being contacted. I rebooted the print server but this made no difference. I have rebooted the computer but this has not helped.

I had disabled IPv6 because I get no network communication when it is enabled, and I had removed references to IPv6 addresses from the /etc/hosts file. Following a comment I found on the web, I have reinstated those lines, but this has made no difference.

The /var/log/cups/error_log file has this content:

E [23/Apr/2015:08:17:19 +1000] Unable to bind socket for address [v1.::1]:631 - Cannot assign requested address.
E [23/Apr/2015:08:24:53 +1000] [cups-driverd] Bad driver information file "/usr/share/cups/drv/sample.drv"!
E [23/Apr/2015:08:26:20 +1000] [cups-driverd] Bad driver information file "/usr/share/cups/drv/sample.drv"!
E [23/Apr/2015:08:28:15 +1000] cupsdReadClient: 17 IPP Read Error!
E [23/Apr/2015:08:46:43 +1000] Unable to bind socket for address [v1.::1]:631 - Cannot assign requested address.
E [23/Apr/2015:10:10:44 +1000] Unable to bind socket for address [v1.::1]:631 - Cannot assign requested address.
E [23/Apr/2015:10:22:00 +1000] cupsdReadClient: 16 IPP Read Error!
E [23/Apr/2015:10:23:46 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:24:09 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:24:32 +1000] cupsdAuthorize: pam_authenticate() returned 7 (Authentication failure)!
E [23/Apr/2015:10:24:34 +1000] cupsdAuthorize: pam_authenticate() returned 7 (Authentication failure)!
E [23/Apr/2015:10:24:56 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:24:56 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:25:15 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:25:15 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:25:45 +1000] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/5) from localhost
E [23/Apr/2015:10:25:45 +1000] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/5) from localhost
E [23/Apr/2015:10:25:45 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:25:45 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:26:00 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:10 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:10 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:10 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:19 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:19 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:19 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:20 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:20 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:20 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:50 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:30:50 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:31:04 +1000] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/4) from localhost
E [23/Apr/2015:10:31:04 +1000] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/4) from localhost
E [23/Apr/2015:10:31:04 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:31:04 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:34:29 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:35:16 +1000] [Job 4] Stopping unresponsive job!
E [23/Apr/2015:10:35:16 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:45:09 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:45:31 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:45:32 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:45:37 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:45:37 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:45:37 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:45:37 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:46:15 +1000] Returning IPP client-error-bad-request for Create-Printer-Subscription (/) from localhost
E [23/Apr/2015:10:47:43 +1000] Returning HTTP Forbidden for CUPS-Get-Devices (no URI) from localhost
E [23/Apr/2015:10:47:43 +1000] [CGI] CUPS-Get-Devices request failed with status 401: Forbidden
E [23/Apr/2015:10:48:17 +1000] Returning HTTP Forbidden for CUPS-Set-Default (ipp://localhost/printers/brother) from localhost
E [23/Apr/2015:10:52:09 +1000] [Job 6] Stopping unresponsive job!
2

On 2015-04-23 03:26, tgf wrote:
>
> I have been using a D-Link print server on my LAN for many years and
> have been able to print with 13.2 with the printer set up to be accessed
> using CUPS with the address
> Code:
> --------------------
> lpd://dlink-6D7033/LPT2
> --------------------
> and a PPD file specifying its properties.

And that name can be resolved to an IP address?

> Yesterday I installed the latest updates and after rebooting,

What kind of updates? mandatory updates (YOU / zypper patch), or
something else?

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

3

The “lpd://” address is recognized by CUPS to indicate that the traditional Unix lpd protocol should be used. Other protocols work, but “lpd” sends across information on the number of duplicates required rather than sending the whole document for each copy. It has worked reliably before.

I received a message saying that there were important updates to be installed, so I issued a “zypper up”.

4

That’s not what was being asked. It’s not about the printing protocol you’re using, but whether you can ping the print server successfully by name (ie ‘dlink-6D7033’) or IP address?

ping dlink-6D7033

then do the same by actual IP address of the device. For example,if you can ping by IP address, then ‘lpd://<IP address>/LPT2’ should work too eg ‘lpd://192.168.1.1/LPT2’

It’s just useful to try and distinguish between a networking issue and a print subsystem issue first.

5

Thanks for that advice. Yes, I was able to ping 192.168.1.104 but not dlink-6D703. Adding dlink-6D7033 to the /etc/hosts table for the IP address has fixed the problem. Many thanks.

6

Glad to have been of help.