Old JetDirect Cards & New Java...

[DavidM]

Anyone else having problems with 600n and 610n network cards with the new Adobe (ver. 9.x)? We are having to replace them with newer (620n or petter) JetDirect Cards. We keep getting 81.xxx errors with the old cards. We've tried firmwear upgrades but that hasn't helped.

David Milsop

[cs_steve]

Have not heard anyone else mention this as an issue ... have you tried printing the same PDFs with a different PDF program like FoxIt?

[MichaelTech]

I've been seeing this a lot. I think the problem lies with the appliance thruput.
Newer hubs, and routers are faster, Apps are creating larger files, so the issue may be memory in the printer. What printers do you use?
How many users, and how many files are being sent?
Could be bottleneck issues.

[redcow]

MT hit the nail on the head. The 600n has a 10mbps xfer rate.
The 620n has a 100mbps xfer rate.

[DavidM]

We've got just about everything form LJ4 and 5Si's to LJ5550's. The problem is only related to the older Jetdirect cards and pdf files. Office, Lotus Notes, and other apps that we use don't have any problems.
One other thing: when we try to look at the printers over the internet with LCDispatcher, we get a Java error. If we replace the 600n cards with 620n card all the problems clear up and the printer starts working fine again.

David Milsop

[ptjeff1]

Have you tried a different pdf reader, like CSSteve suggested? I've heard of some of these weird problems going away with diff pdf readers.

[DavidM]

Unfortunately our company believes that the world will come to an end
if we test/use anything with non-approved/non-standard applications.

David

[ptjeff1]

I was emailed a note from someone a little while ago about 49.4 and 49.5 errors (thanks the the tip Alan!). Even though this isn't the same error you are experiencing his notes might have some relevance.

"49.4 errors are usually caused by bad postscript (excessively long headers
- HP printers only scan the first 1024 bytes of PS looking for the start code). Adobe Acrobat is a particularly bad offender for doing this.

49.5 are also bad code indicators, but I'm still not sure what the trigger is.

I've repeatedly complained to HP about these problems and they acknowledge there's an issue but they refuse to issue fixes. Our solution was to put a CUPS server in front of the printers and massage all jobs via that."

The part about Acrobat being a bad offender for long headers made me wonder if a different pdf reader might help in your case. Then again, header length might be completely irrelevant.

[DavidM]

Thanks for the info Jeff. I'm currently collecting data on the problem. And you're right about HP being uncooperative. They flatly stated that the problem was either something in our network hardware or bad PDF's, and refused to even look at the problem. They couldn't explain the problem with LCDispatcher though. You can be sure that if I turn up anything, I let everyone know.