This is what I do:- /usr/sbin/lpadmin -p samsung -v /tmp/SUNWut/units/IEEE802.00144f######/dev/printers/########## /usr/bin/enable samsung /usr/sbin/accept samsung Printer driver needs installing on the terminal server and in uttsc -r printer:"samsung"="Samsung ML-2250 Series"
However usb printing seems to be extremely temperamental, working fine one minute & not the next. Printer shows up on the terminal server but the print jobs seem to go into a black hole. Network printing from the terminal server is 100 times better solution if it fits your enviroment. Unfortuantly I wanted to print from home using the sunray vpn & a locally attached usb printer :( -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Benoit Audet Sent: 11 March 2008 13:40 To: SunRay-Users mailing list Subject: [SunRay-Users] Using printers with uttsc not working Hi fellow Sun Ray Gods! (I thought it would be a good start calling you all 'Sun Ray Gods' ;-)) One of my clients have in place a Sun Fire x4200 with Solaris 10 8/07, with SRSS 4.0 and uttsc 2.0.23. Following patches has been installed on the servers: 127554-01 and 127554-01. AFAIK, everything seem to be working flawlessly. We installed some HP printers on the server, using CUPS, and when printing from Solaris (let's say from a JDS session), it prints perfectly. We as well put in place the "Follow Me Printing" 0.3 and it works just perfectly. What we want to do is to be able to "push" de print queue to through RDP with "uttsc" to be able to use the same printer from Windows Terminal Server (which is a Windows 2003 Server), but this is where we have problem. We did some tests using the uttsc command options: '-r printer:SR-Default' (without the quotes...). Windows seems to see it, but use a generic driver, instead of the good one. So we put '-r printer:SR-Default="HP LaserJet 8150"' (using only the double-quotes for the driver name - and this is the exact driver used if we try to install this printer in Windows 2003 (it works well this way on Windows 2003)): the printer seems to be seen perfectly, with the good driver, but again, we're unable to print yet. Finally, we decided to test "manually", without the Follow-Me-Printing option. In a terminal window, we put this command in a shell: $ uttsc -r printer:exact-print-queue-name="HP LaserJet 8150" -m ip-of-the-win-server but we get the same result. Is there anything I should do to be able to "push" the printer through RDP with uttsc that I am missing? Related to the documentation, it should do the trick... ...and I push a good driver to Windows, a driver that works for *this* printer when installed localy (and of course the driver is on the Windows 2003 Server). Thanks in advance!! Ben Audet _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
