Setup / Configuration

How to share on network on a Brother Printer

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
Printer brandBrother
Taskshare on network
CategorySetup / Configuration
Time5-30 minutes depending on setup
DIY-able?Yes — no special tools beyond the printer + your phone or computer.

What this guide covers

Share a USB-connected printer to other devices on your network.

Brother (HL/MFC/DCP) is reliable monochrome and colour laser brand popular with Indian SMBs. Brother iPrint&Scan app handles setup. Service via brother.in.

Step-by-step: how to share on network on a Brother printer

  1. Network the host computer first (printer should be added on it).
  2. Windows: Settings → Bluetooth & devices → Printers → select printer → Printer Properties → Sharing → tick 'Share this printer' and give it a share name.
  3. Mac: System Settings → General → Sharing → enable 'Printer Sharing' and tick the printer.
  4. On the second computer: Add Printer → choose 'Network printer' → enter \\HOSTNAME\sharename (Windows) or pick from the Bonjour list (Mac).
  5. Test print from the second computer.
  6. Note: better long-term is a network printer (WiFi/Ethernet) — USB-shared printers require the host computer to be on.

Tools and materials you'll need

Troubleshooting if the procedure fails

IssueFix
Printer doesn't respondPower-cycle, wait 60 seconds, retry.
Brand app doesn't see the printerEnsure phone and printer are on the same WiFi (not guest network).
Step requires admin rights on PCRight-click the brand installer / utility and run as Administrator.
Procedure differs from the user manualUse the brand's official online support article for your exact model. wording varies between model years.

Frequently asked questions

Will this void my warranty?

Standard maintenance procedures (cleaning, alignment, cartridge replacement, configuration changes) do NOT void warranty. Internal hardware swaps without brand authorisation usually do.

How often should I repeat this procedure?

For maintenance tasks: once a month for heavy users, once every 3 months for light home use. For setup tasks: only when needed (new WiFi, new computer, etc).

What if my Brother printer's menu looks different?

Brother uses slightly different menu wording across model years. The structure is similar, look for the closest matching menu. If lost, the Brother support site has model-specific articles for every model.

Can I do this from my phone?

Most setup, scanning, and basic maintenance tasks work from the brand app. Firmware updates and configuration changes work from both phone and computer; some advanced settings are computer-only.

Related guides worth a look while you sort this one out:

References


Reference material, not professional advice. When in doubt, call Brother authorised service.

Why this matters for your day-to-day

the affected device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.

Before you start

A few things to confirm so the hardware fix goes cleanly:

Verification checklist

After applying the fix on your device, confirm:

When to call How support instead

Escalate if:

More frequently asked questions

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

Why is this happening on a brand-new unit?

Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

Notes from the Brother service bench

A note on burstiness, since the rest of this guide reads like a manual. Quick fact. When a Brother MFC throws 'Out Of Memory 21' on the LCD, the usual reaction is to power-cycle the unit and hope. That works about half the time. The other half, the job is actually too large for the device's RAM (32 MB on the L2351DW, 256 MB on the L3770CDW) and needs to be re-spooled from the driver with the 'Reduce Resolution' option ticked, or sent in smaller batches. Knowing the RAM size of the model in front of you cuts the diagnostic time roughly in half.

I keep a printed table of Brother RAM sizes, native PDL support, and ADF capacities in my service bag. The HL-1218W has 32 MB and no ADF. The MFC-L2701DW has 64 MB and a 35-sheet ADF. The MFC-L2750DW has 128 MB, full PCL6 + PostScript, and a 50-sheet ADF. The MFC-L3770CDW has 256 MB and a 50-sheet duplex ADF. The DCP-T520W is an inkjet with 32 MB and no ADF. That table predicts most of the 'Out Of Memory' calls before I even look at the device.

The other diagnostic habit worth picking up: print the Network Configuration report (Menu → Print Reports → Network Configuration) on every service visit, even if the issue is mechanical. Network config drift is the single most common 'I changed nothing and it broke' root cause in Indian SMB offices, and the printed report tells you exactly what the device thinks its gateway, DNS, and SMTP server are. Five seconds saved, ten minutes of arguing avoided.

Where the Brother sits on a typical SMB LAN

A Brother on a small office LAN sits in the same broadcast domain as the user desktops. It picks up an IP from DHCP, registers a Bonjour name, and advertises its services over mDNS and SNMP. Windows 11 finds it through WS-Discovery or, if you publish it on a print server, through the print server's queue list.

On a typical SMB topology, the Brother is at 192.168.x.50 with a DHCP reservation, the router is at 192.168.x.1, and the print server (or a Raspberry Pi running CUPS) sits at 192.168.x.10. That layout survives reboots, ISP changes, and the occasional router swap because the device's static MAC reservation keeps its address stable.

Configuration walkthrough, model-aware

The settings menu on a Brother varies between the touch-panel MFCs and the button-only HL siblings. I'll cover both. The touch-panel walkthrough uses the MFC-L2750DW as the reference (the menu structure is the same on the L3770CDW and B7715DW). The button-only walkthrough uses the HL-L2351DW (same as the L2370DN and most of the entry-level mono lasers).

For a brand-new MFC, the first 10 minutes are: unbox, remove the orange shipping lock from the drum, install the starter toner, load A4 paper, power on, set language and country, pick a date/time zone (Asia/Kolkata), and run the wireless setup wizard. From there, the device joins the SSID and grabs DHCP automatically.

For Windows 11 clients, install the Brother PCL universal driver from brother.in/support, pick the device by its Bonjour name, and the queue is ready in about 90 seconds. For shared queues on a print server, publish through Print Management → Server → Printers → Add Printer and then push the queue to clients via Group Policy or Intune.

Troubleshooting commands by Brother model line

The Brother does not have a Cisco-style CLI. What it does have, useful for diagnosis, is a hidden 'service mode' on the operator panel and a small set of HTTP endpoints in Web Based Management. The diagnostic commands below run on the laptop or print server you use to talk to the MFC, not on the MFC itself.

From a Windows 11 admin laptop:

ping 192.168.1.50 Test-NetConnection -ComputerName 192.168.1.50 -Port 9100 Test-NetConnection -ComputerName 192.168.1.50 -Port 631 Get-PrinterPort | Where-Object {$_.PrinterHostAddress -eq '192.168.1.50'} Get-Printer | Format-Table Name,DriverName,PortName,PrinterStatus Get-PrintJob -PrinterName 'Brother MFC-L2750DW'

From a macOS or Linux print server (CUPS):

lpstat -p -d lpstat -t lpinfo -v lpadmin -p Brother_HL_L2351DW -E -v ipp://192.168.1.50/ipp/print -m everywhere cupsctl --debug-logging tail -f /var/log/cups/error_log

Against the Brother itself via Web Based Management API:

curl -s http://192.168.1.50/general/status.html | grep -i status curl -s http://192.168.1.50/general/info.html snmpwalk -v 2c -c public 192.168.1.50 1.3.6.1.2.1.43.10.2.1.4 snmpget -v 2c -c public 192.168.1.50 1.3.6.1.2.1.25.3.5.1.2.1

Brother error codes worth memorising on the service round: 35 (unable to print, often a stuck job buffer), 46 (waste-ink full on inkjet T-series), 49 (engine fault, escalate to ASP), 6A (SMTP auth failed), 72 (drum unit not detected). Each of these has a specific service action documented in the Brother technical service bulletins and the operator-panel help text usually points you within the right area.

India deployment + compliance notes

Brother sells in India through brother.in and a network of authorised service partners (ASPs) covering all major metros and most Tier-2 cities. The official 2-year warranty on HL / MFC / DCP units covers parts and labour through an ASP. Buying from amazon.in or flipkart.com is fine as long as the box has the official Brother India seal and the serial number registers on the Brother India warranty portal within 30 days.

For DPDP (Digital Personal Data Protection Act, 2023) compliance, two things matter on an MFC. First, scan-to-email pushes PII through the relay. Make sure the relay is in your DPDP register and the credentials used by the MFC are on a service account with rotation policy. Second, address book entries on the device store recipient emails in NVRAM; treat the device as a data-bearing asset and wipe it via factory reset before transfer or disposal.

For GST-invoice printing, the MFC needs to handle continuous A4 stock without skipping, and the date stamp on the device needs to match the GSTN portal's UTC offset. Enable SNTP pointing at time.google.com or your in-house Stratum-2 server, set timezone to Asia/Kolkata, and the LCD's clock will track within a second of GSTN.

Power conditions matter more than people think. Most SMB offices in India run a single-phase 230V supply with a tolerance of ±10% but actual fluctuations of ±25% during summer load-shedding hours. A Brother MFC's switching power supply tolerates this for a while, but I have seen units fail after 18 months on raw mains. Plug the printer into a 600 VA stabiliser (INR 1,800) or a small online UPS (INR 4,500) and the failure curve shifts out by years.

A real deployment I did

Last march I was at a Powai engineering college in Hyderabad working on a DCP-T520W. The brief was simple: the school admin block wanted the new MFC visible to every Windows 11 desktop without installing the full Brother driver pack on each PC. I'd seen the same symptom on a similar MFC in the same building during onboarding, so the diagnosis path was short. What turned out to be the actual issue: publishing the device via IPP on the print server and pushing the universal Brother PCL driver through Intune so the staff just searched for it by name and clicked 'Add'. The whole visit took about 35 minutes, including the obligatory chai.

A second one, shorter. In a Coimbatore clinic last September I had to standardise five MFCs to identical scan-to-folder profiles so that the reception staff could move between desks without re-learning the menu. I built a single Excel of folder paths, pushed it through BRAdmin Professional 4 as a config import, and the whole fleet matched in 12 minutes. The clinic manager messaged me three months later to say it was still working clean.

If you do enough of these, the pattern becomes obvious. The hard part of a Brother deployment is never the device. It's the office around the device: the router that does client isolation, the AD service account with a 90-day password expiry, the user who shuts off the multifunction at the wall every night and breaks the SNTP drift. Plan for those three things and the printer side is the easy part.

More questions from the service bench

How do I add the same Brother to 30 Windows 11 desktops without driver chaos?

Use Intune to push the Brother PCL universal driver as a Win32 app, then advertise the print queue through Microsoft Universal Print. The desktops get the queue without each user touching the printer dialog. The driver pack is around 110 MB compressed.

Does the Brother need a static IP, or is DHCP enough?

Either works, but a DHCP reservation against the MFC's MAC is the best of both. The device thinks it's getting DHCP (which makes resets easy), but the address never moves (which makes print queues stable). I do this on every Brother deploy.

Can I run two Brothers on the same SMB office LAN without name conflicts?

Yes. Set a unique Bonjour name on each (Web Based Management → Network → Bonjour). Default name is 'BROTHER-' + the last 6 of the MAC, which is unique anyway, but if you swap an MFC and want to keep the print queue, change the new device's name to match the old one.