[SOLVED] CUPS is unable to find printer

sabreman · 2019-09-29 13:55:04

I'm trying to add my brother MFC-l2750DW wirelessly without using a static ip on the thing, and while cups finds it and adds it no problem, whenever I try to
print anything it just tells me that it's "Unable to locate printer 'BRW5413799F87FA.local'".

I have avahi-daemon running, and I was able to use avahi-discover to find it and avahi-resolve to get it's IP. It's uri entry when using
system-config-printer is "lpd://BRW5413799F87FA.local/BINARY_P1".

What am I doing wrong?

Last edited by sabreman (2019-10-06 13:00:33)

seth · 2019-09-29 14:13:53

https://wiki.archlinux.org/index.php/Av … resolution ?

sabreman · 2019-09-29 15:26:46

Yeah I've tried that, also restarted both the avahi and cups services after just in-case and it's still not able to find it.

ewaller · 2019-09-29 15:31:46

Can you ping the printer at BRW5413799F87FA.local ?
Does that printer serve a web interface? Can you reach that interface by browsing to BRW5413799F87FA.local ?

If the answers to these are no, it is probably not cups' fault.

seth · 2019-09-29 15:35:10

nslookup BRW5413799F87FA.local

Are you maybe using systemd-resolved?
(See the note: https://wiki.archlinux.org/index.php/Avahi#Installation )

sabreman · 2019-09-29 15:50:26

So I can't ping the printer or access it via the address (unless im typing it wrong which is possible). The systemd resolver is disabled and stopped, so my next idea is that my avahi is miss-configured?
This is what I have in the hosts lines in my nsswich.conf:

hosts: files mdns_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns

Edit: I should clarify that i can access the printer, ping, and print even if just use the ip address that "avahi-resolve -n" returns.

Last edited by sabreman (2019-09-29 15:57:55)

seth · 2019-09-29 16:22:49

You also do have nss-mdns installed?

sabreman · 2019-09-29 16:35:31

I do.

sabreman · 2019-10-06 13:00:07

So I'm not exactly sure how this got fixed, but it did. I literally just turned off my laptop for a few days because I was busy, then turned it on today, installed the base package in accordance to the recent news, and everything was able to auto-resolve the printer's address just fine. Firefox, ping, etc. I can now print to it without issues.

And it's not like

avahi-daemon.service

wasn't running or something, I confirmed it was operational last time I was messing with this.

Could this have been a local network issue of some sort? I'd love some input on this because this "solution" isn't helpful for anyone else experiencing this issue.

seth · 2019-10-06 14:33:12

If you had not rebooted before, the avahi daemon might have had a hiccup, maybe a caching issue, maybe unresponsive.
The base package itself is just a meta-packages the pulls in a bunch of dependencies.

Arch Linux

#1 2019-09-29 13:55:04

[SOLVED] CUPS is unable to find printer

#2 2019-09-29 14:13:53

Re: [SOLVED] CUPS is unable to find printer

#3 2019-09-29 15:26:46

Re: [SOLVED] CUPS is unable to find printer

#4 2019-09-29 15:31:46

Re: [SOLVED] CUPS is unable to find printer

#5 2019-09-29 15:35:10

Re: [SOLVED] CUPS is unable to find printer

#6 2019-09-29 15:50:26

Re: [SOLVED] CUPS is unable to find printer

#7 2019-09-29 16:22:49

Re: [SOLVED] CUPS is unable to find printer

#8 2019-09-29 16:35:31

Re: [SOLVED] CUPS is unable to find printer

#9 2019-10-06 13:00:07

Re: [SOLVED] CUPS is unable to find printer

#10 2019-10-06 14:33:12

Re: [SOLVED] CUPS is unable to find printer

Board footer