Archived from groups: microsoft.public.windowsnt.terminalserver.setup (
More info?)
Yes, of course they are autocreated, since you installed the
drivers on the server. That enables the server to recognize the
printer and autocreate it.
But it does NOT mean that the printer driver is TS-compatible, and
it obviously isn't, since it crashes your printer spooler. That's
what causes all printers to stop working and slows down your
server.
Uninstall the printer drivers completely. Then the printer will not
autocreate anymore, you will get Event 1111, 1105 and 1106, which
will give you the information you need to map them to a native
driver.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
"Adrian Lamas" <adrianlamas@hotmail.com> wrote on 29 jan 2005 in
microsoft.public.windowsnt.terminalserver.setup:
> Vera, thanks for helping.
>
> Actually, HP3650 and HP3820 are autocreated each time terminals
> logs on. They works properly until one of them crashes (never is
> the same printer, the problem shouldn´t be with a particular
> printer). Then the user CLOSES THE SESSION because the printer
> doesn´t responds (you can open the PRINTER FOLDER on server and
> you can see his printer autocreated with one document with state
> DELETING DOCUMENT), inmediatly all other printers stop printing,
> even if users send documents, and windows 2000 server became
> slow.
>
> I´m checking the URL http://support.microsoft.com/?kbid=239088,
> I will let you know in case my trouble was resolved mapping the
> printer.
>
> Regards
>
> --
> Adrián V. Lamas
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
> escribió en el mensaje
> news:Xns95ED1AA6694Dveranoesthemutforsse@207.46.248.16...
>> I'm sorry, but HP DeskJet 3650 and 3820 are not supported in a
>> Terminal Server environment.
>>
>> Even if they were, it is never recommended to install 3th party
>> printer drivers on a Terminal Server. Most of these drivers are
>> not TS-compatible and they can easily crash your printer
>> spooler or your whole TS.
>>
>> What you should do if the printer is not automatically created
>> in the TS session is to check the EventLog on the TS for the
>> reason why. If you see Event 1111, stating that the driver is
>> unknown, you can map the printer driver to a native driver on
>> the server (one that came with the operating system).
>> The article below explains how to do this.
>> I would give it a try by mapping them to a HP DeskJet 550C. Be
>> sure to uninstall the HP DeskJet 3650 and 3820 drivers first.
>>
>> 239088 - Windows 2000 Terminal Services Server Logs Events
>> 1111, 1105, and 1106
>>
http://support.microsoft.com/?kbid=239088
>>
>> --
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>
http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>> "Adrian Lamas" <adrianlamas@hotmail.com> wrote on 28 jan 2005
>> in microsoft.public.windowsnt.terminalserver.setup:
>>
>> > Good evening and thanks for help in advance.
>> > Sorry because of my english, I would like to find a spanish
>> > newsgroup to expose my problem.
>> >
>> > Server: Windows 2000 SP4 with Terminal Server
>> > Terminals: Windows XP Pro and Windows ME.
>> > Printers: 8 HP 3650 and 2 HP 3820
>> > Installation Process: I just installed driver in server and
>> > terminals machine, when they logs on terminal server
>> > autodetects the printer.
>> >
>> > Problem:
>> > One Printer spool hangs showing DELETING DOCUMENT and all
>> > other printers stop printing (just show PRINTING status but
>> > nothing happends)
>> >
>> > Question:
>> > Did I make a bad installation for printers ? Should I make
>> > another kind of installation ?
>> >
>> > Please, help me on this because it´s making me crazy.
>> > I´m sure I´m doing something wrong, since I´m not an expert
>> > in Terminal Server.
>> > Thank you in advance.
>> >
>> >
>> > --
>> > Adrián V. Lamas
Facebook
Twitter
Instagram