Providing local printing for unsupported drivers...

[Brad Pears]

We have a windows 2000 (SP3) Terminal Server and are allowing remote users
to log into our systems using TS sessions.

Most of these users have the 3-in-one HP printers and I am having all kinds
of problems getting them to print.

First off, neither of these printers (HP PSC 750 and PSC 950) are supported
by Win2000 by default, so does that mean that I have to obtain the printer
drivers for each of these unsupported printers and install onto our terminal
server in order to provide local print support for these users?

I read somewhere where you only need to make an entry in the NTPRINT.INF
file that has the EXACT driver name the client has and you'd be good to go.
I tried this and it does not work. How can it if you don't have the proper
driver installed? I think the instructions were not correct.

Can someone tell me exactly what all is required to provide local client
print support for unsupported printers in windows 2000?

Two of the printers I am having most problems with are USB connected HP PSC
750 all-in-one and PSC 950 all-in-one. (I've been told USB printing should
be no problem)

Both of these users are running the RDP 5.1 or 5.2 client .

Thanks,

Brad

 

[Matthew Harris [MVP]]

NTPrint.inf allows the terminal server is use a substitute
driver for printers that clients have, in the case where
the client is using a printer who's drivers are not on the
terminal server.

Take a look at this link:

support.microsoft.com/default.aspx?scid=kb;en-us;275495

Those 3 in 1 printers are always a problem. To start out,
try mapping them to use the LaserJet 4 drivers (using the
ntprint.inf file). If that doesn't work, then check out
www.printingsupport.com to see if you can find the printer
there.

-M

 

[Brad Pears]

Thankyou for the responses you have both given me. I really appreciate it.

A couple of quick questions...

1) If I do a substitution and use a supported print driver such as an HP
Laserjet IV driver etc... instead of the native all-in-one drivers, do I
have to change the clients local print driver as well to use that driver or
just do the substitution on the terminal server?

2) It looks like to provide the USB support, some registry hacks may need to
be made. The article written by Microsoft on this was really unclear on
which machine the hacks need to be made (server or clients). However, I am
assuming the hack must be made on the client as the client has the registry
key effeected while the server does not. Can you clarify that for sure?

Thanks,

Brad

 

[Vera Noest [MVP]]

(1) No, you should not change the driver on the client, just record the
exact name and use that to map it to a supported printer driver name on the
server.

(2) The reghack for the USB printers must be made on the client.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

 

[Brad Pears]

Thank you!

Brad

(1) No, you should not change the driver on the client, just record the
exact name and use that to map it to a supported printer driver name on the
server.

(2) The reghack for the USB printers must be made on the client.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*