Re: printer problems since patch Tuesday

Printer problems here too after WSUS patch. Only our Windows 2000 Pro
machines are seeing it and it is with Dell 5100 and 5300 printers.


Fred


"Tom Che [MSFT]" <v-tomche@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:YXMo4rlnFHA.3672@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Mike,
>
> Thanks for your posting.
>
> From your post, my understanding of this issue is: You have been
> experiencing numerous printer problems ever since the latest patches were
> released and installed for Windows 2000 Professional. If this is not
> correct, please feel free to let me know.
>
> Based on your detailed description, I guess the current driver for
> IBM/Lexmark printers may be not compatible with latest patches for Windows
> 2000 Pro.
>
> To confirm this root cause, a test machine is a wonderful idea. I think
> the first thing is that we should find out which patches are the root
> cause. Could you please let me know which patches were installed as you
> mentioned before this issue?
>
> Then, we may try to uninstall the probable patches and then test this
> issue. If the issue disappears just after uninstalling patches, we may
> know that the patches are the root cause indeed. I can perform more
> research according the detailed patches.
>
> On the other hand, if certain patches are the root cause, it might be
> better if you also contact the printer vendor. They may confirm this
issue
> further, and provide a newer and compatible driver for the latest patches.
>
> Hope this helps!
>
> Have a nice day!
>
> Sincerely,
> Tom Che
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> --------------------
> From: "Mike Koch" <mikey@xxxxxxxxxxxxxxxxx>
> Subject: printer problems since patch Tuesday
> Date: Wed, 10 Aug 2005 16:54:46 -0400
> Lines: 31
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
> X-RFC2646: Format=Flowed; Original
> Message-ID: <#$bs#2enFHA.2916@xxxxxxxxxxxxxxxxxxxx>
> Newsgroups: microsoft.public.win2000.printing
> NNTP-Posting-Host: 65.202.11.7
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.printing:5016
> X-Tomcat-NG: microsoft.public.win2000.printing
>
> We've been experiencing numerous printer problems ever since the latest
> Microsoft patches were released and installed. It only seems to affect
> Windows 2000 Professional machines (our WinXP workstations do not exhibit
> the problem), and it's only certain printers - the IBM/Lexmark printers.
> When any Win2KPro user attempts to print to one of those printers, a small
> error dialog appears (I don't have a sample, but it wasn't helpful,
> referring to a hex address, didn't even necessarily look printer-related).
> Same dialog appears if the user attempts to view the printer property
pages
> (the properties dialog never comes up).
>
> This problem is growing wider as the day progresses and more users accept
> the prompt to reboot to complete the patch installations. Third party apps
> crash and die when they attempt to print to one of these printers.
> Microsoft
> apps are misbehaving if one of these printers is the users' default
printer.
>
> I've tried removing the printers from the workstation completely and
> reinstalling from the print server. I tried removing the printer and
> deleting the driver files manually, to make sure the ones from the print
> server actually got downloaded and installed. No change. I checked on
IBM's
> site for a newer driver, but it appears that we're already using the
latest
> driver. I'm in the process of building a test machine to do some more
> experiments without impacting user productivity, but I'm running out of
> ideas. Yes, we'd like to upgrade them all to Windows XP, but that takes
> time
> and I need a quicker fix for this problem.
>
> Anybody have any ideas?
>
> Thanks,
> Mike
>
>
>


.

Relevant Pages

  • Re: Cryptogram Comment
    ... >> bother me with Windows questions. ... >> machines are broken. ... Just like if you don't know to tune up your car every year then you ... > and Linux and other open OS's make all patches FREE to redistribute. ...
    (sci.crypt)
  • Re: Cryptogram Comment
    ... Or had to go through setting up basic security for their ... > bother me with Windows questions. ... > machines are broken. ... and Linux and other open OS's make all patches FREE to redistribute. ...
    (sci.crypt)
  • Re: Manually run Auto-Update
    ... Auto-Update downloads it's patches ... > (requiring only the occasional reboot) - the problem arises where the ... The machines ARE connected to the ... Windows) ...
    (microsoft.public.windowsupdate)
  • Re: Cryptogram Comment
    ... Tom St Denis wrote: ... > In his latest Cryptogram Bruce took up the position on the WinXP SP2 patches ... > While I personally hate Windows [on various levels none of which have to do ... 0wned machines? ...
    (sci.crypt)
  • Re: Why not patch all windows and not just legal copies
    ... If bootleg systems received patches, ... Now that reasoning is flawed. ... Can we harden Windows to resist arbitrary attacks? ... windows the ability to patch their computers. ...
    (microsoft.public.security)