I have an older MFC and both scan and print over LAN (wired) work. Both scan and print did not work at first. I had several weird issues with both scan/print, so I'll throw out some things that seemed to get one or the other working various times:
Ran sudo brsaneconfig4 -a name=Brother-Scanner model=Brother MFC-L2740DW ip=192.168.xxx.xx.
- Try the brsaneconfig4 command as root (not sudo), put name/model/ip in quotes and don't use hyphens in name/model (model no. not necessary.. mines called brotha fromanothamotha)
scanimage -L recognizes scannerbr
Fired-up xsane...receive an "Failed to open device 'brother4:net1:dev0' Invalid Argument.
- a) Did you try to scan from scanimage instead of xsane? What is the output of
scanimage > test.pnm and
scanimage -d "brother4:net1;dev0" --source FlatBed -p > test2.pnm? Same error as xsane? Also try as root.
b) Just noticed your xsane error has two colons in device name. Second one should be semicolon (see scanimage command above). Did you copy/paste that error?
- If those easy fixes fail, don't overlook your network settings, both in the MFC (check both web UI and on the MFC keypad buttons) and in your router. After working for a few months suddenly mywouldn't scan despite scanimage -L finding it (it may have been "invalid arg" but don't remember) and able to ping the IP from other LAN devices. After many frustrating hours, I fixed it by disabling the "bound to" (ARP binding) setting in my router (tomatousb) for DHCP reservations. I don't know why this worked, but the problem never came back, and it remains my only dhcp reservation without "bound to MAC address" checked.
I had a similar problem where it would no longer print but it would scan. The solution was to set MFC to get a DHCP address. Initially I gave it a static IP in the MFC settings, but it was very flukey. IMO the most reliable setup is MFC set to DHCP, router has a DHCP reservation for MFC (reservation, not a static IP), and if your router has the option, disable ARP binding.
If possible, try installing from scratch with (1) ethernet, (2) MFC internally set to get IP from DHCP server, (3) router set to reserve an address for MFC, (4) router set to NOT bind the reserved IP to a MAC address for MFC.
If that doesn't work, then: (5) jiggle the handle or (6) try turning the MFC, your router, your computer, all the light switches within walking distance, and your car off and on a few times.
I am happy with my MFC7860DW, but you quickly learn what the M and the F stand for after you get a few cryptic error messages. Which reminds me, the 7860DW ppd for cups doesn't actually work for the 7860DW. Instead, you must use the 7840DW ppd, which works perfectly. Why? Because it's a MF... C.