this post was submitted on 04 Sep 2025
385 points (99.7% liked)
Non-Serious Technology
70 readers
19 users here now
A community for non- serious tech articles.
founded 3 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My Brother printer does not connect to my Linux computer over Ethernet on the same network no matter what I do. I have to physically connect PC to the printer for it to work. It also doesn't wirelessly work with it. I can only wirelessly talk to it through my phone using their app.
I hate printers. The moment someone offers a high quality, non-scummy, easy to use in every basic scenario printer compatible with Linux I will buy it and never stop buying it until something changes in those categories. Laser, inkjet, whatever. My use cases are hex maps and legal documents. If I could get a printer that made TCG quality cards in my house I'd buy that as well for a substantial price but that's because my childhood was saturated with card games and their animated shows. I digress.
Please make a good printer. Brother was supposed to be that but I've not had any success with their stuff for the past 6 or 7 years, even on windows.
After reading down a few comments...
FTFY
I mean... True. But my computer is Linux and my partner's computer is windows (for now 😈).
But like... What matters is the printer doesn't connect and therefore I'm upset. So framework come out with a printer.
Totally, not trying to criticise. I wanted to point it out so it doesn't scare any potential Linux newbies away. It's definitely a printer or network problem.
If you're reading this, Linux is easy. Jump over. It's great.
Really? My Brother MFP works fine on the network, and I'm on Linux. The phone does use the Brother print driver you have to download. But just for general computing use you ought not to be having any trouble with network printing so I'm curious.
Ya, I wish I could tell you what it is. Maybe I'm just not getting it - some simple step or something - or maybe I bought a weird model and it happens to be problematic everytime I've bought one (2 or 3 printers from them now).
I'd love to click print on my PC and hear the machine whirl up in the other room but right now I can only get that to happen if I have it directly connected to my PC.
Honestly sounds more like a network problem
Sure, but how. If the printer is plugged into a switch which my computer is plugged into, both going to the same router, why is there a network problem that could cause this?
all the cables are good? all the network configs are good? firewall maybe? does the switch not support a network feature that is required?
you didn't explicitly say it, so i have to ask: can the same computer running windows print over the network?
When I was on windows it could not print over the network. My partner who is still on windows can't either.
All the cables are good I've checked them myself.
Neither of our Firewalls should be set up to block it, although I admit I could have made a mistake here if the default config and one with minor tweaks would prevent it on both Linux and windows.
Network config is largely untouched although again I could have made a mistake here on Linux and windows.
The switch is ubiquity and so is the dream machine, I assume they're very capable.
Can you ping the IP of the printer from your PC? If not, is it part of the same subnet or are there VLAN shenanigans going on? If yes, did you try using the IP directly in Windows? I could imagine the switch blocking mDNS or something (which likely is the default discovery method).
If you can print from your phone, does that actually use the wifi network or does it connect using wifi direct (or some other mechanism)?
I can't, but my unifi gives me the same IP address that the printer says it has. I believe it's a part of the same subnet and there are no vlans as far as I'm aware.
I can try the IP on windows.
I'm not certain how I would check which wifi mechanism my phone is using.
I appreciate all the troubleshooting.
If the printer is able to get an IP address and shows up in Unifi, the connection from the printer to the controller must be fine. If your PC has internet access, it's connection must be fine as well.
If both are on the same subnet (in most cases, that would mean that the IP addresses of both devices only differ in the last block of digits, e.g. 192.168.1.28 and 192.168.1.10), they should directly connect through the switch. Blocking access there is definitely possible (VLANs, Port Isolation, ..), but none of those would be enabled by default, so I wouldn't expect them to be turned on if you didn't mess with them.
I suppose there is also a possibility, that access could be blocked directly on the printer. My Brother printer has a web interface, where you can enable/disable the different protocols and enable an IP whitelist. But those aren't enabled by default either, so they should be fine if you didn't mess with anything.
Overall, it's fairly hard to diagnose this remotely. I'd probably try the following:
That's assuming that you actually want to get it working. If you don't print a lot, just plugging in a cable every once in a while probably isn't too much of a hassle.
As 9blb says, this is a networking issue. Considering both your Linux and Windows machines cannot print over LAN or WAN, you should start at the switch.
Does the printer's port config match that of the Linux and Windows machines? For simplicity, they need to all be on the same VLAN and be access. For accessing machines within the same network, don't worry about routing traffic to the firewalls or dumping it to the router, that introduces needless complexity on a home network.
If that is true, then check the printer's network settings. The subnet and IP range need to match that of the Linux and Windows machines, allowing access over the same VLAN. While here, also check for duplicate IPs. If the IP range or subnet is wrong, your traffic will either drop at the switch or get dumped to the router/firewall depending on how you set the routes. If you have duplicated IPs, your network is gonna be confused on where to send the packets and kill whichever route it deems to be an imposter.
If that's all matching and you're still getting nowhere, double check your Linux and Windows machines to ensure you have the proper driver's installed.
Tried to print to an office printer yesterday for the first time and it worked immediately. Ricoh IM3000C or some mix of those letters.