Fixing a Stuck Brother Printer & Getting Back to Production: A Field Guide for Urgent Situations

There is no single answer to a frozen Brother printer. What works for a single offline unit in a home office might be completely inadequate for a network of machines running a 48-hour catalog job. My experience is based on roughly 200+ rush orders over five years, many of which involved a Brother printer—like the HL-L2390DW—freezing up mid-print. If your situation involves an industrial press or a very different network topology, your steps might differ. I can't speak to that.

The upside of clearing a 'Receiving Data' hang-up is that it's almost always solvable. The risk is that a rushed reset can corrupt print queues or lose a job that was half-processed. I keep asking myself: is saving 30 seconds on a hard reset worth potentially losing the job that's already buffered?

Know Your Scenario: The 'Receiving Data' Hang

A Brother printer stuck on 'Receiving Data' isn't a hardware failure in most cases. It's a communication breakdown between your computer and the printer's onboard memory. The fix depends on where the data is stuck. I've found that the right fix depends on three common scenarios: a small data packet from a quick print, a large file from a catalog, or a potential memory corruption.

Scenario A: The Quick Print Hang (Single Page or Small Document)

This is the most common scenario I handle. Someone hits 'print' on a single-page flyer or a form, and the printer just sits there, refusing to move. The job is small, so the data is likely sitting in the printer's buffer. The solution is straightforward but requires a specific order of operations.

First, reject the print job on the printer itself. On the Brother HL-L2390DW, press the 'Cancel' or 'Stop' button. Wait 10 seconds. Then, on your computer, go to your print queue and delete the job. The key is to clear the job from both ends. I've seen people only do the computer part, leaving a ghost job in the printer's memory. That's a rookie mistake I made in my first year: assumed 'deleting from PC' was enough. Cost me an hour of head-scratching.

If the job clears, try printing a small test page directly from the printer's menu. If that works, your fix is done. If not, you're looking at the next scenario.

Scenario B: The Large File or Catalog Job (Multi-Page or High-Resolution)

Now we're talking about the e-commerce catalog solution. You've been printing a large PDF with high-resolution images, and the printer freezes on 'Receiving Data'. This is way more critical than a single page. The data could be part of a multi-hundred megabyte file. A simple cancel might not be enough.

My go-to here is a power cycle with a forced flush. Unplug the Brother HL-L2390DW from the power outlet, not just the power button. Wait 60 seconds—not 10, not 30. I've found that a minute allows the capacitors to fully discharge and clear the internal memory. While it's unplugged, restart your PC. When both are back up, check the printer's memory to confirm it's empty (print a configuration page). Then resend the catalog job.

Seriously, this works 80% of the time. The power cycle flushes the jammed communication state. But if you get stuck again, there's a tactical nuclear option.

Scenario C: The Factory Reset (Last Resort)

This is for when the printer is stuck in a loop. It will show 'Receiving Data' even after a power cycle and even when you send nothing to it. Something got corrupted in the internal firmware or settings file. I've encountered this three times in the last two years—twice after a bad driver update.

To do a full reset on the Brother HL-L2390DW, you need to access the printer's menu:

  • Press 'Menu'.
  • Navigate to 'Initial Setup'.
  • Select 'Factory Reset'.
  • Confirm when asked 'Are you sure?'.

This will erase your network settings and any stored jobs. You'll need to reconnect to Wi-Fi and re-add the printer on your computer. It's not ideal, but it's better than a $200 service call. I'd only recommend this if Scenario A and B both failed, and you're staring at a deadline that's already passed.

How to Tell Which Scenario You're In

Ask yourself these two questions:

  1. What was the job size? A single page is quick, but a 500-page catalog requires more memory. If you printed a small form, go to Scenario A. If it was a large catalog or high-resolution PDF, start with Scenario B.
  2. Did a power cycle fix it? If not, and the printer was working fine before a recent driver update, you've likely corrupted something in the firmware. That's your cue for Scenario C.

Bottom line: a stuck 'Receiving Data' message does not mean a dead printer. It usually means a temporary communication error. The fix takes 5 to 15 minutes. In my experience managing rush orders, that 15 minutes of troubleshooting is way less costly than the 2-hour round trip to swap a printer under service warranty. Total cost of ownership includes your time, not just the machine.

(Should mention: this is based on my experience with the HL-L2390DW and similar models. If you're using a different unit, your menu paths might vary. Check the manual.)