Cannot get local printer to print from Terminal Server session

We have an application shared on a Termial Server that requires printing labels to a local Dymo labelmaker on each user's workstation. I know a lot about TS printing, and everything seems to be setup properly, but when the print job gets to the local station it just sits in the queue with an error. Of course, with Windows XP you never get any details on the error, just says "error printing", so we don't know what the problem is. The job is getting from the remote server to the local printer, but won't print. I have run out of things to try. Any suggestions would be welcome.
Rohidas357Asked:
Who is Participating?
 
Beachdude67Commented:
0
 
Rohidas357Author Commented:
No, sorry. This article is just the basics of getting the local printer available when you are in a remote session. In our case the local printer is already available, it just doesn't print. But thanks anyway.
0
 
Beachdude67Commented:
I ran into a similar problem once in an optometrist's office using a custom application. Are you using Office to print or some other application? The application in question required some specific configurations to be made at the workstation.
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
Rohidas357Author Commented:
We are using a specialized medical application, which needs to print labels for specimens that are sent to a lab. But this app is being used at many other locations with very similar configurations to ours, and they have not had any problems like this.
0
 
StashioCommented:
Clearly you know that the print driver has got to be installed on the terminal server so I won't go there. It sounds like an issue with the print queue it's self. Is the printer set up as RAW and have you got the Unix Print Service running? Off the top of my head doesn't Dymo use LPR? Might be wrong - long day but worth a shot!
0
 
forteksCommented:
Rohidas357, did you ever locate a resolution to this problem. I have the exact same setup you describe- medical app, TS, Dymo at local workstations, etc. The print jobs leave the TS session to the local print queue and errorr out. The driver versions are the same on local and TS. Any thoughts or advice would be greatly appreciated. Thanks!
0
 
rohidas57Commented:
I don't know if what we did will be applicable to your situation, but we were, and still are, using a server-based remote printing utility  called UniPrint, which is excellent, as it allows you to turn off printer mapping at the server, and does away with the need for any drivers to be installed on the TS. This would not work for the Dymo, however, due to the way that the software we were using (a specialized app) worked. It requires the remote printer to be chosen from within the applications settings screen, and if printer mapping is turned off, it would not allow the Dymo to be seen or chosen. So our solution was to turn the printer mapping back on.
0
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.

All Courses

From novice to tech pro — start learning today.