Unable to use Brother MFC-L8850CDW scanner over LAN

English Network/Internet
1

I’ve not needed to use this scanner since upgrading from 13.2, however I now discover that xsane can no longer find the scanner. I fact neither can YAST.

Here’s what I have so far:
All drivers are downloaded from http://support.brother.com/g/b/downloadtop.aspx?c=us&lang=en&prod=mfcl8850cdw_us_eu_as and installed


# brsaneconfig4 -q | grep BrotherAtLamb
  0 BrotherAtLamb       "mfc-l8850cdw"      I:10.0.0.114



# scanimage -L


No scanners were identified.

udev rule is created under /etc/udev/rules.d/

#Brother scannersATTR{idVendor}==“04f9”, MODE=“0664”, GROUP=“lp”, ENV{libsane_matched}=“yes”

suggestions?

2

Check that you can ping your printer by IP address first

ping 10.0.0.114

BTW, the udev rule is only needed for access to USB connected scanners.

3

If you can ping the scanner ok, then run the following command to diagnose the connection

brscanconfig4 -d

Also, make sure that ‘brother4’ driver entry is present in /etc/sane.d/dll.conf

4

Thank you

I got a good ping (2.61ms)

BTW, the udev rule is only needed for access to USB connected scanners.

ah hah, thanks

If you can ping the scanner ok, then run the following command to diagnose the connection

brscanconfig4 -d

linux-nx75:~ # brscanconfig4 -dIf 'brscanconfig4' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf brscanconfig4
linux-nx75:~ # cnf brscanconfig4
brscanconfig4: command not found                              
linux-nx75:~ #

Also, make sure that ‘brother4’ driver entry is present in /etc/sane.d/dll.conf

Not present

5

this makes no sense but…

I just clicked on xsane expecting nothing, but it found the scanner, made the scan and wrote the PDF.

Not sure what I did to bring that about. I’d made no changes since my last post.

As my Daddy used to say “if it ain’t broke don’t fix it”, so I guess I’ll leave it alone now.

Thanks Deano

6

My bad…that was a typo. It should have been

brsaneconfig -d
7

No worries. I read somewhere that a restart was needed following the configuration step, so maybe that was it? Anyway, good that it’s working as expected now. :slight_smile: