On 02/12/2017 06:50 AM, Armin Novak wrote: >> Hi Armin, >> >> I started a "how to" for my records. And it does not work. >> What did I do wrong? >> >> Many thanks, >> -T >> >> >> DOESN'T WORK >> >> To map a printer on your local computer to a remote computer, use >> >> /printer:<device>,<driver> >> >> where >> <device> is the name of the printer in CUPS, >> >> and >> <driver> is the name of the driver used in CUPS
I this statement is inaccurate. The <driver> should be the name over on the Windows machine. >> >> >> For example: >> /printer:B4350,'HP LaserJet IIP' > Your syntax looks correct, but if that should work depends on a few > variables: > * First of which, did you use xfreerdp compiled from upstream or a > distribution provided package? Fedora and Scientific Linux are really out of date on xfreerdp. I requested that Red Hat please hurry up and update it: https://bugzilla.redhat.com/show_bug.cgi?id=1417798 In the mean time, I installed one of the "nightlies" freerdp-nightly-2.0-0+0~20170131033816.283~1.git58cc996.x86_64.rpm > Either way you need to check if it was compiled with -DWITH_CUPS=ON > CMake option. > > * Then you should try with just /printer which redirects all locally > attached CUPS printers to the remote machine. > Be aware that that may take a few seconds/minutes depending on driver > installation time of the remote machine. > If the printers show up on the remote machine you have a working > redirection. > > * You can retry with /printer:<cups name> only and look if the printer > is redirected properly with the default driver settings This worked: /printer:B4350 But this did not: /printer:B4350,"HP LaserJet IIP" Also tried with single quotes It transpires that this driver was not installed on the remote machine. For yuks, I redirected "Cups-PDF" and it did show up and it' did print, but who knows where it went. It did not appear on my desktop like it was suppose to. /printer:Cups-PDF > > * At last you can try fiddling with the driver settings. > You may need a few tries until you get the driver string correct (or > you're lucky) > > regards > Armin > Just as an aside, I switched from rdesktop to xfreerdp as rdesktop doesn't work when you turn off 3DES (sugar32 exploit) and enable RDP on a Windows 7 Remote Desktop server. https://github.com/rdesktop/rdesktop/issues/97 xfreerdp has no such issue. And I was also pleasantly surprised: xfreerdp is faster, especially on the shared drive. Thank you for all the help! -T Here is my updated How To: xfreerdp printer mapping: To map a printer on your local computer to a remote computer, use /printer:<device>,<driver> where <device> is the name of the printer in CUPS, and <driver> is the name of the driver used in the remote machine (Windows) use quotes around driver names with spaces To find the name of the Windows driver: --> open "Devices and Printers"and "add printer" --> go into the "manufacturer/printer" dialog box --> quote the exact name that appears on the printer you want. For example "HP LaserJet 2200 Series PCL 5" --> this may go without saying, but cancel out the add printer dialog For example: /printer:B4350 (For some reason it picks up the Post script driver but it works anyway.) This does not work: /printer:B4350,"HP LaserJet IIP" as this driver is not in Windows 7 But this does: /printer:B4350,"HP LaserJet 2200 Series PCL 5" -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I am Windows I am the Blue Screen of Death No one hears your screams ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
