I have a Brother HL-L2300D printer, connected by USB to a Raspberry Pi serving as a print server for a LAN segment somewhere. The Pi runs Raspbian, and has a samba server and a CUPS server running - the exact configuration of which I had forgotten about - and it was happily humming along for a couple of years, printing as requested.
Then about a week ago, users of several Windows 10 machines on the LAN started complaining about print failures. I was telling people to try removing the printer, then re-connecting to it (which in some cases seems to work for printers); but - they were unable to connect to the printer.
We checked that the printer itself works when directly connected one of those Windows boxes (via USB); and that, on the CUPS web interface, the printer is enabled and a test page prints correctly. The printer's CUPS management page says:
brother-hl-l2300d (Idle, Accepting Jobs, Shared, Server Default)
The error message people get when trying to connect the printer is:
Windows couldn't connect to the printer. Check the printer name and try again. If this is a network printer, make sure that the printer is turned on, and that the printer address is correct.
I should mention that \\1.2.3.4\
is browseable (where 1.2.3.4 is the print server's IP), and shows the printer. It's just the connection that fails.
My question: What could cause this failure, and what can I do to overcome it?
Additional information (ask if anything is missing):
- I've tried uninstalling the Windows print driver for the printer, then adding a printer with the new driver. This gets me to the "Can't Connect" error before the dialog in which I can provide the new driver.
iptables --list
on the Pi print server yields empty lists.- The version of Samba is: 4.5.16
- The Raspbian version is 9.
- When I try to Open rather than Connect to the printer, I get an Error 0x709.
cupsd.conf
: here (pastebin.com)