I Think The Latest Airport Update Broke My Printer
Well, I'm sure the printer is still actually fine. But ever since I installed the latest Airport Extreme 802.11n firmware update, we haven't been able to print from either my iMac which is hard-wired to the router, or from my fiancée's MacBook, which normally prints wirelessly.
When we've tried to print, nothing would happen. When I finally looked into it, I saw that the Airport Utility said there was no printer connected to it, so I went into the Printer Setup Utility. Our printer, a Canon Pixma MP 460, was listed, but also greyed out. I went to the Add Printer dialog and the Canon showed up as being on Bonjour. I clicked on it, and hit "Add" and after some delay I was greeted with a -9672 error, with no other information provided.
After a little research online (it seems I'm not the only one with this problem since the update, and it affects other printer brands/models as well), I deleted the printers drivers, downloaded the latest from Canon's site, and installed both the printer and scanner drivers. But the outcome is exactly the same.
Has anyone found a way around this issue? I'm concerned that the only possible fix is for Apple to issue a patch to the Airport update, because it seems pretty obvious this is the cause of the error.
When we've tried to print, nothing would happen. When I finally looked into it, I saw that the Airport Utility said there was no printer connected to it, so I went into the Printer Setup Utility. Our printer, a Canon Pixma MP 460, was listed, but also greyed out. I went to the Add Printer dialog and the Canon showed up as being on Bonjour. I clicked on it, and hit "Add" and after some delay I was greeted with a -9672 error, with no other information provided.
After a little research online (it seems I'm not the only one with this problem since the update, and it affects other printer brands/models as well), I deleted the printers drivers, downloaded the latest from Canon's site, and installed both the printer and scanner drivers. But the outcome is exactly the same.
Has anyone found a way around this issue? I'm concerned that the only possible fix is for Apple to issue a patch to the Airport update, because it seems pretty obvious this is the cause of the error.
Comments
My main reason for picking the Airport Extreme was because of how easy I could set up a printer on our network, but now the only way I can do that is to use a method I could have employed with a much cheaper router. I've posted this on the Apple Discussion forums and sent an e-mail via the feedback page, so I hope someone is looking into this.