Terminal Server Exits on print

Question

Level 1

9 points

Terminal Server Exits on print

Hi All,

Client: Mac OS 10.6.6
rdesktop: rdesktop-1.6.0.dmg
Server: Windows 2003 R2, Sp2, 32 bit

We do not use M$'s RDP for MAC as it does not support port masking.

I have a customer with a Apple that has the annoying habit of
exiting his Terminal Service session whenever he tries to print (from
TS). When he logs back in to terminal services, he pick up right where
he left off. All except no print out.

I have done three other Apples with the same set up. No problems.

Has anyone come across this problem and how did you fix it?

Many thanks,
-T

Posted on Mar 3, 2011 7:08 PM

Reply

Answer 1

Todd twice Author

Level 1

9 points

Mar 6, 2011 3:05 PM in response to Todd twice

This is all command line. It looks like this on the apple side:

/usr/bin/rdesktop -N -a 16 -d FOODOMAIN -u xxxxx -p yyyyyy -g 85% -r printer:'Officejet 7500_E910_670D7C'='HP Officejet 7500 E910' -r printer:'HP Color_Laser_2840_143703'='HP Color LaserJet 2840 PCL 6' -r disk:MyShare=/Users/xxxxx/Desktop -r clipboard:CLIPBOARD server[:port]

Where
-N: enable numlock syncronization
-a: connection color depth
-d: domain
-u: user name
-p: password
-g: desktop geometry (WxH)
-r: enable specified device redirection (this flag can be repeated)

The print redirection is done with the "-r" flag. In this instance, two printers are being redirected. And they do show up mapped correctly in the Terminal Server's printer diaglog:

Syntax: -r printer:'Apples CUPS printer name'='Terminal Services Printer name'

-r printer:'Officejet 7500_E910_670D7C'='HP Officejet 7500 E910'
-r printer:'HP Color_Laser_2840_143703'='HP Color LaserJet 2840 PCL 6'

When the users press the print button in Terminal Services, the Terminal Services session vanished. When you log back in, you resume just after the print command. And, no print out.

-T

Reply

Answer 2

Todd twice Author

Level 1

9 points

Mar 9, 2011 10:09 AM in response to Todd twice

Follow up. I have specifically isolated this problem to rdesktop ( http://www.rdesktop.org).

Workaround: install CoRD instead ( http://cord.sourceforge.net/). Prints perfectly, does not have the instabilities that the Microsoft RDP client for Windows has, and supports port redirection, unlike the Microsoft RDP client. It is also very easy to use.

Thank you for all the help,

-T

Reply

Answer 3

Dec 20, 2013 4:17 AM in response to Todd twice

For those who nees professional services around rdesktop there is a list of professionals on the rdesktop home page.

Reply