Cannot add networked Brother MFC-7820N after upgrading to Leopard

Question

Cannot add networked Brother MFC-7820N after upgrading to Leopard

Hi,

I did a clean install of Leopard on a new drive I installed on my Macbook. Then I migrated my account from an old drive which was running the latest version of Tiger.

Leopard is running fine, except that I cannot add my networked printer (Brother MFC-7820N). According to Brother, the printer drivers come with the Leopard CD. In the /Library/Printers/Brother directory there sub-directories for Brother LUT, Filter, Icons, Profiles, Utilities. So I think the drivers are present.

In the Print & Fax system preference, I click to add a printer and nothing shows up under "Default". According to Brother's instructions, the printer should show up. Is the MFC-7820N Bonjour capable?

Is there something else I need to do? I am not running control center like I did under Tiger.

Any help would be appreciated.

Network is a wireless network with the printer attached to a netgear wireless router.

MacBook - Black stock model, Mac OS X (10.5.1), Core Duo Machine

Posted on Jan 17, 2008 9:50 AM

Reply

Answer 1

Jan 17, 2008 10:00 AM in response to Eric Replogle

Okay, I found the answer to the problem. It is a Brother configuration, not a Leopard one. Needed to setup Bonjour on the printer by configuring the mDNS properly.

From a browser, go to your printer using the ip address. Click on Network configuration link. Default user/password is: admin/access. Find the "mDNS" link, click on it. Then configure with a name such as BrotherMFC and select enable. Once this is setup, then clicking on "+" in the print and fax system preference works.

Reply

Answer 2

Jan 17, 2008 10:03 AM in response to Eric Replogle

See followup comment.

Reply

Answer 3

Mar 11, 2008 10:51 AM in response to Eric Replogle

I am curious about this printer. Can you scan across the network on the Mac or do you have to connect it to the USB port? I have been looking for a network scanner and wondered if this one would work with the Mac. I have had conflicting searches for info on this - some say you can and others say you can't. I just figured if you had this printer set up on a network, you might be able to tell me if it works for scanning. I am using Leopard.

Thanks,
John

Reply

Answer 4

Mar 13, 2008 8:27 AM in response to John Conrader

I have been unable to get the 7820N scanning over the network after the Leopard upgrade. The software is just not there for it and while I downloaded an updated driver, those are not the tools I need.

Has anyone gotten this model to scan over the network in Leopard? Responses appreciated!

Reply

Answer 5

Mar 17, 2008 4:20 AM in response to misterorange

Scanning is working fine over network.
There is a 10.5 driver on Brother´s website.

But don´t expect too much... there is only a Preview and Scan button in TWAIN window and scanning is very slow with high dpi scans....

Reply

Answer 6

Mar 17, 2008 9:30 AM in response to Jens Habermann

You are correct! Installing the updated TWAIN driver brings the "ControlCenter" application back and it works just fine.

If you have slow scanning, I would suggest lowering the resolution to 300x300. That's what we use internally due to the delays in scanning on those machines.

Thanks for your response!

Reply

Answer 7

Mar 18, 2008 4:21 AM in response to Jens Habermann

Thanks for the info. I don't have very complex scanning requirements, so just preview and scan are probably good enough. I just want to have a scanner that is available over the network.

Thanks again,
John

Reply

Answer 8

Jasgrek

Level 1

0 points

Mar 31, 2008 12:06 AM in response to Eric Replogle

Thanks so much for describing this fix! Just fyi to other users, I could not connect to my printer via its IP address from Safari-- I had to use Firefox to get to the printer's configuration screen.

Reply

Answer 9

Mar 31, 2008 9:31 AM in response to Jasgrek

This page will also save you a lot of headache:

http://www.parkerwallace.com/BrotherControlCenterMacOSXLeopard

30 minutes of troubleshooting when this URL fixed it in the first go. Stupid Preferences...

Reply