Can't print from terminal session

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Invisible - 27 May 2005 10:58 GMT

Greetings.

I have a user with a USB printer connected directly to their laptop.
They connect to a terminal server, and the printer doesn't show up. The
guy at the other end thinks it's because the drivers weren't installed
on the server. Sure enough, the printer now DOES show up... but still
won't actually PRINT anything. (Print job appears saying "spooling".
Remains at 0 bytes forever.)

Terminal server is Windows 2003 Enterprise Edition. Laptop is Windows XP
Professional (can't remember what service pack off the top of my head;
it's at least SP1, might be SP2). Printer is HP LaserJet 1000.

Any hints...? The terminal server operators are going to take until next
Christmas to get back to me on this... and it's a tad more urgent than that.

Thanks.

Reply to this Message

APLavitt - 27 May 2005 17:33 GMT

USB's are tough. You probably should get a third party software. I have a few
clients setup on Uniprint, Uniprint.net is the site.
Not cheap, but after client install on the local machine,, works perfectly.
Arthur

Signature

Arthur Lavitt

> Greetings.
>
[quoted text clipped - 13 lines]
>
> Thanks.

Reply to this Message

Vera Noest [MVP] - 27 May 2005 21:47 GMT

The USB connection is not the problem, it's the printer model.
You will not get this to work with the HP LJ 1000 driver, since HP
LJ 1000 is not supported on a Terminal Server. Documented here by
HP:

HP Color LaserJet, LaserJet, All-in-One, and Multi-Function Series
Products
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?
objectID=c00213455&locale=en_US&taskId=101&prodSeriesId=410622
&prodTypeId=18972

I would uninstall the HP LJ 1000 driver from your server as soon as
possible.
Installing 3th party printer drivers on a TS is *not* recommended.
Most of these drivers are not completely TS compatible, and are
known to crash the printer spooler or the whole server.
If your client printers are not autocreated, check the EventLog to
find the reason. If the server doesn't recognize the printer, map
the printer to a native driver on the server, by creating a custom
ntprintsubs.inf file. Details are explained here:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

You can check the recommended native driver substitution for your
local printers here:

Client Printer Autocreation Matrix
http://www.printingsupport.com/matrix.htm

If you are running 2003 SP1 on your Terminal Server, you can
configure a Terminal Server Fallback Printer Driver. For more info,
check:

http://www.thelazyadmin.com/index.php?/archives/18-Terminal-Server-
Fallback-Printer-Driver.html#extended

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Invisible <void@dev.null> wrote on 27 maj 2005 in
microsoft.public.win2000.termserv.clients:

> Greetings.
>
[quoted text clipped - 16 lines]
>
> Thanks.

Reply to this Message