Redirecting Network Printers

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

Guest

Hi. How do I get network printers i.e. IP based to be redirect when a users
is connected to a TS. I know that Win 2000 does not do that by design but are
there work around for this?
 
HI, I tried this.

There is a network printer(A) via HP jetdirect with IP 10.10.10.1. I
installed that printer(A) onto the TSrv as a local IP printer via add
printer utility(created a TCP/IP port) and then shared the
printer(A_shared). Next I executed net use lpt1 \\Tsrv\A_shared at my PC. But
after I run the cmd, I don't see anything in my printer menu. Maybe nothing
should actually appears. Then, I installed the same printer model as my lpt1
printer(B) and not as IP based. I guess I need to tell apps to print to a
printer. I guess I'm still at the right track. Then, when I connect to TS,
the printer(B) gets redirected onto the Tsrv. I can print to the network
printer 10.10.10.1. The path taken for printing is from the redirected lpt1
printer created at the TSrv(TS_B) to my lpt1(B) and then to the TS shared
printer(A_Shared) and then to the IP printer(A). This is a long shot. Any way
to reduce the steps?
 
Use Remote Desktop Client version 5.2.3790 or 5.2.3790.1830.

If you have access to a Windows 2003 server, you will find
the install files in C:\WINDOWS\system32\clients\tsclient\win32

You can also download the client from the web (not MS's site),
use Google to find.

If you need to use an older client, see this kb article:

http://support.microsoft.com/kb/302361

-TP
 
Hi, I'm using the web based Terminal access thru http://servername/tsweb on
Win 2K srv. I found that the TSrv can redirect IP based network printers. The
catch is that the driver must match. My printer driver on my PC was HP4050
PCL 6 while the server had PCL5 driver installed. After I updated the server
with the PCL 6 driver, I was able to redirect the IP printer. tested OK!
 
I'd be careful about installing 3rd party printer drivers on your terminal
servers, even the ones from HP that they certified for use on TS & Citrix.
3rd party printer drivers (those that didn't come with your version of
Windows Server) are by far the number one cause of instablility on terminal
server, often causing spooler failures and even server reboots (if using a
kernel mode driver).

I'd highly recommend that you stick with the built-in drivers whenever
possible, and use driver mapping to map a natively unsupported printer to a
bult-in compatible driver. For LaserJet 4xxx series printers I use LaserJet
4 Plus Drivers.

Built-in PCL5 & PS Drivers are the safest, whereas PCL6 drivers tend to be
more problematic and cause much larger spool files. Disabling the advanced
printing options in the client's printer properties can reduce the spool size
by up to 90% on certain types of files.

NEVER, EVER use a kernel mode printer driver on a terminal server. These
are the ones that are labled for use with NT4 and 2000, not for XP or 2003.
These drivers run in system context and if they become unstable will likely
BSOD your server.

http://www.sessioncomputing.com/printing.htm
 
What is driver mapping and how do I do that? The advance printing option, is
that at the advance tab where options such as 'spool first, printer
immediately' etc is located. If so, what options may reduce spool size.

Thanks
 
You must be using a newer version of tsweb than what shipped
with Windows 2000 Server.

I recommend following Patrick's advice and mapping your
printer to a built-in driver. If you choose to do this you should
remove the new driver you installed. Please read the article
below for instructions.

Windows 2000 Terminal Services server logs events 1111, 1105, and 1106

http://support.microsoft.com/kb/239088

Thanks.

-TP
 
Back
Top