Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Network printing: ipp "printer is busy"/LPD and AppSock prints garbled data

Dear all,
After months of trying on and off, I give up - I need help please. Since upgrading to Leopard, then Snow Leopard, I cannot print to the office computers. Windows or IPP printer settings produce the "printer is busy - wait 15 seconds" etc error message; LPD and AppSock printer settings enable data to get through, but the output is garbled text (the Adobe Postscript 3 engine on the printer isn't happy, obviously).

We have some new colour copier/printers from FujiXerox (FX Docucentre IV C3370) and some older Canon laser printers (LBP5600), but they don't offer Bonjour connectivity and I am stuck. I can ping them, I have the latest drivers, but nothing works. They worked fine in OS10.4 on this same computer, and XP and Windows 7 of course in BootCamp, but nothing in OS10.5 or 10.6.
I've been all over the web and through the Discussions forums and tried all the suggestions I can see, to no avail. I've tried KeyChains to carry by login ID and password to the machines, and deleting/adding printers through both the System Preferences and the CUPS interface, but I confess I am stuck. I currently copy all of my documents every day to a Dell desktop on my desk just to print them out.
The Canons are run through a Windows server, the FujiXerox has a standalone IP address and no separate print queue at the moment. Running OS10.6.2 on MacBook Pro. I'm happily connected to the network and can access all sharepoints and servers, I just can print to any of the printers - it's infuriating.

Is it a Firewall problem? Sub-net problems? Any ideas most welcome, thanks for looking and sorry if I've missed out anything important.

MBP, Mac OS X (10.6.2)

Posted on Feb 28, 2010 11:18 PM

Reply
12 replies

Feb 28, 2010 11:50 PM in response to MacJapan

You may find the Canon LBP5600 uses a proprietary printer language, such as CAPT (or LIPS if you are in Japan). These proprietary languages do not work that well (or at all) when shared from Windows. So this could be the issue with the Canon. Although if you were printing from Tiger I would say that the issue could be with an outdated driver that does not support Snow Leopard. Do you have a driver that reports support for the new OS? The readme included with the driver should indicate this.

If the Canon is a PostScript device, then this will help get around the driver issue. In theory you could use the Generic PostScript driver.

For Windows print queues, you will need to select Windows when adding the printer. This should show the advertised workgroups, and upon selecting the workgroup the Windows server is using, you should see the server's name in the list. When you select this you should be prompted for a Windows user account and password. If the Guest account is enabled on the Windows server, you should be able to select this to see the shared printer names. With the shared printer name selected, you can then select the printer model in the Print Using. This should work fine providing the printer driver can be used in this method.

For the Xerox, I suggest you try HP Jetdirect-Socket as the IP protocol instead of LPD or IPP. This is the same as Standard TCP/IP Printing on Windows, and since that is working on Win7 and XP, it should also work for the Mac. If you wanted to double-check the setup on Windows, select the printer and look at the Properties. Under the Ports tab you can select Configure Port. This will confirm what Windows is using to connect to the printer.

Hope this helps. Reply if you need more assistance.

Pahu

Mar 1, 2010 1:39 AM in response to PAHU

Pahu, great of you to answer to soon, thank you for taking so much time to reply.
I did install the latest LIPS drivers for the Canon a few months ago, but it still comes out garbled.
I've also previously tried adding the Windows printers using the method you suggest, but no joy. I don't think I tried the HP Jetdirect-Socket though, I'll give that a go. I thought it was for HP only.

This is the first time I've run into such a brick-wall of a problem; I've been using and administrating Macs in the office environment since MacOS7.5, and this is the first time I've been stumped. Under Leopard I did manage to print to an older Kyocera machine through Bonjour and a CUPS/Gutenprint driver, but we changed the printers on the weekend and the new one doesn't support Bonjour.

Many thanks again, I'll have another go in the morning at work. (Everything is fine at home of course, accessing my own network printers).

Best wishes.

Stephen

Mar 2, 2010 4:18 PM in response to MacJapan

Hi MacJapan and Pahu
excuse me for hijacking this thread but I ran exactly into the same problem today; I tried four hours to get a friends network printer to work, no luck. Maybe we can sort out a solution together.
The printer (Brother HL6050D) works fine with Leopard, using AppleTalk. We now have a new MiniMac with SnowLeopard on it, using the same network connection as before.
I downloaded the newest (SnowLeopard) drivers, installed and tried all available connections (Bonjour, LPD, IPP, and HP Jetdirect-Socket), following exactly all the instructions given by Brother and trying out all ideas and tricks I found in this forum. The printer has a fixed and unique IP-adress and is found in the network. Now when I try to print I immediately get the „printer is busy“-message.
I reseted the printer settings several times, added new ones with generic PS driver or original Brother driver, unplugged printer and network, restarted the mac (did all the voodoo Brother suggests in their instructions).
The best result (once after 20 attempts) was that the printer quitted after receiving 22% of the job. By the way, I also switched off the firewall, no difference.
As you say, MacJapan, for me it‘s also the first time since OS7.5, that I run into such problem, I hope we‘ll find a solution that works for all of us.
Regards Philo

Mar 2, 2010 11:40 PM in response to philo2

Thanks for the reply Philo. I think you will find the D stands for duplex while the N stands for networked...

Okay, with a direct IP connection and the device supporting Bonjour, I would expect there to be no issue with the print queue. I could understand your symptom with one of the other IP protocols selected, as they may not be enabled in the printer. But if you can see the printer advertised as a Bonjour printer than it shows the service is active and seen by the Mini.

At this stage I suggest you print a network configuration page from the Brother, this should confirm what ports/protocols are active and that the IP address, subnet mask and gateway address are set correctly.

To change any setting if needed, a number of printers now have built-in web pages. You may find that if you enter the IP address of the printer into a browser, you will access the printer's web page and most likely have the means to change the current network settings.

If everything appears to be correct I would try creating another printer queue on the Leopard Mac, this time using Bonjour or HP Jetdirect-Socket. The HP protocol is used by Windows as a default and requires no specific queue name, which can assist with problem solving. I would also stick with using the Generic PS driver for starters to rule out any driver related issue.

If printing from the Leopard Mac doesn't work using an IP protocol, then I would disconnect the Brother's Ethernet cable and Ping the IP address. If you still get a response with the printer disconnected then this would explain the symptom to date.

Hope this helps. Reply if needed.

Pahu

Mar 3, 2010 3:50 AM in response to PAHU

Hi Pahu,
It's good of you to take so much time to help us out. As you rightly noted, I can use IPP or JetDirect to communicate with the printer, although only garbled text comes out.
I decided to plug my laptop directly into the back of the FujiXerox by USB to see if the network was creating obstacles or not. The printer/copier showed up straight away in the default Printer preference pane when I went to add a new printer, and found the latest postscript driver. So far so good. Printing a test page just produced garbled text, which is when I dug around in the back of the machine and saw that the optional Adobe Postscript board hadn't been installed - and hence the postscript drivers for the machine were presumably useless.

After digging around I found the Windows drivers are ART EX drivers; obviously that doesn't really come in Macintosh flavour, but FujiXerox do have a non-postscript driver for the machine which I downloaded. This time I could connect via LPD, as FujiXerox recommend, but the print job stalls at the spooling stage; the error message reads that the 'Library/Printers/FujiXerox/Filter/FXPSACMMFilter.bundle/Contents/MacOS/FXPSACM MFilter' failed.
I tried reinstalling the driver, and repaired permissions, but no luck.

So close, but still not quite there. Silly me though for automatically assuming a new FujiXerox colour printer with postscript drivers on the support page would use, well, postscript drivers. Lesson learned though. I'll let you know if I ever work it out, and thanks so much again for your assistance. If you know anything about the error message or Art Ex drivers, that would be great!

Take care.

Mar 3, 2010 10:40 PM in response to MacJapan

MacJapan wrote:
After digging around I found the Windows drivers are ART EX drivers; obviously that doesn't really come in Macintosh flavour, but FujiXerox do have a non-postscript driver for the machine which I downloaded. This time I could connect via LPD, as FujiXerox recommend, but the print job stalls at the spooling stage; the error message reads that the 'Library/Printers/FujiXerox/Filter/FXPSACMMFilter.bundle/Contents/MacOS/FXPSACM MFilter' failed.

The filter bundle crashing could be related to permissions on the filter or a result of using a 32bit driver with a 64bit application.

For the permissions, you could opening Terminal and entering the following text;

sudo chown -R root:wheel /Library/Printers/FujiXerox/Filter/

then press ENTER. You will be prompted to enter you user name and password. The user name needs to be an account that has admin rights to the Mac.

Exit Terminal and restart the Mac. Now try printing again.


Regarding the 64bit apps, these are the included SL apps like Preview, TextEdit and Safari. If you attempted to print with one of these apps when you got the error, you could try forcing the app to open in 32bit mode. This is done with the application closed. Locate the app with Finder and do a Get Info on the package (icon). There will be the option to 'Open in 32bit mode'. Select this, close the Get Info window and open the app. Now try a print.

Regarding the Non-Postscript driver, looking at the FJ drivers web site, there are two of these drivers available. Both are showing as version 1.1, but the dates are different. Have a look at the following link to see if you have the one with the most recent date.

http://onlinesupport.fujixerox.com/setupDriverForm.do?ctrycode=AU&lang_code=en&dlang=en&pid=DCIVC3370


Greg's suggestion to use the Generic PCL is also a good alternative. One thing I did find however with the PCL5c is that it does not print in colour, even though it would suggest it does based on the name (the c normally indicates colour).

Did you get the Canon LBP printing?

Pahu

Mar 4, 2010 11:27 PM in response to PAHU

Pahu,
Thanks so much for the additional ideas. I made sure it was the latest driver, and printed from Word and TextEdit, the latter opened in 32-bit mode, after running the command in Terminal. I just dragged the relevant folder to the Terminal window to make sure the address was right.

Anyway, no luck, the same 'failed' error message comes up.

I tried the PCL5 drivers, but as you say, no color options. The print job was sent to the printer but it wasn't processed - I don't have access to the printer's log to see why it was cancelled.

The Canon isn't working, but after rooting around more on the website I noticed that it's marked as a model that won't work with Snow Leopard - end of story.

I emailed FujiXerox Australia tech support about the driver, since I also downloaded a copy from their website with the same results, but they're not interested in helping: I'll need to discuss the technical details in Japanese with FujiXerox here. I'll let you know what comes of it. Again, it's been immensely kind of you to help out.

Many thanks.

Mar 5, 2010 12:19 AM in response to MacJapan

MacJapan wrote:
I tried the PCL5 drivers, but as you say, no color options. The print job was sent to the printer but it wasn't processed - I don't have access to the printer's log to see why it was cancelled.

Some office copiers have a Job Accounting function, whereby you have to enter a valid username with password in order to copy and print. Maybe this is enabled in the machine and this is stopping the PCL print job?

Or, the printer also doesn't have PCL - some regions it is also an option - and this would stop it from printing.

The Canon isn't working, but after rooting around more on the website I noticed that it's marked as a model that won't work with Snow Leopard - end of story.

That's the problem with proprietary printer languages. You are at the mercy of the vendor if they decide to drop support. At least with a printer that supports PCL or PS, you have options if the vendor is late with or not producing an update.

I emailed FujiXerox Australia tech support about the driver, since I also downloaded a copy from their website with the same results, but they're not interested in helping: I'll need to discuss the technical details in Japanese with FujiXerox here. I'll let you know what comes of it. Again, it's been immensely kind of you to help out.

Sorry we couldn't get it working. It feels like we are close and it may prove to be something simple, but I sure have no idea at this stage what it could be.

Good luck.

Pahu

Network printing: ipp "printer is busy"/LPD and AppSock prints garbled data

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.