Brother Printer Not Printing? Read Its Reports First

When a Brother printer is not printing, its own display and reports can tell you more than the status word on a computer. A local report proves the machine can act without Windows or macOS. A WLAN report can show whether Wi-Fi actually connected. A network configuration report can reveal whether a driver is still pointing at yesterday's address.

I would use those facts before removing the printer or resetting its network. Brother's product families and connection modes differ, so the exact report name and menu path must come from the support page for your model.

Read the Brother Display Before the Computer

Wake the machine and copy the exact message, code, or light pattern. Ready, Offline, Replace Toner, No Paper, Jam, Manual Feed, and a held-job prompt lead to different repairs.

Resolve a visible device condition first. Check ordinary user-access areas named in the manual, make sure the loaded paper matches the selected tray, and close normal covers firmly. Do not force an inaccessible jam or reach into a powered laser mechanism.

Brother's current unable-to-print guidance treats the operating system and USB, wired, or wireless connection as separate routes. That matters. A generic instruction to “reconnect the printer” is incomplete until you know which route it uses.

Stop for a hot smell, smoke, grinding, damaged power parts, leaking ink, or loose toner outside the normal replacement area. Software cannot make unsafe hardware safe.

Print the Report That Answers Your Question

Brother models use names such as Printer Settings, User Settings, Network Configuration, WLAN Report, Print Quality Check Sheet, or Test Print. The names are not interchangeable.

I would use the exact manual to print one relevant report. A clean local page weakens theories about toner, ink, paper movement, and the basic print mechanism. It does not prove the computer selected the right queue.

I would keep the report private if it contains an IP address, network name, device identifier, or organization details. I need the facts, not a public screenshot.

Choose the Real Connection: USB, Wired, Wi-Fi, or Print Server

Look behind the printer and inspect the approved setup on the computer. Do not assume a Brother with Wi-Fi capability is using Wi-Fi today. An office model may be wired to a switch but installed through a print server; a home model may have both an old USB instance and a newer wireless one.

I would open the print dialog and read the complete destination name. If two Brother entries exist, preserve them until one plain page identifies the live route. Deleting both immediately destroys a useful comparison.

For a generic stuck queue or duplicate destination, use the printer troubleshooting pillar. If the Brother has left the network entirely, use the printer Wi-Fi connection guide before changing brand-specific software. The rest of this page follows Brother's connection-specific evidence.

For Wi-Fi, Start With the WLAN Report

Brother's wireless printing procedure tells users of the listed model to print a WLAN report, read its connection status or error code, confirm the wireless interface is enabled, and verify the computer and printer are on the network.

The linked page is tied to a particular model family, so use your model's version of the procedure. The diagnostic logic is still useful.

1. Confirm the Brother display has no blocking error.
2. Print the model's WLAN report.
3. Read Connection and any error code rather than guessing from signal bars.
4. Verify the computer is on the intended network, not an isolated guest network.
5. After restarting network devices, allow the time named by Brother for the machine to rejoin before testing.

Brother's example procedure says to wait at least five minutes after the router, computer, and machine restart sequence before trying to print. Treat that as the model-specific minimum used by the linked procedure, not a universal timer for every network. It prevents judging the test before that documented machine has had the stated time to reconnect.

If the router or network name recently changed, reconnect the printer using the exact model setup. A factory reset is not the first way to update one Wi-Fi relationship.

Use Network Connection Repair Tool With One Important Caution

For supported Windows models, Brother's Network Connection Repair Tool can locate the printer and update the IP address stored in the printer driver. Brother's current tool documentation says it can assign the correct IP address and subnet mask, then asks the user to confirm the result with a Network Configuration Report or Printer Settings page.

I would run it only when the model and Windows setup support it, the Brother is on the same trusted network, and I have the required administrator permission. I would retest one plain page afterward.

There is a meaningful exception. Brother warns that enabling automatic connection repair is not recommended when a network administrator assigned a static IP address, because the tool can change that address. On a managed network, preserve the configuration and contact the administrator instead of “repairing” it locally.

That warning is exactly why brand-specific guidance matters. A tool designed to fix a home driver's stale address can create a new problem on an office printer with an intentional static address.

For Wired Ethernet, Look for a Physical Link

On a wired Brother, check that the network cable is seated at the printer and switch, router, or wall port. Where the hardware exposes a link light, Brother's connection guidance uses a lit or blinking Link LED as evidence that the physical connection exists.

No link light keeps the cable, port, switch, or printer interface in scope. If permitted, test a known working cable or approved port. A healthy link does not prove the driver has the correct address, so compare it with the Network Configuration Report before reinstalling anything.

In a workplace, do not move a cable to an arbitrary jack. Network ports can belong to different segments or security policies. Record the port and ask the administrator.

For USB, Remove Network Assumptions

A direct USB setup does not need a WLAN report to deliver a page. I would confirm the computer selected the USB-connected Brother instance, reseat both ends, avoid an unpowered hub, and test a known working computer port if available.

If the machine prints a local report but never appears over USB, use Brother's exact operating-system and model setup. Avoid third-party driver sites. If it appears twice, send one plain page through the instance that matches the active USB route and remove the stale copy only after success.

Do not reset Wi-Fi merely because USB printing failed. Those are separate configurations.

Managed and Print-Server Brother Printers Need a Different Boundary

A school or office Brother may be connected through a managed server queue or administrator-assigned address. It can also be subject to organization-specific authentication or release controls. Check four boundaries before changing it.

1. Record the queue name, connection path, and exact machine message.
2. Ask whether another authorized user on the same approved route can print.
3. Report a shared failure when everyone is affected.
4. Preserve the printer configuration when only one computer fails.

Do not run Network Connection Repair Tool, disable a firewall, create a direct-IP bypass, or reset the Brother without administrator approval. Those moves can evade controls, break accounting, or hide the actual print-server failure.

A job that reaches the Brother but waits for a PIN or badge release is not lost. Read the machine display and follow the organization's release process.

When the Machine Prints a Report but the Computer Does Not

A clean local report establishes a boundary. Leave toner, ink, drum, and head cleaning alone for the moment. Watch one plain computer job.

If it remains in the queue, inspect the selected Brother route and connection. If it leaves normally but nothing happens, read the display immediately for a tray, paper-size, manual-feed, secure-print, or held-job prompt. One document can ask for a condition the machine is waiting to receive.

If a second authorized device prints through the same approved route, focus on the first computer. If neither does but the local report stays clean, preserve the shared connection evidence.

The operating system saying Ready is not stronger evidence than a page. Demand the page.

When the Brother's Own Page Is Blank or Damaged

Now the connection is not the leading branch. Use the exact model's local print-quality or consumable procedure.

Brother's current inkjet support uses a Print Quality Check Sheet on supported models to show missing lines and color blocks. A laser model does not use that inkjet nozzle-cleaning route. Follow the exact laser model's toner, imaging, paper, and safety instructions instead.

Record whether the problem began after a cartridge, toner, drum, paper, or transport event. Check only setup items named in the manual, such as properly seating a supported supply or removing documented shipping material. An estimated supply level is not proof of good output.

If a local report is clean but only one PDF is wrong, test plain text from another trusted application. That isolates document settings without disturbing a healthy printer.

Two Brother Cases That Look Similar at First

In the first case, the display says Ready, a Printer Settings page is clean, the WLAN report says Connection OK, but Windows holds jobs under Offline. I would compare the selected Brother instance and its address with the current report, then use Network Connection Repair Tool only if the model, Windows setup, and network policy support it. I would not replace toner.

In the second case, the computer job leaves normally, the Brother feeds paper, and both that page and the local quality sheet are blank. I would stop changing the queue. The machine reproduced the output problem without the computer, so the exact inkjet or laser quality path now owns the diagnosis.

The third case belongs in the office. The local report is clean, several colleagues cannot print through the same server queue, and direct changes are restricted. That is a shared managed-service incident. Preserve the queue and report it rather than creating five different local workarounds.

Reinstall and Reset Come After the Reports

Reinstall Brother software only after the machine state is clear, the chosen connection is known, the relevant report is good, the correct destination is selected, and the supported repair route still points to a damaged driver or installation.

I would use Brother's official download page for the exact model and operating system. After installation, I would print the same plain page used throughout the diagnosis.

Brother documents different reset scopes on supported model families, but their names and retained settings vary. Follow only the exact model's official sequence, and first record what its warning says will be erased. A clean local page plus a stale computer address usually argues for a narrower connection repair, not a factory reset.

Build a Useful Brother Support Record

Record the model, operating system, connection type, exact display state, selected queue, local report name and result, WLAN or network status, job behavior, and the outcome of one plain-page test. Add whether the printer uses a static address, server queue, or secure release when that information is safe and relevant.

Do not include network passwords, account codes, private document titles, or a public photo of the full network report.

The practical finish is to make the Brother tell you what it knows. Read the display, print the right report, identify the actual connection, and apply the repair designed for that path. Reports preserve clues. Resets erase them.