1 Reply Latest reply: Mar 4, 2010 8:45 AM by G Robert Lewis
balistikboy Level 1 Level 1 (0 points)
I have a HP Laserjet 3600n connected via ethernet cable to our Airport Extreme base station using the built-in JetDirect functionality of the printer. Prior to installing Snow Leopard we had no problems and every computer on the home network could see and print with full functionality on the printer.

After installing Snow Leopard, it took a while but I got the printer working again with the same setup. Then we had a power outage and the printer was no longer visible on the network or in the airport settings. Again it took a while but I once again got it to work. But now it seems like it keeps falling off the network and the printer itself either shows an IP address of or another random one. The IP address should be generated by DHCP by the airport.

I don't know if this is a problem with Snow Leopard, the airport extreme, or the printer. The way I got it to work the last couple times no longer fixes the problem. Someone please help.

Message was edited by: balistikboy

24" Intel iMac, Mac OS X (10.6.2), HP Color Laserjet 3600
  • G Robert Lewis Level 2 Level 2 (225 points)
    I don't know if this is related, but...
    My MacBook Pro (Airport) has always been dicey connecting to an HP LaserJet 4000 on my wired LAN. Before Snow Leopard, I used AppleTalk rather than IP printing because it just worked.
    But Snow Leopard doesn't support AppleTalk any more, so I reinstalled the printer to connect via JetDirect (which supposedly provides more features). When it works, it works fine. But very often I get a message that it can't connect to the printer. The only thing I've found that fixes the problem is power-cycling the printer, which somehow enables queued jobs to print. Needless to say, this gets old.
    Is there some trick I'm missing?