HP Laserjet 1010 & Wireless printing via Airport USB - Not working in SL

I'm experiencing the same with that configuration.

I've noticed another peculiarity not reported elsewhere. If I look at the Airport Express under Airport Utility, the front page shows there's a printer; Bonjour also shows there's a printer. But if I go to the Printer tab for the AE, it tells me there is no printer attached.

I had similar problems, my printer HP LaserJet 1010 is connected using USB to my Airport Extreme and I couldn't print after upgrading to SL.

My solution was to reboot the airport and upgrade the firmware to 7.4.2, after that the printer worked again.

Lucky you ... I wish I could say the same about my HP LaserJet 1010 hooked up to an AirPort Extreme. I updated my system to 10.6.1 this morning and then added my printer from scratch. Printing did not work though 😟

I do have to admit though that I did not power-cycle the AirPort due to a lack of time. Maybe that's the necessary step to revive wireless printing?! I'll definitely try that as soon as I am back home again tonight after work ...

Nope, still not printing even after power-cycling everything. All I get are error messages such as:

"/usr/libexec/cups/backend/dnssd failed"
Unable to open device (read failure)!

😟

Guess it's back to directly hooking up my printer to one computer via USB and then sharing that printer over the network for the others.

Did you make sure your Airport Extreme firmware is updated to 7.4.2? I spotted several threads here talking about that.

I had a similar-sounding problem with my HP1012.

The fix:
a. power-cycled the Airport Extreme.
b. Updated firmware.
c. Select Print in an application.

For an extended discussion of what I did see here - some of this may help:
http://discussions.apple.com/thread.jspa?threadID=2142906&tstart=60

Actually, at this point I have two printers connected: Airport Extreme ->USB powered hub ->2 printers. One is the HP1012, the other is an HP 4300 series inkjet. Took sometime to get it right, the first hub I tried apparently was not powered enough. In that vein, one earlier thread (a response to one of my posts) pointed out the possibility that the AE -> printer USB connection might not be adequately powered, and to try using an intermediate hub. Assuming your AE is performing properly in all other respects, don't rule out a cable or other printer connection issue even if the setup was working properly before.

stan

Well, I did try to update my AirPort Extreme's firmware (which is at 5.7 now; probably because I got an APE with 802.11g???).

If I choose "Check for Updates ..." in AirPort Utility, I only get the following message: "No updates to AirPort Utility or any of your Apple wireless devices are available at this time."

Also, I didn't find any site where I could directly (as in manually) download the latest firmware update. Maybe that wouldn't be of much use anyway as AirPort Utility ought to be able to detect any suiting updates for my hardware, right?

I also have the older "UFO" AEBS with version 5.7 and cannot print to my LaserJet 1012, even after the 10.6.1 update and the new printer drivers. This is extremely aggravating, especially if the latest firmware for the newer AEBS units does work after the update. I refuse to buy a new printer or router simply because I cannot print.

This is absolutely an issue that Apple should resolve. I'm certain that if there are 2 people in this forum with the same issue, there must be a large number of others out there with the same problem.

I had success changing from 802.11 b/g to b on my wireless router and some have had success changing to g.

After doing some further digging, I did find something that worked, only after cycling the power of my AEBS. Details in this post:

http://discussions.apple.com/thread.jspa?messageID=10135182&#10135182

I certainly would call this a "work around" but at least it's working.

Awesome ... that "work around" (and it sure is one, having to use open source printing drivers instead of the original HP ones) did the trick for me as well. Thanks for pointing it out, Jim!