Defined printers become invalid (randomly) in TS sessions
hi folks,
put problem printing/faxing forum, didn't answers, post here. basic os problem, not printing problem.
problem:
users printing in ts session, no matter type of client, printing errors meaning selected printer invalid or cannot found. happens printers non-default printers user, , non-ms apps. strange thing problems occur of printers, not persistently same printers. printer, except default, can give error, seemingly randomly. when printer has started give off error, it's not usable anymore, unless user chooses printer default. if user chooses printer that's giving error, works printer, some, not all, of other printers start give error instead.
(please, have @ setup first, don't waste time doesn't apply).
i've got following setup:
windows 2008 enterprise server x64 terminal services run. users connect terminal server plethora of different rdp-clients range of os'es (different versions of windows + linux). there no local printers, or other default local devices connected users ts sessions. there separate pdc in network running windows 2008 server core x64. printers, except xps , cutepdf, network printers using raw printing protocol. vast majority of printers hp laserjets, using universal pcl6 64-bit driver. there couple of other pcl-printer types using own drivers, 64-bit. printers on , available. there no shared printers defined, , printers respond raw, or lpd printing protocols. ipp, smb, , switched off.
causing me lots of trouble, , i'd grateful ideas this.
best regards,
peter
put problem printing/faxing forum, didn't answers, post here. basic os problem, not printing problem.
problem:
users printing in ts session, no matter type of client, printing errors meaning selected printer invalid or cannot found. happens printers non-default printers user, , non-ms apps. strange thing problems occur of printers, not persistently same printers. printer, except default, can give error, seemingly randomly. when printer has started give off error, it's not usable anymore, unless user chooses printer default. if user chooses printer that's giving error, works printer, some, not all, of other printers start give error instead.
(please, have @ setup first, don't waste time doesn't apply).
i've got following setup:
windows 2008 enterprise server x64 terminal services run. users connect terminal server plethora of different rdp-clients range of os'es (different versions of windows + linux). there no local printers, or other default local devices connected users ts sessions. there separate pdc in network running windows 2008 server core x64. printers, except xps , cutepdf, network printers using raw printing protocol. vast majority of printers hp laserjets, using universal pcl6 64-bit driver. there couple of other pcl-printer types using own drivers, 64-bit. printers on , available. there no shared printers defined, , printers respond raw, or lpd printing protocols. ipp, smb, , switched off.
causing me lots of trouble, , i'd grateful ideas this.
best regards,
peter
try stressprinters to see if of drivers bad.
Windows Server > Remote Desktop Services (Terminal Services)
Comments
Post a Comment