Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 515
  • Last Modified:

Local Printer not connecting through Terminal Services

I have an odd problem that is been driving me nuts all day. I have searched the web and found a few articles of things to try to help remedy my problem but none of them seem to work. I now turn to the experts for their help.I have a client with two offices about 65 miles apart. The main office houses the server that has a certain medical application on it. The remote office logs in through terminal services to access the medical application. Up until 3 weeks ago, when the server hard drive bombed and had to be reloaded, the remote office had no problems printing locally to a printer at their remote office. Since the hard drive reload, when the remote users terminal service into the server it does not map their local printer so they cannot print to the USB printer attached to their local machine at the remote office. ( I hope all of these references to local and remote makes sense) I have applied the fixes listed in the following articles but they still did not remedy the problem.

Both the local server and the remote workstation are Windows 2000.
Just to sum the whole thing up:
Remote users Terminal service into the local server to use the medical software. The remote users are unable to print to the USB HP Laserjet 1200 that is attached to their PC at the remote office. I am offering 500 points for this because it is really urgent and really drving me insane as to how to fix it. Thanks in advance.
  • 2
1 Solution
Having not read the entire document you attached (just too long) I would try

1) Make the printer shared from the remote workstation and publish the queue in Active Directory
2) Install the driver locally on the terminal server (if possible, and not shared just to have the dlls present) and use the Remote Desktop client (instead of the older tsec client) with printer redirection checkbox enabled

The RDP client will log errors in the event logs if there is an issue with the printer queue and drivers. If there are genuine erros (as some are just notices) paste them here so we can see what they are.
robertbranchAuthor Commented:
I shared the printer from the remote workstation and published the queue. The printer driver is already installed as there is an identical printer already connected to the terminal server.

I did notice a few more things I find "fishy". From the remote PC I choose to also share my Disk Drives, these remote drives also do not show up on the terminal server like they do if I connect to any other machines. I tested this by creating a new RDP connection back to a server that I have in my office. When I connected to my server, the disk drives were shared but the printer was NOT. I cannot find any errors in the event viewer of my server nor the remote terminal server that the problem originated on. It is almost as if Windows doesn't even recognize that there is a printer attached to the remote PC, although they can print to it locally with no problems. I think I am losing my mind on this one.
robertbranchAuthor Commented:
The solution was a registry hack that allows all printers to be redirected not just the default port names.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now