Archived from groups: microsoft.public.windowsnt.terminalserver.misc (
More info?)
"max@work" <max@work> wrote on 06 dec 2004 in
microsoft.public.windowsnt.terminalserver.misc:
> Ken Ingvaldsen ha scritto:
>
>> You have to install drivers for local printers on the
>> terminal-server before logging on. Then the printers will be
>> auto-created!
>
> OK. I installed on my PC (client of TS) the printer "HP 2000 C",
> then I went to the server console and I installed the identical
> printer (connected to the LPT1, even if I don't have any printer
> connected to the server).
>
> Then I went back to my PC and I tried to connect to the server
> using a Terminal Server Session.
>
> The Printer/Fax folder only displays the server printer but
> there isn't trace of my local printer.
>
> I'm a newbie, I'm trying to verify if the Terminal Server is
> good for me so it is possible I'm doing something wrong.
>
> If this can hellp, I can say that the server licence is not yet
> activated (I can use the server for 34 days).
>
> thank-you
> Max
Check the EventLog on your Terminal Server, it probably shows you
a couple of Events telling you why the printer isn't autocreated.
The driver names have to match exactly. If they don't, you have to
map the driver to a native driver on the server. Details here:
239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088
The HP Color LaserJet 2000 is not on HPs list of TS-compatible
printers. You might have to map it to a "HP LaserJet Series II"
HP LaserJet Printers and Terminal Servers - Overview
http://h10025.www1.hp.com/ewfrf/wc/genericDocument?
lc=en&cc=us&docname=bpl10248
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---