TS client not printer to local printer

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a user who is connecting to a W2K server running terminal services.
She is on a win XP Pro machine and has a brother hl-1440 series printer. She
had previously been printing just fine. I don't know what the change was,
but now if she tries to print it will only print the top three or four lines
of the print job or freeze up the printer.

I have uninstalled and reinstalled the printer many times on both the server
and her machine, but to no avail. I'm really frustrated here and could use
any help. In the event logs it just says that so and so printed such and
such document on port TS00some number. size (some number) pages printed:0

When she logges in,the even viewer displays multiple informational events
that such and such printer on her computer was set and then it will say that
it was unpublished.

like this:

Printer Brother HL-1440 series/computername/Session 14 was set.
(it will have 3 or four of these in a row)

then will finally have this:
Printer Brother HL-1440 series/computername/Session 14 was successfully
unpublished.

I have also been getting some of these errors, but they don't seem to be
related:
The Print Spooler service terminated unexpectedly. It has done this 1
time(s). The following corrective action will be taken in 60000
milliseconds: Restart the service.

When ever I check the service is started and I can restart it just fine.

Again, any help here is very appreciated.

Thanks in Advance,

Tia
 
I don't have a water-tight explanation for why this stopped
working.

The general recommendation is to *not* install 3th party printer
drivers on a Terminal Server. Most of these drivers are not 100%
TS-compatible and known to crash your spooler service and
sometimes the whole server. I believe that this is what happens at
your place: the Brother driver crashes the spooler, and that makes
the printout fail.

The solution is to completely uninstall the 3th party driver from
the server, and instead map the local printer driver to a native
Windows 2000 driver on the server, by creating a custom
ntprintsubs.inf file.

For your Brother printer, I would start to map it to a HP LaserJet
4 printer driver.

Details here:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088
 
Thanks you so much. I will give this a try!!

Vera Noest said:
I don't have a water-tight explanation for why this stopped
working.

The general recommendation is to *not* install 3th party printer
drivers on a Terminal Server. Most of these drivers are not 100%
TS-compatible and known to crash your spooler service and
sometimes the whole server. I believe that this is what happens at
your place: the Brother driver crashes the spooler, and that makes
the printout fail.

The solution is to completely uninstall the 3th party driver from
the server, and instead map the local printer driver to a native
Windows 2000 driver on the server, by creating a custom
ntprintsubs.inf file.

For your Brother printer, I would start to map it to a HP LaserJet
4 printer driver.

Details here:

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 reply in newsgroup -------------*
Click to expand...
 
Sorry this is going to be a stupid question, but after I totally remove the
printer from the server. I still need to add it back again correct? And I
want to add it w/ the HP LaserJet 4 printer driver? I did all the mapping
and whatnot. Thanks for your help!!
 
No, you do not have to install the printer on the server.

When the client (who has the printer installed locally) connects
to the TS, the TS checks which printers the client has installed.
If the TS recognizes the printer on the client (either because it
has an identical driver, or you have "told" the server to threat
this printer as a known printer), then the client printer is
automatically created inside the rdp session.

So the only thing you have to do is to let the client connect
once, look in the EventLog on the server for Event 1111, which
gives you the exact printer driver name, and then add a line to
the custom ntprintsubs.inf file which maps this driver name to the
HP driver. And folllow the rest of the instructions in KB 239088,
about the registry key pointing to your custom ntprintsubs.inf.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
the print processor for brother printers always screws up the print spooler
in win2k and xp. change it under the printer properties to the winprint raw
one and you should work fine.
 
Back
Top