PC Review
Forums
Newsgroups
Windows 2000
Microsoft Windows 2000 Terminal Server Applications
Printing Problem
Forums
Newsgroups
Windows 2000
Microsoft Windows 2000 Terminal Server Applications
Printing Problem
![]() |
Printing Problem |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
How can I have a user using Terminal Service use a network printer.
I have created a network printer on the users session but when I try to print from that session it does'nt work. |
|
|
|
#2 |
|
Guest
Posts: n/a
|
You also have to load that print driver on the Terminal Server. >-----Original Message----- >How can I have a user using Terminal Service use a network printer. >I have created a network printer on the users session but when I try to print from that session it does'nt work. >. > |
|
|
|
#3 |
|
Guest
Posts: n/a
|
Beware...loading a printer driver onto a terminal server
is a dangerous activity. If the printer driver fails or crashes, it has the potential to crash your entire system. You are much better off using a driver that came with the original Windows 2000 disk and editing the ntprint.inf file to force the system to use a particular pre-installed driver for that printer. -M >-----Original Message----- > > > You also have to load that print driver on the Terminal >Server. >>-----Original Message----- >>How can I have a user using Terminal Service use a >network printer. >>I have created a network printer on the users session but >when I try to print from that session it does'nt work. >>. >> >. > |
|
|
|
#4 |
|
Guest
Posts: n/a
|
Matthew,
Why is this? I have many laser printers that are not avail. in the original 200 disk (mostly Samsung) and have been using their drivers on my TS. Do you think it might be a good practice to uninstall and re-install the drivers from time to time, or are you saying I need to find a compatible driver and include a line in the Models Section of that .INF file that lists that printer name and associates it with the compatible *.GPD or *.PPD file? Or do you know if there are some companies (like Samsung, hopefully) that "certify" their drivers with TS? Thanks! Mark B ----- Matthew Harris [MVP] wrote: ----- Beware...loading a printer driver onto a terminal server is a dangerous activity. If the printer driver fails or crashes, it has the potential to crash your entire system. You are much better off using a driver that came with the original Windows 2000 disk and editing the ntprint.inf file to force the system to use a particular pre-installed driver for that printer. -M >-----Original Message----- >>> You also have to load that print driver on the Terminal >Server. >>-----Original Message----- >>How can I have a user using Terminal Service use a >network printer. >>I have created a network printer on the users session but >when I try to print from that session it does'nt work. >>. >>>. > |
|
|
|
#5 |
|
Guest
Posts: n/a
|
Admittedly, some printer drivers are perfect and never
crash, however, there are a bunch out there that do. It is easier to just not load any of the drivers and just use a generic universal driver instead, rather than loading a ton of drivers, than having your system crash, and then having to unload all of them until you find the offending one. Y'know what I mean? The best practice and most recommended thing to do is to not load any of the drivers (or unload them if you have them), and then edit the ntprint.inf file (or printupg.inf file) to force the terminal server to use a specific driver for a specific printer. Check out this article for more information: support.microsoft.com/default.aspx?scid=kb;en- us;275495&Product=win2000 I'm sure that some companies do "cerify" their drivers, but if someone told you that jumping off a building was safe, would you do it? Seriously though...if you absolutely need to use a driver because of some feature or whatnot, be sure to test the driver. I needed to use a special duplexing option on an HP printer, so I loaded the driver up on a test system and tested it for a week before even thinking about touching my production servers. Using a third-party's driver isn't bad, but past experiences make everybody a little touchy and send up red flags everywhere.. -M >-----Original Message----- >Matthew, > >Why is this? I have many laser printers that are not avail. in the original 200 disk (mostly Samsung) and have been using their drivers on my TS. > >Do you think it might be a good practice to uninstall and re-install the drivers from time to time, or are you saying I need to find a compatible driver and include a line in the Models Section of that .INF file that lists that printer name and associates it with the compatible *.GPD or *.PPD file? > >Or do you know if there are some companies (like Samsung, hopefully) that "certify" their drivers with TS? > >Thanks! >Mark B > > ----- Matthew Harris [MVP] wrote: ----- > > Beware...loading a printer driver onto a terminal server > is a dangerous activity. If the printer driver fails or > crashes, it has the potential to crash your entire > system. You are much better off using a driver that came > with the original Windows 2000 disk and editing the > ntprint.inf file to force the system to use a particular > pre-installed driver for that printer. > > -M > > >-----Original Message----- > >>> You also have to load that print driver on the Terminal > >Server. > >>-----Original Message----- > >>How can I have a user using Terminal Service use a > >network printer. > >>I have created a network printer on the users session > but > >when I try to print from that session it does'nt work. > >>. > >>>. > > > . > >. > |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

