The only way to get the printers working again was to uninstall the 5 updates and Rollup for SP4 issued Tuesday by Microsoft.

KB896423 dealt with a sec vuln with the print spooler mechanism, but just removing that update was not enough. I had to remove the other 4 and the rollup.

Anyone know if Dell has confirmed this as a problem? Has anyone else seen this?

I can confirm this as well. After an hour on the phone with dell tech support, they still would not admit this as a dell driver problem..None of our hp's or Savin's or Sharps are having this problem...We have about 8 of these deployed enterprise wide in branch offices. Funny thing is, 2000 clients seem to be the only ones affected, xp works just fine. All this after the fact that you cant set these printers static..Dell needs to get on the ball..

You certainly can set the 1700n and the s2500 to a static IP address using the embedded web server or the Set IP Utility.

The problem just came back - so my prior solution did not work out in the long-term... I do know however it is a kind of 'resource' problem to do specifically with that printer.

:mansad:

I is definitely some kind of conflict between MS Kb896423 and The Dell printer drivers. we have many Dell printer set up on a print server and any 2KSP4 Pc with Kb896423 cannot print, all getting this same error. however if I delete the printer from printers under the users profile. then as an admin remove the patch Kb896423 then reboot. and then log back in as the user and re add the printer the printer works fine.... but now the Pc is not patch.. I do not know as of yet how to resolve this. I would think that Dell needs to update their drivers. problem is when we download drivers for these network printers. they seem to be marked to support specific desktop systems Optiplex ect.. these are network printers and should not be desktop specific just OS specific. this is causing and issue reinstalling and updating the drivers on the print server. If anyone has come up with a solution to Keep the Pc's updated with this Kb896423 and be able to print to dell printers please post it. Thank you in advance for your help.

Tom

I have this problem on W5300N drivers on my network.

Removing KB896423 doesn't fix the problem for me, unless it needs to be removed on the file and print server as well ?

I have temporarily got round the problem (until there is a proper fix), by selecting the HP Laserjet 4 driver under the DELLW5300 printer properties Advanced Tab.  This is not ideal but means you haven't got to re-install any shared printers on your users workstations.  Not had any problems so far as the driver is PCL.  Not sure I want to risk changing to the Postscript driver in case there are any font / formatting issues when using applications.

Message Edited by sbaldry on 08-25-2005 06:06 AM

This happens on a Dell 2500S as well.  Removing 896423 and the SP4 Rollup works if you remove all printers first and then add them back once the offending patches are removed.  Time for both Dell and MS to issue whatever fixes are needed.

I have found that if you Delete the printer first then remove the update then reboot then re add the printer. this will resolve the issue. but of course this is only temporary because the PC is now vulnerable.

One of the post on this forum did help.. I was able to replace the drivers on the sever for our 5300n to the post script drivers and the re apply the update to the PC's connect them to the printer and they could print with no issues.. however this trick did not work for our two 5100cn printers..

If anyone has any more ideas please post them. I thank you all in advance for working in this issue.

Tomas

Sorry about the last post.. I didn't notice the second page.. nothing I wrote was new info.. sorry..


Thank you all for the hard work..

Apparently not.  MS fixed a security issue in the printer subsystem and from what I've been able to find out only Lexmark (and by proxy Dell) wrote their drivers in such a poor way as to be using the defective part of the code.  From what I'm told no HP, Canon, Brother, Xerox, Richo, or other branded printers are experiencing this problem.  Only Lexmark (and thus Dell) drivers are affected.  If everyone else's drivers work without revision (we have HP LJ drivers on our LAN 3+ years old on old HP LJ printers) then it's Lexmark's poor programming that led to this problem. 

MS has been great in being the conduit to getting it fixed, but it's Lexmark's bad drivers that need updated.

BTW, don't count on Dell drivers for weeks given their clueless insistence on getting them WHQL certified.  I would call Dell and tell them you demand they fix it now.