Brian Madden Logo
Your independent source for application and desktop virtualization.
advertisement

TS Printing Issue, in the Terminal Services forum on BrianMadden.com

rated by 0 users
Not Answered This post has 0 verified answers | 10 Replies | 6 Followers

Not Ranked
Points 110
jlawre23 posted on Fri, May 22 2009 11:28 AM

I have a user that connects to the TS 2008 server, printer maps

properly, but when they print, it doesn't print out.  It spools to his

machine and even shows it successfully printed, but nothing comes

out.  We have rebooted the server and the workstation as well

as the printer with no go.  Any ideas?

  • | Post Points: 50

All Replies

Not Ranked
Points 40

Hey jlawre - I have a similar problem with TS2008 - some of my clients print fine and some of them - can click Print and I go into the Event Viewer on the TS server and it says it printed successfully - but no printout... Can print locally to the Printer outside the TS... argh! Have tried Domain Administrator account to see if it was a permission issue - but to no avail. I even installed the driver on the server - to eliminate Easy Print - but still same issue - are you using 64bit 2008 server also?

Derry

  • | Post Points: 20
Not Ranked
Points 110
jlawre23 replied on Tue, Jun 30 2009 10:36 AM

Sorry for the late reply.  Yes we are using the 64-bit version of Win2k8.  I also tried to use the Easy Print and removed it too, but neither helped.  I ended up setting the user up to use a Win2k3 server and everything worked as it should.  I have yet to get any help with this issue.

  • | Post Points: 20
Top 10 Contributor
Points 24,510

How is the printer installed on the client side (i.e. local, network, IPP)?

Also, how is the printer connected to the remote computer (locally via USB/parallel printer cable, via a print server, or via direct TCP/IP connection to network attached printer)?

Does making the end user of the workstation a local administrator make any difference?

 

Alan Osborne

President (MCSE, CCNA, VCP, CCA)

VCIT Consulting - Citrix/Terminal Services Remote Desktop Solutions for SMB

VCIT website My Blog

  • | Post Points: 20
Not Ranked
Points 110

The printer is installed locally on the client side.  As for the remote TS session, the printer automatically creates a printer on the TS server when the user connects based on the correct drivers being on the TS server.

Local admin rights didn't make a difference as the user is the local admin of his PC.

  • | Post Points: 35
Top 25 Contributor
Points 7,839
Dan Foley replied on Wed, Jul 1 2009 10:16 AM

Have you tried mapping the driver in Citrix?  Is this a deskjet printer?

  • | Post Points: 11
Not Ranked
Points 235

Have you tried changing the "Print Processor" on the advanced tab of the properties of the client's local printer.  I've found that setting it to "WinPrint" "RAW" works in most cases but there have been times I've had to set it to something else. 

Hope this helps.

Sam

Sam Snyder
Sr. Consultant
  • | Post Points: 20
Not Ranked
Points 55

Try toggling BiDirectional support on the client side. Alternatively you could try what have just had to so and share the printer and then map it back from the ts session to the client. Sounds a bit crazy but i have found this a great work around for a few of the printing quirks with ts2008. I can give you a script that will auto map the printer for you based on client name.

  • | Post Points: 5
Not Ranked
Points 55

Also if the default behaviour of the printer driver is to enable bidi support on the recreated (server side) printer then it is likley not to work.

  • | Post Points: 5
Not Ranked
Points 70
Nice69 replied on Thu, Aug 27 2009 8:59 AM

Install the CORRECT printer driver on the TS, and by correct I mean the driver for the client machines printer and OS.

If the user is connecting with a 32bit XP machine, a 64 bit 2008 driver won't work properly.

If you look in the print server settings on the 2008 box, you will see you can add other OS's drivers.

 

 

  • | Post Points: 5
Not Ranked
Points 185

I had a similar issue with some of my local printers.  Turns out it was due to the USB connection.  If you notice that the DOT is the port used, you might want to try updatingyour TSC.  I have copied our reg entry.  Hope this helps.

 

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR]

  • | Post Points: 5
Page 1 of 1 (11 items) | RSS