Many of my users are having a problem where they loose the ability to print to our Dell W5300N. It happens from several different computers (win2k, and XP) from several different applications. The printer is connected over tcp/ip. Clients print to a win2k3 print server that send them off to the printer. When this problem occurs the printer is listed, but you cannot go to the prefferences because it does not think a driver is installed. A reboot temporarily solves the driver problem. When they cannot print to the W5300n they can still print to other printers. I have tried to by pass the print server and have the clients print directly to the W5300n and that does not solve the problem. Any suggestions?
I am experiencing similar problems with the W5300 on the network, either from WinXP Pro or using a Win2003 print server. It is intermittent and very difficult to reproduce the problem to determine the cause.
I have noticed two specific issues that may be related:
When printing many print jobs (hundreds of single page jobs), if the printer runs out of paper, the computer becomes seriously bogged down. Printing continues when paper is added, although the printer occasionally skips a print job.
When printing from an IE browser using Ctrl-P or right click Print, the computer pauses then displays Print dialog box with the Print button greyed out. I have noticed this quite often using the “Printer Friendly� option available on some websites.
The only resolution is to reboot and reload the page to print it. Reinstalling the driver does nothing.
I am not certain where to point the finger yet, but I am certain that the sequential print jobs are going somewhere into never-never-land because it happens a few times a week.
Let’s hope we can find a resolution to this problem.
Good question. Now how would I go about doing that?
The printer is connected directly to the network, so I looked up the settings in configure network port and noticed the End of Job timeout was set to 90 seconds. I wonder if this might be why we are loosing jobs because we don't change the paper fast enough.
Print Server Settings (via web interface)
Ethernet 10/100
Standard Network Card
Status: Connected
Speed, Duplex: 100 Mbps, Half Duplex
Current Date & Time: 2004-10-06 07:29
End-of-Job Timeout: 90
UAA (MSB, Canonical): 002000EC3164, 000400378C26
LAA: 000000000000, 000000000000
Firmware, Bootcode Revision: 55.10.19, NA
Compi: bld-lib, 551.019, 07-Apr-04 12:58
Integrated Network Option Settings
Printer Type: Dell Laser Printer W5300
TCP/IP
Active: Yes
Enable DHCP: No
Enable BOOTP: No
Enable RARP: No
Address Source: Manual
IP Address: 192.168.0.152
Netmask: 255.255.255.0
Gateway: 192.168.0.6
Hostname: W5300
WINS Status: Registered
WINS Server: 192.168.0.3
I appreciate any suggestions that you might have.
Thanks!
Message Edited by djbaldwin on 10-06-2004 07:36 AM
I have disabled Bidi support and it stilled happened. I also used the Lexmark driver and disabled the bidi support. I have finally taken the win2003 server out of the picture and now users print directly to the w5300. This seems to have remedied the problem. I wish dell would release new drivers that say it supports win2003.
I know I can use the lexmark drivers but they did not solve my problem. One thing that is confusing to me is that on the server you can enable and disable the BiDi support but on the desktop computers the option is greyed out.
When you upgrade the driver on the server, are you sure that all your workstations are getting upgraded as well?
I'd advise deinstalling all instances of drivers, cleaning up the registry, installing Lexmark driver for 2003 Server and using "point and print" to distribute it on the workstations.
The BiDi option may be grayed if you did not install the BiDi support (The lexmark site has 2 downloads, one for the driver and a second to install BiDi support).
yes, I have several HP printers on my network, HP 4050, two HP4200, HP 5N, HP 2200, HP 2300. All in all I will never ever buy a Dell printer again in my life. HP have their act together, Dell needs to pull their head out.
d3sp
470 Posts
574
0
Posted July 19th, 2004 11:00
When you install the drivers locally, does it still happen?