 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows 2000 / Terminal Services / April 2006TS Printing error
Win 2000, Printer on client is Oki c5200ne, usb2 connection. TS print generates an error message, saying "error" with no further detail. Will print after clicking the error message. Any Ideas? Thanks. 1. Are you using a built-in MSFT Printer Driver, or one that you donwloaded from Oki? Non-MSFT Drivers can cause all kinds of nasty problems on TS, as they're often not written or tested for use on a multi-user machine. 2. Did you check the event log on the terminal server, for more information on the error. http://www.sessioncomputing.com/printing.htm http://www.printingsupport.com  SignaturePatrick Rouse Microsoft MVP - Terminal Server http://www.sessioncomputing.com > Win 2000, Printer on client is Oki c5200ne, usb2 connection. TS print > generates an error message, saying "error" with no further detail. Will > print after clicking the error message. Any Ideas? > Thanks. Yes the driver is from disk. No available Microsoft driver. Event log does not give more information. Thanks. > 1. Are you using a built-in MSFT Printer Driver, or one that you donwloaded > from Oki? Non-MSFT Drivers can cause all kinds of nasty problems on TS, as [quoted text clipped - 16 lines] > > print after clicking the error message. Any Ideas? > > Thanks. This is the likely cause of your error. Just because the driver does not natively exist, does NOT mean the first course of action is to install the manufacturers drivers, as this is the easiest way (next to making everyone an admin) to de-stabilize your terminal server. The preferred methods are via one of the following: 1. Manual User Defined Inf File Mapping of the unsupported printer to a built-in compatible driver. http://www.sessioncomputing.com/printing.htm 2. Via the Terminal Services Printer Redirection Wizard (automates creating the file and registry settings that would be created manually in number 1). 3. Via Fallback Printer Driver in 2003 SP1 (an on the fly automation of the printer mappings done in 1 and 2). 4. via 3rd party printing program like ThinPrint .Print RDP Engine, triCerat Simplify Printing, or Provision Networks Print-IT. If you often fight with printing problems, this is the best solution, as these will allow you to print to virtually any printer w/o loading a new driver on the terminal server each time. SignaturePatrick Rouse Microsoft MVP - Terminal Server http://www.sessioncomputing.com > Yes the driver is from disk. No available Microsoft driver. > Event log does not give more information. [quoted text clipped - 22 lines] > > > print after clicking the error message. Any Ideas? > > > Thanks. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.