In the vast majority of cases, a Brother printer that reports "offline" is not actually broken or disconnected. It is showing an old IP address. Windows and macOS remember the network address a printer had when it was added, and most home routers hand out addresses using DHCP, which reassigns them periodically. When the printer's real address drifts from the one your computer has stored, the computer stops finding it and slaps an "offline" label on it, even though the printer itself is sitting there, powered on, connected to Wi-Fi, and perfectly willing to print.
The second most common cause is Windows' own "Use Printer Offline" setting, a manual toggle buried in the print queue that can get flipped on by a failed print job and then simply stays on until someone switches it back. Neither of these has anything to do with the printer's hardware, which is why unplugging it, restarting the router, and buying a new USB cable so often fail to fix the problem for good.
This guide walks through both quick fixes and the permanent one, in the order that actually resolves the issue fastest.
Why does a fully connected printer show as offline?
Every Brother network printer, whether it is a DCP, MFC, or HL model, gets its IP address from your router unless you have told it otherwise. Consumer routers typically renew DHCP leases anywhere from every 24 hours to every seven days, and each time a lease renews, there is a chance the printer gets handed a different address. Your PC's printer driver, however, keeps using the address it was configured with when you first installed it. The moment those two addresses diverge, print jobs go nowhere and the status changes to offline.
Brother printers have a second quirk worth knowing: if a printer loses its DHCP lease entirely (for instance after a router reboot happens faster than the printer reconnects), it will fall back to a self-assigned APIPA address in the 169.254.x.x range. That address is only valid on the printer's own network segment, so your computer, sitting on a normal 192.168.x.x network, cannot reach it at all. This is one of the most common causes of a printer that goes offline overnight and only comes back after you power-cycle it.
Sleep mode compounds the problem. Brother's eco-friendly deep sleep setting, which on many inkjet models kicks in after as little as one minute of inactivity, drops the printer's network interface into a low-power state. Laser models generally wake and rejoin the network within a second or two because there's no print head to prime; some inkjet models take noticeably longer, and if your PC tries to print during that gap, it can register the timeout as an offline printer rather than simply retrying.
The quick fixes to try first
Before touching network settings, rule out the easy causes. These take under five minutes combined and fix a surprising number of cases.
Clear the manual offline toggle. Open Devices and Printers, right-click your Brother printer, and check whether "Use Printer Offline" is ticked. If it is, click it once to switch it off. This single setting, on its own, accounts for a large share of "offline" reports on Windows, because a stalled or cancelled print job can flip it automatically.
Restart the print spooler. Windows manages all print jobs through a background service called Print Spooler. If it hangs, every printer on the system can show as offline or unresponsive, not just the Brother one. Open Services (services.msc), find Print Spooler, and restart it. If jobs were stuck in the queue beforehand, clear the queue first or the stuck job can jam the spooler again immediately.
Set the printer as default and remove duplicates. Brother's installer sometimes creates a second printer entry, particularly after a driver reinstall or when both the printer and the "fax" driver component get added. If your PC is sending jobs to a stale duplicate entry, the live one will never show activity. Delete any duplicate Brother entries and confirm the correct one is set as default.
Power-cycle printer and router together. Turn the printer off, turn the router off, wait about ten seconds, bring the router back up first and let it fully settle, then power the printer back on. This forces a fresh DHCP handshake and clears an APIPA fallback address if that's what caused the drop.
The real fix: give the printer a fixed address
Quick fixes clear the symptom for a day or two; a static IP or DHCP reservation clears it for good, because it stops the printer's address from ever changing again.
There are two ways to do this, and which one is right depends on how comfortable you are with your router's admin panel.
DHCP reservation (recommended). Log into your router's admin page, find the DHCP client list, locate your Brother printer by its name or MAC address (printed on a network configuration sheet you can print from the printer's control panel menu), and reserve its current IP address permanently. The router will keep handing out that same address to the printer every time, and your PC's driver never goes stale. This is the approach Brother's own support documentation and most network administrators recommend over a fully static IP, because the printer still gets its gateway and DNS settings automatically from the router rather than needing them entered by hand.
Static IP on the printer. From the printer's control panel, go to Network settings, then TCP/IP, and set Boot Method to Static rather than Auto. You will need to enter the IP address, subnet mask, and gateway manually, and the address you choose must sit outside your router's DHCP range or you risk a future conflict when the router hands that same address to another device. This method works but is easier to get wrong than a DHCP reservation, and it's a step some users skip only to find their printer offline again after the next router firmware update resets DHCP ranges.
Once either is in place, remove the printer from Windows or macOS and re-add it using the new fixed address, so the driver isn't still pointed at the old, changeable one.
Wi-Fi Direct and dual-network conflicts
If your Brother printer supports Wi-Fi Direct, a peer-to-peer connection Brother includes so a phone or tablet can print without joining your home network, it's worth checking whether it's been left switched on. A printer connected to both your infrastructure Wi-Fi and broadcasting its own Wi-Fi Direct network can occasionally confuse which interface a given device should use to reach it, particularly on phones that auto-connect to the printer's direct network out of habit. Turning Wi-Fi Direct off from the printer's Network menu, if you aren't actively using it to print from a mobile device, removes this as a variable entirely.
USB-connected printers going offline
Offline errors aren't exclusive to network printers. Over USB, the usual causes are different: a USB hub or port entering selective suspend to save power, a cable fault, or a driver that's lost track of the port. Plugging the printer directly into a rear motherboard USB port rather than a hub, and disabling USB selective suspend for that port in Windows' power plan settings, resolves most recurring USB offline errors. If the printer reconnects fine after a cable swap but drops offline again after a few hours, the fault is almost always the power management setting rather than the cable itself.
Comparing the causes and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Offline appears randomly, clears after restart | DHCP lease changed | Set a DHCP reservation on the router |
| Offline every morning after being idle overnight | Printer fell back to an APIPA address | Power-cycle router then printer; reserve IP |
| Offline immediately after a failed or cancelled print job | "Use Printer Offline" toggled on | Untick it in Devices and Printers |
| All printers on the PC show offline, not just Brother | Print Spooler service hung | Restart the Spooler service |
| Only offline when printing from a phone, fine from PC | Wi-Fi Direct interfering | Disable Wi-Fi Direct if unused |
| USB-connected printer drops offline after being idle | USB selective suspend | Disable selective suspend for that port |
| Offline since a router firmware update or replacement | DHCP range or settings reset | Re-check and re-apply the IP reservation |
Should I just factory reset the printer?
It's tempting, and Brother's own support line will sometimes suggest it as a first step, but a factory reset wipes the printer's Wi-Fi credentials, network name, and any static IP configuration, which means you're rebuilding the connection from scratch rather than fixing the actual cause. It's worth doing only if the printer's network settings appear genuinely corrupted, for example if it won't take a static IP at all or the control panel network menu behaves erratically. For a standard offline error, a factory reset without addressing the underlying DHCP or spooler issue tends to produce exactly the same offline error again within a few days.
What if it's still offline after all of this?
Run a ping test from the command line (ping followed by the printer's IP address) while the printer shows offline. If the ping fails outright, the problem sits at the network level, most likely your router or the printer's Wi-Fi radio, and reconnecting the printer to Wi-Fi from its own control panel is the next step. If the ping succeeds but Windows still shows offline, the fault is local to the driver, which means removing the printer entirely, deleting any leftover print queue entries, and reinstalling it fresh from Brother's current driver package for your exact model is more reliable than repairing the existing installation. Outdated firmware can also cause intermittent drops on older units, so it's worth checking the printer's control panel for a firmware update while you're there.
Related Guides
- for readers on Windows 11 specifically, where the Devices & Printers path differs slightly from older versions.
- useful if the offline error started right after setup, since a bad initial install is a common root cause on macOS.
- for anyone who needs to rejoin the printer to the network from scratch after a factory reset or router swap, as covered in this article's final section.
- worth a look if you manage a mixed-brand office, since the DHCP and spooler causes are near-identical across manufacturers.