I have a Brother MFC-L2700DW
. I am trying to set it up on my Linux Ubuntu 16.4. I have installed the driver, and the printer appears in settings. It is also connected via my wireless router, and I can see it in my router settings.
I have just added the printer to a new laptop running Ubuntu 18.4. It installed and connected flawlessly the first time. I use it wirelessly going through my Sagemcom F@st 5260
router.
Why would the work on one and not the other? Properties have:
Description: MFCL2700DW
Location: *blank*, i.e. empty
Device URI: file:///dev/null
Make and Model: Local Raw Printer
Printer Status: Idle
The same properties on the working computer are:
Description: *blank*
Location: *blank*
Device URI: ipp://BRW70778128A937.local:631/ipp/print
Make and Model: Brother MFC-L2700DW series, driverless, cups-filters 1.20.2
Printer Status: Idle
For some reason I have this printer defined twice, the other settings are:
Description: MFC-L2700DW
Location: *blank*
Device URI: dnssd://Brother%20MFC-L2700DW%20series.ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-30055cafa9b
Make and Model: Brother MFC-L2700DW for CUPS
Printer Status: Idle
Yes, I know that the file:///dev/null
is the elephant in the room, but I don't know what would belong there or even how to generate that file for this particular computer.
Help/suggestions would be super appreciated.
Update 12/25/18 .... Per advice I ran
sudo dpkg -i --force-all mfcl2700dwlpr-3.2.0-1.i386.deb
and verified with:
dpkg -l | grep Brother ii brscan-skey
0.2.4-1 amd64 Brother Linux scanner S-KEY tool ii brscan4
0.4.6-1 amd64 Brother Scanner Driver ii mfcl2700dwcupswrapper:i386
3.2.0-1 i386 Brother MFC-L2700DW CUPS wrapper driver ii mfcl2700dwlpr:i386
3.2.0-1 i386 Brother MFC-L2700DW LPR driver ii printer-driver-brlaser
3-5~ubuntu1 amd64
printer driver for (some) Brother laser printers ii printer-driver-ptouch 1.4-1
amd64 printer driver Brother P-touch label printers
According to
I should have the commands...
/etc/init.d/lpr restart
/etc/init.d/lprng restart
...to run, but I have neither. Quite odd, because my other computer, the one the printer works correctly with also does not have lpr or lprng.
update 12/26/2018 --- ! solved see answer below ! ------------------------------------