Print server + TS head-scratcher

Hello All,

A quick intro from me - I work in IT support in a healthcare environment and I'm a long time reader (but a noob poster) on TR. I've certainly benefitted in the past from the pool of tech (and other) knowhow around here and maybe MAYBE I can even contribute something in return happy

Back to my issue: I'm trying to get my head around a printer setup problem. I'm aware of the basic 2 ways to set up a printer for use on a network: 1) install it locally on a workstation and then share it, or 2) attach it to the network directly using a print server device (e.g. HP JetDirect or some such device). In 1) the printer is available as a network shared resource and in 2) the printer has it's own IP address and is independent from any workstation. Of course there are advantages and disadvantages of both.

Now, when I was doing some TS testing I discovered that the network-attached printers are visible to TS users, but the locally shared printers are not. (Well, a shared printer can be seen from the TS box itself, but a user connecting to a TS session can NOT see it.)

So I'm trying to 'cheat'. I'm trying to make a locally shared printer look like it's a network printer. Is there a way to do this? I first tried by installing a USB printer locally at a pc, and then from a different pc, installing THAT printer as a network printer, i.e. adding a printer, choosing a TCP/IP port (and giving the IP address of the first pc, to which the printer is attached), and selecting a driver, etc. Basically I want the first pc to behave like that printer's 'JetDirect'.

It actually lets me complete the setup, but when I try print a test page then nothing happens.

Am I attempting the impossible? Is there a workaround or some piece of software that can do the trick? Or maybe just a setting in Windows printer setup that I missed?

Any help will be most appreciated.

Cheers,

Tags: windows, software, hardware, network, server, networking, terminal server, printer, print, setup, ts

cmaritz@...

13th Oct 2008

Answer the Question

Answers (1)

Preferences

0 Votes

+ -

A little unclear but here goes.

When you refer to a "locally shared printer" I take it you mean the printer is shared from a desktop/workstation instead of the print server.

This is still technically a networked printer but the workstation is acting as a stand alone print server.

First rule to remember. Only buy printers with a network adapter. Prefereably HP. (My personal preference)

Second. Only share printers to the network from a server where you can control access to the printer through user rights.

It sounds like you want Terminal Services to re-direct print output to the "locally shared printer" that is installed/configured at the workstation that is using RDP/Terminal Service Client.

The server will usualy not re-direct printers unless it has at least an appropriate printer driver installed at the server.

You can try creating or configuring the "locally shared printer" on the TS Server itself. By this I mean add the printer at the server, pointing it to the workstation that is sharing the printer to the network. It may then recognise it as an available resource and re-direct properly.

1bn0

14th Oct 2008

Replies

Thanks also for clearing up my terminology.

"You can try creating or configuring the "locally shared printer" on the TS Server itself. By this I mean add the printer at the server, pointing it to the workstation that is sharing the printer to the network. It may then recognise it as an available resource and re-direct properly."

I tried this (by sharing the printer on the workstation and then connecting from the TS server to \\workstation\printer, right?). The printer installs on the TS server fine, and I can print a test page. However, as a user connecting on a TS session, I cannot even see that printer in the list of available printers. The only printers I do see are the ones that were installed by going the route of specifying TCP/IP port (i.e. for those printers that have their own network adapter or that are connected to a JetDirect). I've double-checked the permissions on each printer added on the TS box and all are set to allow the test user to print, so I'm sure it's not a permissions problem.

Hence, just to see what happens, I tried to install the printer shared from the workstation by going the TCP/IP route (giving the workstation's IP address), instead of installing by connecting to \\workstation\printer. The installation does complete and a printer is added, but nothing ever prints - always get an error.

Is there a way to get a printer that is shared on a workstation to show up correctly for a user in a TS session?

Cheers,

cmaritz@... 14th Oct 2008