Additional point of information: The server itself was not yet patched this round of updates, but the XP and Windows 7 clients attaching to it have been. Connecting with a printer that uses Fallback printing (a Xerox in this case) leads to the printer being created, but printing garbage.
-- Durf On Mon, Aug 16, 2010 at 1:21 PM, Durf <[email protected]> wrote: > I am also observing a similar issue on a client 2003 Terminal Server with > Fallback Printing enabled to use a classic HP driver, which is also > essentially what the Universal Print driver does. No further relevant info, > nothing in the eventlogs that is relevant. > > --Durf > > On Mon, Aug 16, 2010 at 1:05 PM, Sean Martin <[email protected]>wrote: > >> Anyone having issues with the latest batch of patches installed on a >> Windows 2003 Printer server? Our users are unable to print to any printer >> utilizing the HP Universal Print Driver. I noticed the latest patches were >> installed late last night so I'm looking at one of those being the possible >> culprit. Just trying to determine which patch it may be.... >> >> KB2286198 >> KB980436 >> KB2079403 >> KB2183461 >> KB982214 >> KB2160329 >> KB2115168 >> KB2229593 >> >> >> - Sean >> >> >> >> >> >> > > > -- > NEW PHONE NUMBER: > tel: 617.671.0572 > Just state your name and wait to be connected. > -------------- > Give a man a fish, and he'll eat for a day. > Give a fish a man, and he'll eat for weeks! > > > > > > -- NEW PHONE NUMBER: tel: 617.671.0572 Just state your name and wait to be connected. -------------- Give a man a fish, and he'll eat for a day. Give a fish a man, and he'll eat for weeks! ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
