Use Dymo Label Printer from Remote site with Terminal Services

By billktd ·
I am having a strange problem and I am looking for some advice. We have a client with two locations. Location 1 is the main office and Location 2 is a remote site. At loc#1 we have a terminal server set up using Server 2008 Std. At the remote site they are using a dymo labelwriter connected via usb to print labels. At the remote site the printer works fine on the local machine (XP Pro). When we connect up using RDP this printer is redirected and shows up in the printer list. If I print a test page it will come through. However, if I open up the DYMO software it will not see this remote printer. I have tryed reinstalling the software but I do not get the option to choose this remote printer that has been redirected. I have also tryed manually installing the printer driver on the server with no luck. If anyone has had similar experience or have found a work around please let me know

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

just a thought

by SystemCheck In reply to Use Dymo Label Printer fr ...

try setting up the labelwriter as a shared might work no harm in it either

Collapse -

As I Recall

by Kenone In reply to Use Dymo Label Printer fr ...

I had to make the DYMO printer a network printer, set it on a standard tcp/ip port and give it an IP address in order to make that work. It has been a while since I set that up but that is what I remember.

Collapse -

Did you use a print server?

by billktd In reply to As I Recall

When you say that you changed the printer to a network printer, I assume you used a print server of some sort? If this is the case you were able to make the terminal session (network #1) see the printer that was physicly connected to network #2? thanks for the help

Collapse -

print server

by bldsm In reply to As I Recall

We bought a cheap print server and plugged our usb dymo printer into it and gave it an ip address. now we can send it details for printing from client's PCs when we do installs and they print out remotely, in order and ready for posting out. google print server.

Collapse -

Terminal Services Easy Print

by joel In reply to Use Dymo Label Printer fr ...

I've seen this happen at one of my clients since they upgraded to 2008..
By default Server 2008 will attempt to load a remote printer using the generic Terminal Services Easy Print Driver first. This _sorta_ allows printing to the dymo, but fails miserably, especially when using either the dymo software or you need to use several label sizes (Like on a Twin)

Under Local Policy or group Policy, you can specify the property of
"Use Terminal Services Easy Print First"
"Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection"
Set this to Disabled.

Next time the user logs on, provided you have the driver installed on the server, it will create a redirected printer using the actual dymo drivers.
At this point you should have no problem using the printer or the Dymo software.

Collapse -

Have you tried a com port redirect?

by magman90 In reply to Use Dymo Label Printer fr ...

In sugesting this I am assuming we do not have a VPN connection beween the terminal server and the remote site.

On the workstation with the printer share the dymo.

Then use the "net use" command to map the printer. I have had the best experience using the loopback ip address... ie "net use com2 \\\Dymoprinter" Be sure you have this com port available on the server.

The create an instance of the printer on the server using this com port.

**Note: port redirection must be anable in order for this to work**

Back to Networks Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums