If you change the driver server side, the new driver will magically appear on the clients after a while or reboot normally.
Got a weird one today.
A printer has decided it will only print text upto a certain font size, above that and it just ignores the text and prints out a blank page.
It would seem its to do with the printer driver as when i reinstalled the driver on the print server and connected with my own PC all was well. I have tried to delete the drivers from the local PC but they are locked as they are in use. Renaming the folder they are in works but does not solve the problem.
Can anyone suggest anything as i have half a dozen PCs which cant print and i dont fancy rebuilding them for something as daft as this.
If you change the driver server side, the new driver will magically appear on the clients after a while or reboot normally.
Reboot and look in the event viewer under System for "Print" entries talking about driver installations.
There is a manual way of cleaning the drivers out if you want to look at that afterwards?
Try this:
After logging on locally at the workstation as administrator stop and restart the Spool Service then clear any print jobs still in the queue. Stop and start spool service again.
Go to Printers and Faxes, right click in the white space [without selecting any printers, or faxes]
Select Server Properties. Then select the Drivers tab. Delete any drivers no longer required. Once the drivers have been deleted then delete the printer[s]
Hope it works.
I should have said: I have used this to delete a printer from a workstation where the shared server queue no longer existed: I could not find any other way of removing the printer/drivers.
Last edited by DaveP; 06-01-2009 at 03:36 PM. Reason: Add content/clarify post.
Try the clean spooler on the admin bar [ see below ] - it's a GUI tool that restores the print spooler to its original state. It deletes all print jobs, printers, printer drivers, and spool files on a specified local or remote server / PC.
Yup had the duff batch of 2430 drivers a while back, caused no end of trouble - finally sorted now tho
As for the TCPIP Monitor Driver I would guess reinstalling the TCPIP stack from network connections should get it back...
There are currently 1 users browsing this thread. (0 members and 1 guests)