Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Setting up a Printer on a Terminal Server

Status
Not open for further replies.

niallo32

IS-IT--Management
Joined
Apr 29, 2004
Messages
404
Location
IE
I have a Windows 2003 Terminal Server.
Clients access the Business System on this Terminal Server via web access (VPN).
Normally, when I setup a Clients printer on the Server so they can print to it from the TS, I add a Local Printer, using the Host name of the Client PC as the Port name, get the correct driver for their country, specify the Printer and Share name and it prints no problem.

When I or the user try and Print to the Printer I have setup now, it appears in the Print queue, but has no status against it and just stays there.

Any ideas what I am doing wrong?

The Server is fully patched & AV is up to date.

Thanks,
 
Hi,

I usually the printer driver to the server by adding it as a local printer on lpt1. Then delete the printer - this leaves the driver on the server.
When clients logon they get it fine as their local printer.

Check the clients have the same driver on the local PC's??

Regards
David
 
Thanks Dave, I'll try that.
 
I tried that, installed the correct driver on LPT1 and then deleted the printer, but still does not work.

The user is now logged into the Terminal Server, I reinstalled the printer using his pc host name as the port, tried a test page. It just stays there in the Print queue without a status.

Anyone got any ideas?

Thanks
 
This printer is not a local Printer to the Client, it's a network printer on the Clients LAN. There is no VPN access between the LAN of the TS Client and TS Server.

How should I setup this HP Laserjet 8000?

Thanks.
 
Only Com, LPT and some other port is mapped by TS. Network printers, USB and DOT4 (HP) are not mapped. There a few tricks on the net that allows you to rename the Dot4 and with some registry modifs, it's supposed to work. I tried and it didn't. I'll actually be working on this problem tonight. I managed to get one network printer (xerox) working. Now, I'm trying to get an HP Officejet D135 working. I have another customer who was willing to dish out $$$ and with Citrix everything works fine.
 
Thanks for the feedback, if you get any further with what you're working on, could you let me know?


Thanks
 
Problem solved ! I got almost everything working. For my HP OfficeJet D135, I did the following :


For my other HP Laserjet 3330 (with a print server), I did the following :

Install the printer on each computer using the software cd and point it straight to the IP of the print server. I then installed the printer also with the CD on one local server. I then shared the printer from the server. After that, I connected the share printer to the workstation. I also installed the same printer (using the CD) onto the remote server (TS Server). I then deleted the printer on the remote server. Connected with TS and everything works.
I could also maybe try the same method as I used with the HP D135 but since this method already works for this printer, why change it ! If it ain't broke, don't fix it !

The only problem I have left is with the Xerox Work Center pro 412. Somehow when users print to this printer, it generates error messages but still prints. It also always adds one extra page at the end of the printout with an error msg on it. I'll work on that later this week...

Good luck.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top