Installing the PCL6 driver seems to have fixed the problem, but I will let the users test it out for a while. The guy that installed the printer said that we must use RPCS driver instead of the PCL6, but who care what the guy who *should* know what must be done says. Here is where the old IT side of me kicked in - Don't trust what people tell you. After a bit more testing, I could recreate the problem by printing to the network machine first followed by the HP machine. This got me to the same issue that I had before, but it turned on a lightbulb. This time though, I tested the hp printer after the network (mp2000) printer - does not print. Installed the new network printer - printed fine. I deleted ll drivers, installed the problem printer - works fine. The problem would come back later though. Great problem solved for half a day or more. Heres what I saw:Įverytime I played around with the printers (Delete drivers, reinstall, etc) I would have problems with the hp printer and, if lucky, I would get the printer to work and would be able to print to the problem (HP) printer.
This was one easy to overlook because of previous testing and how the users use the printers. The most annoying thing is that it seems to only affect HP machines.Īfter some some more troubleshooting I found what looks to be a pattern of events.
At the same time our company was audited but I don't think the auditors put anything into our network (USB, CD's, etc). These symptoms happened soon after a new range of printers were intalled (afico mp2000 and afico mp171). After many tries at doing he same thing, the printer will work and stop working after a ramdom amount of time (anything from 3 hours to 2 weeks if it does stop). I have restarted the spooler, restarted the machine, uninstalled and deleted the drivers and used a combonation of these at times. On testing with the microsoft test page, the printer merrily chugs along and the page comes out, but no other document can print. On the host side though the document never gets registered through the printer driver. If you click print on the client pc, the document seems to go through to the network printer as normal and the pc thinks it has been printed. As of a month ago, my printers are no longer printing on command. I have a number of printers on my network, most of which are shared through the network.
I have a curious issue that does not want to be resolved.
0 kommentar(er)
