Printing is really slow since I patched last ...

[Guest]

Hi,

I patched my domain controller (Windows 2000 SP4) on Tuesday, July 26th.
Since I patched it, I am getting weird complaints about slowness with HP
printers. I have no errors in event viewer that would give me any clues as
to the issue. The printers are not down, just really slow compared to normal
operation. Here are the patches I applied...

Windows 2000 family Update Rollup 1 for Windows 2000 Service Pack 4
(KB891861) Tuesday, July 26, 2005 Windows Update website
Windows 2000 family Security Update for JView Profiler (KB903235) Tuesday,
July 26, 2005 Windows Update website
Windows 2000 family Windows Malicious Software Removal Tool - July 2005
(KB890830) Tuesday, July 26, 2005 Windows Update website
Windows 2000 family Security Update for Windows 2000 (KB901214) Tuesday,
July 26, 2005 Windows Update website
Windows 2000 family Cumulative Security Update for Outlook Express 6 Service
Pack 1 (KB897715) Tuesday, July 26, 2005 Windows Update website
Windows 2000 family Security Update for Windows 2000 (KB896358) Tuesday,
July 26, 2005 Windows Update website
Windows 2000 family Security Update for Windows 2000 (KB890046) Tuesday,
July 26, 2005 Windows Update website
Windows 2000 family Security Update for Windows 2000 (KB896422) Tuesday,
July 26, 2005 Windows Update website
Windows 2000 family Cumulative Security Update for Internet Explorer 6
Service Pack 1 (KB883939) Tuesday, July 26, 2005 Windows Update website
Windows 2000 family Security Update for Windows 2000 (KB894320) Tuesday,
July 26, 2005 Windows Update website
Windows 2000 family Microsoft Windows Installer 3.1 Tuesday, July 26, 2005
Windows Update website
Windows 2000 family Update for Background Intelligent Transfer Service
(BITS) 2.0 and WinHTTP 5.1 (KB842773) Tuesday, July 26, 2005 Windows Update
website

None of these patches seem to have anything to do with printers. Can
someone give me an idea to try out and fix this issue >???

 

[Guest]

Also, the user's who are complaining of slowness get this warning :


Event Type: Warning
Event Source: Print
Event Category: None
Event ID: 20
Date: 8/1/2005
Time: 7:27:49 AM
User: NT AUTHORITY\SYSTEM
Computer: MARVIN-XP
Description:
Printer Driver HP LaserJet 5Si Mopier for Windows NT x86 Version-3 was added
or updated. Files:- UNIDRV.DLL, UNIDRVUI.DLL, HPMOPY.GPD, UNIDRV.HLP,
UNIRES.DLL, STDNAMES.GPD, hpcui02.dll, hpcrd02.dll, hpoemui.dll, hpcmbox.ini,
pcl5eres.dll, hpcstr02.dll, hpcljx02.hlp, UNIRES.DLL, STDNAMES.GPD,
TTFSUB.GPD.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Almost looks like a driver got updated and it is bad ????

Serge

 

[Guest]

I thought I fixed it by reinstalling the drivers … they seemed happy for
about 2 hours, and then they are reporting slowness again … think I need to
reboot my domain Controller ?

VSACIT

 

[Jimmy]

If you have not rebooted the server machine, then it may be a good idea to
do so. The operating system will postpone deleting driver-files until they
are no longer in use. Patching the operating system without rebooting is
great, if it works. If things don't work right, then rebooting may be the
solution.

The event-message looks like the printer driver on the client machine is
being updated automatically. Sometimes, this does not work properly
(version numbers, cached-copies of drivers, system restore).

If you suspect a printer-driver problem on the client machine, open up
Printers, delete the printer, then use File / Server Properties / Drivers,
then remove the drivers for that printer. Then, add the printer again.

If this does not correct the problem, then maybe the client machine is not
getting the latest printer-driver from the server machine, so you may need
to remove the "cached" drivers, after using File / Server Properties /
Drivers, and removing the drivers for that printer. Open up a command
window and go to \WINNT \ INF . Use "DIR OEM*.INF". Each of those .INF
files is some kind of hardware that was added to the system. Find which one
of those is for the problem printer. It will be OEM0.INF or OEM1.INF or
OEM2.INF, etc. Delete the OEM#.INF and the OEM#.PNF (the .INF is, as we all
know, the install script, and the .PNF is a compiled-version for use by the
system). Also, if a client machine is XP, delete the INFCACHE.1 file.
Then, add the printer again. Now, the system will not use any
cached-and-out-of-date drivers.

 

[getmeek]

I run Windows2000 server standing alone. My printing is now also so
slow as to be useless, after applying latest Windows 2000 updates.

Any help out there?