03-30-2009 12:01 PM
I have checked the settings and we are using static ip addresses and the printer is set to 100tx full. the switchport is set to 100tx full.
We do use an application campus-wide that uses Crystal Reports to print secure transcripts and such. I do not think that this is at the heart of the matter other than just coincidence. The printer seems to crash as easily on machines print jobs that are not formatted with Crystal Reports.
We are also still using the original firmware ,and as far as I can see from these posts changing it doesn't seem to help. I am planning to change the settings for Linkspeed to match the gentleman above's post to see if 10/half on the switch port and and auto negotiate on the printer will make a difference.
We have tried the 4250PCL5e/4250PCL6/4015xPCL5e/4015PCL6/4015PSdrive
At this point My Network Admin is seriously considering taking Dell up on their offer to replace all our HP equipment. We are also having problems with their 2015d printers and their new 2055dn's USB of course but thats for another Thread.
03-30-2009 02:42 PM
We usually set our P4015 units:
IP Configure: DHCP (not default BOOTP)
Bonjour disabled (one of the FIRST steps)
Multicast IPv4 disabled (sometimes)
Link settings: AUTO
We also set a password for the Admin account (Networking, Security, Authorization) and let it set that for the Set Community Name.
In the Mgmt. Protocols we also turn off the "Encrypt All Web Communication" (may not be the safest setting, but we do it.
Everything else (except the IP name) is left at their default except for some that have some subnets set in the Access Control.
The machines are working very well for us and are running firmware 04.047.2 (except one that is on 04.044.0)
03-30-2009 05:12 PM
I will update in another week, unless I have a problem before then.
03-31-2009 04:24 AM
If you are not having problems with yours I am glad for you. These are troublesome printers to deal with so consider yourself lucky. I wish we were as lucky.
We set ours up very similar to you with 2 exceptions. We assign Static IP addresses and we control port speed at either 10/half or 100/half other than that we are almost identical. Ours will not print a single day without having to be restarted.
03-31-2009 04:49 AM
03-31-2009 06:12 AM
03-31-2009 08:13 AM
He basically helped me upgrade my firmware to the latest. That worked for a few days, then I got a message today that the error reoccured.
Norm is to call me back Thursday to ask me if the error came back and from there we will continue on.
He has seen this thread FYI. He was reading some parts of it to me as we spoke asking if I tried this or that.
04-01-2009 12:31 AM
Hello, we try the driver HP PCL5, PCL6 ! the very bad is the pcl6 ! the pc become very slow ! and the problem is always the same !
Yesterday, i install the universal driver pcl5 ! not the pcl6 ! .. and at this times... no more error ! no stop !
may be is also the solution for you !
04-01-2009 12:38 AM
I entry the ip adress to check..
after i search the network printer..
I add the printer and it's finish....
04-01-2009 04:47 AM
04-03-2009 01:39 AM
i understand that there is no real solution with new firmware so i decide to DL LJ4x15_04.042.0 but i don t understand how to downgrade it with rfu file
can you explain me a little thx in advance
sorry for my english :)
04-03-2009 03:57 AM
Unzip the file and you should have a xxxxx.rfu file. open a ftp connection to your printer (ftp://
04-03-2009 04:22 AM
04-06-2009 04:22 AM
I hate to store 5 new printers that could be replaced with something else that doesn't have this issue staring it in the face. The three that I have out on the network now don't work so why put out 5 more to have to answer help-desk calls on?
Has anyone heard anything positive from HP on this lately? I am trying to get a case number for the ones I have. I guess you cant get any response from HP until you do?
04-06-2009 03:51 PM
04-07-2009 06:18 AM
04-07-2009 06:49 AM
So ... Let me make sure I understand this. Bypassing the embedded JetDirect by using an EIO JetDirect allowed you to run problem free, so HP said to replace the DC Controller and then see how it goes??
Oy, I suspect (and I'll bet you agree) that replacing the DC Controller is only an effort to "cover all bases" and most likely will NOT correct the problem. Especially since embedded JetDirect or EIO JetDirect will still communicate through the Formatter and the DC Controller would be used exactly the same either way. As you know, using the EIO JetDirect only bypassed the embedded JetDirect section of the Formatter, nothing else. That (by itself) demonstrated either the embedded JetDirect to be at fault or the connectivity between the embedded JetDirect and the rest of the Formatter. Either way, the problem is still in the Formatter. Historically, 49.xxxx errors indicate an error (either by hardware or by codes that "confused" the hardware) in the JetDirect (embedded or otherwise).
I think replacing the DC Controller is wasting everyone's time, but it's probably on somebody's checklist of things to do before authorizing further steps.
04-07-2009 07:45 AM
After talking to USA support (thanks to having the care pack) and doing some trouble shooting (He called me back a week later to see if his fixed work, which it didnt) he sent out an HP repair guy, who replaced the entire board in the 4015 (He called it all the logic).
No problems so far.
My advice; if you spend over $200 for an HP printer, get the care pack. it is worth it just to skip the Indian support.
04-07-2009 08:45 AM
I agree with you and shared a similar response to why a DC controller would fix an embeddded jetdirect card issue. But they pay for the parts, so I will go and try it. I expect to call back to escalate the problem. We have already done the firmware, formatter, driver and it didn't work. At least they didn't say replace the feed tires :)
04-09-2009 03:19 PM
04-09-2009 03:44 PM
The second call I made, they sent me a replacement P4014N -- that too didn't fix the issue. ANd it was not easy to get the replacement unit...
I have called HP at lease four times regarding the 49.4C27 error. It's very painful to get thru the first tier support folks.. because of this pain -- I have ended up using this web site as the point of reference and ideas to solve this problem.
I thank each one of you for your efforts, your ideas and your help. You contrubtions have helped me and I'm sure others...
Here's the status of my printer. Since I have done the following...
1. Static IP address.
2. turn off all protocols not in use.
3. Set interface to 10 half on switch side and auto on the printer IO
4. Added 256Mb of additional memory.
5. Down graded firmware to the older recommended version 04.042.0.
6. Verified all folks using this printer have proper drivers for their printing needs.
Since I have added the new memory and went to a older version of F/W we have not had a single error in 14 days.
Note; the SNMP monitoring system show we are using 117Mb average memory usage for the older firmware on this printer. Now with the new memory we are seeing a 33% utilization has our average. The memory was $23. from CDW.
I hope this helps one of you -- Duane
04-10-2009 05:22 AM
I'm going to roll this out to more locations and I'll let you all know the results. Rolling back the firmware isn't the best solution in the world, but at least it seems to work. (let me find a piece of wood to knock on)