I'll add my name to the list, I'm having the same problem. I had already tried turning off power management, no help. It's really quite aggravating. With network scanning now available the machine was shaping up quite nicely.
I started seeing a new error this week with this problem. The display read "line error". Also, "resetting" the network scan utility no longer cleared the problem. To get the printer working, I had to reboot the router/switch.
The line error problem lingered in my head. I replaced the CAT5e cable to the printer and repunched the CAT5e wall jack terminals. The error has not surfaced in over 4 days.
Also, I did follow someone's suggestion to switch the printer to 100 / Half speed. I've tried this speed in the past with no luck in getting rid of the problem, so I believe putting a high quality shielded patch cable on the printer solved the problem. Nevertheless, I mention the 100/Half change for sake of completeness in case others need to both changes to get rid of the error.
I'm guessing the old cable worked well enough before to get a noisy connection to the printer but not good enough to have everything working at 100%.
I've switched mine to 10Mbps / half but still have problems.
I find it difficult to believe that it's power-saving or network speed related as simply restarting the Print spooler service on our server makes the jobs come through. Restarting the printer (power lead in and out) does not seem to bring it back to life.
This makes me think that it's more likely a driver issue/software.
I really think it's about time we heard something from Dell on this. If I don't have this resolved by Thursday it's going back and I'll get an HP. This is the first Dell printer we've bought and have generally been impressed with the features / cost of it. However, the cost is negated if I get hassled every couple of hours to restart it!
I'll throw my hat into the ring also. If I recall correctly, I was having this problem even before the v1.22 firmware update. I remember scanning the community forums then and not seeing anyone else with an occurence. It was driving my wife crazy so I set her up with a USB connection, and I just have the nuisance of refreshing the network scan tool often.
I would not be surprised if the the problem is also related to my piece of junk router, a D-Link DI-624. You others wouldn't mind posting what routing equipment (if any) you're using, would you?
Well, honestly I'm not surprised. I regret the day I bought that DLink and I've just been too cheap to replace it. Actually, cheap's not everything. There are other issues, but beyond the scope of this topic.
Add this quirk to DLink problems. And I think this has put me over the edge into getting a new router.
I'm running this on a medium sized corporate network, and as such there are only Dell Switches (3324 & 5224) inbetween the workstations and the printer.
JMansford
21 Posts
0
July 4th, 2005 13:00
Gary Reinsch
12 Posts
0
July 6th, 2005 23:00
JMansford
21 Posts
0
July 7th, 2005 14:00
I've disabled the power saving this morning but it's not made any difference.
Any other ideas? Dell - anyone there?
Gary Reinsch
12 Posts
0
July 7th, 2005 15:00
You might also want to try adjusting the Network settings on the printer.
If you configure the ethernet setting to 10M Half Duplex, rather than auto, it might help.
If you haven't already done so, you can also reset the NIC, as well.
kirk444
15 Posts
0
July 8th, 2005 20:00
I'll add my name to the list, I'm having the same problem. I had already tried turning off power management, no help. It's really quite aggravating. With network scanning now available the machine was shaping up quite nicely.
If anyone finds a solution, do post!
martymc
4 Posts
0
July 11th, 2005 03:00
I started seeing a new error this week with this problem. The display read "line error". Also, "resetting" the network scan utility no longer cleared the problem. To get the printer working, I had to reboot the router/switch.
The line error problem lingered in my head. I replaced the CAT5e cable to the printer and repunched the CAT5e wall jack terminals. The error has not surfaced in over 4 days.
Also, I did follow someone's suggestion to switch the printer to 100 / Half speed. I've tried this speed in the past with no luck in getting rid of the problem, so I believe putting a high quality shielded patch cable on the printer solved the problem. Nevertheless, I mention the 100/Half change for sake of completeness in case others need to both changes to get rid of the error.
I'm guessing the old cable worked well enough before to get a noisy connection to the printer but not good enough to have everything working at 100%.
I hope this helps others with the same problem.
Take care,
Marty
kirk444
15 Posts
0
July 11th, 2005 05:00
On Monday I'm going to try some different cable/switch configurations and see if I can't duplicate your results.
I'll post here once I have something to report.
JMansford
21 Posts
0
July 11th, 2005 07:00
I've switched mine to 10Mbps / half but still have problems.
I find it difficult to believe that it's power-saving or network speed related as simply restarting the Print spooler service on our server makes the jobs come through. Restarting the printer (power lead in and out) does not seem to bring it back to life.
This makes me think that it's more likely a driver issue/software.
I really think it's about time we heard something from Dell on this. If I don't have this resolved by Thursday it's going back and I'll get an HP. This is the first Dell printer we've bought and have generally been impressed with the features / cost of it. However, the cost is negated if I get hassled every couple of hours to restart it!
martymc
4 Posts
0
July 15th, 2005 23:00
ean smythe
2 Posts
0
July 15th, 2005 23:00
I'll throw my hat into the ring also. If I recall correctly, I was having this problem even before the v1.22 firmware update. I remember scanning the community forums then and not seeing anyone else with an occurence. It was driving my wife crazy so I set her up with a USB connection, and I just have the nuisance of refreshing the network scan tool often.
I would not be surprised if the the problem is also related to my piece of junk router, a D-Link DI-624. You others wouldn't mind posting what routing equipment (if any) you're using, would you?
-e
kirk444
15 Posts
0
July 16th, 2005 08:00
Coincedence? I am not sure, but it makes one wonder....
ean smythe
2 Posts
0
July 16th, 2005 14:00
Well, honestly I'm not surprised. I regret the day I bought that DLink and I've just been too cheap to replace it. Actually, cheap's not everything. There are other issues, but beyond the scope of this topic.
Add this quirk to DLink problems. And I think this has put me over the edge into getting a new router.
-e
JMansford
21 Posts
0
July 18th, 2005 07:00
martymc
4 Posts
0
July 18th, 2005 19:00
-mm