7 replies
by Member 29039981 Accepted solution
by systemcheck Accepted solution
by kenone Accepted solution
by Member 29039981 Accepted solution
by bldsm Accepted solution
by vw71superbeetle Accepted solution
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"
under
"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.
by magman90 Accepted solution
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 \\127.0.0.1\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**
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending