Anyone have info on this.
I have run into this 3 times now in the field, the client PC suddenly stops printing, when you select the printer properties, the client pc asks for the driver to be installed.
The printer shows in the print/fax folder, but it acts like it lost the driver pushed down from the server.
I have seen this on server 2003 and 2008, 32 and 64 bit.
If you select load driver it acts like it can't find it , unless you locally provide a driver for the client.
Additional driver support was enabled under advanced tab on server.

I've seen this with the 'push me pull you' driver corruption in active directory environments.

I posted some scripts somewhere on this forum a couple of years ago that are pretty helpful in cleaning these kinds of issues up.

Basically you want to clean up the drivers on the server (if you restart the print spooler service first the driver files should delete when you remove the drivers without needing to reboot. Windows WON'T tell you if it was unable to delete a file). Setup the logon scripts for the domain to delete the printer and automatically add them back in.

What is clients operatring system? windows xp?

It was server 2003 in this case. I have seen this in 2008 also.
The workaround is to use the add printer wizard on the server, and point it to the OEM install file.
Have seen this 5 times now, somehow the server loses the update connection to the client PC's, they will see the driver, but no options.
I can't be sure if it's only servers that push scripts when the client PC's start up, but it's a good possibility.

Something to look into is if there a windows 7 PC on the network printing to the same printer.We have run across an issue where the printer becomes disabled for all users after the windows 7 PC prints or even just does "Auto Config".Driver corruption.

Ughh, ran into it again today on SBS 2008. Tried KX and PCL driver no luck. KM said obviously it's a network issue GOOD LUCK WITH THAT, and gave ZERO support. THANKS Guys!!!
This is a driver issue, end of. They have numerous HP's on the network with NO problems, and here we have a brand new 5550 Ci that can't let the clients print.

P.S. I have amended this post removing a semi offensive word as KM is watching . After spending time at KM training I realize that they are in the same boat, but.... frustrations are running really high with this driver issue, and we would have lost accounts if I had not loaded the drivers locally, on 25 PC's, not the way to spend a 1/2 day

This message has been edited. Last edited by: drewsup,

Well, Well, the plot thickens.
Went back in this morning, ready to do battle, and it's working with the PCL 5 driver that would not even let the 32 bit clients add it yesterday.
IT had restarted the server overnight, so the only thing I can guess is there was a patch waiting to be applied on restart.

P.S. there was one 32 bit Win 7 machine on the network, even though IT swore there weren't any !

Thanks for your posts I solve allot of problem's from reading them. This problem you probably know already. Today I had a 32 bit 2003 server dropping print connections and throwing error codes on computer side with ten new Windows 7 64 bit stations and like was mentioned XP would then fail. What helped is loading on the server the 32 bit first, the 64 bit next then going to sharing - additional drivers and putting a check mark next to the 64 bit driver -then pulling the driver from server. No more errors 7 PC side, no more print jobs that looked like they went and did not, no more XP's failing after 7 printed. And what Drew said point to OEM through add printer.

This message has been edited. Last edited by: Skyshot1,

The plot thickens again..
Just did an install with a VERY knowledgeable SYS admin who was fresh out of Server 2008 school.
Apparently, MS "forgot" to bundle Named Printer Deployment in 2008.... This will affect most manufacturers,(except HP of course ) We are all in the same boat on this, I am researching this weekend, will post later. What I found in 2003 is this..
From the MS website....

Consider the following scenario:

Windows Server 2003 Service Pack 2 (SP2) or hotfix 923218 is installed on a Windows Server 2003-based print server.
Simple Network Management Protocol (SNMP) is enabled on a printer port.
Printer devices that use the SNMP-enabled port do not respond to SNMP commands.

In this scenario, the related print queue status is displayed as "Offline" even though the printer devices are ready and are working correctly. Therefore, clients cannot use this print queue.

Note This problem does not occur on a print server that is running the original version of Windows Server 2003.
Back to the top
Resolution
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 SP2 installed.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.