I found a discussion of this "problem" in the Samba documentation:
http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#id390974
Basically, we were setting up double sided printing in the via:
Start->Printers and Faxes->right-click printer->Properties->General
tab->Printing Preferences...
And it was working!
We should have been setting it up via:
Start->Printers and Faxes->right-click printer->Properties->Advanced
tab->Printing Defaults...
Something about the new Samba release forced this change.
Owen Beckley wrote:
What is the best way to back out the samba update that came through on
11/16?
Owen Beckley wrote:
My users just noticed today that the "double-sided" setting for their
printers will no longer stay saved. All of our printers are spooled
using cups through samba on SL 4.5 from WinXP clients.
There was a samba update on 11/16 to version 3.0.25b-1.el4.2. Has
anyone else noticed any problems.
Here are some more details...
On WinXP, if you go into Start->"Printers and Faxes", right-click on a
printer, and choose "Properties" you're provided a dialog that lets
you set the default properties of your printer for all applications.
For most 2-sided capable printers, you need to first tell the driver
that you have a duplex (double-sided) option installed. Then you go
the the "General" tab, click on "Printing Preferences" and on a new
dialog, you say that you want printing on both sides. If I click on
"Flip on Long Edge" the dialog will show that two-sided printing is
now set up. Clicking on "Apply" and the "OK" eventually gets me out of
the dialogs. If I go back into "Properties" for that same printer
again, the "Flip on Long Edge" option is no longer chosen and the
setting is back on "None".
At first I wanted to blame a WinXP update for the problem. To show
whether or not WinXP was at fault, I added one of the printers
"directly" to a TCP port bypassing the samba (or any other) server.
When I change the printing preferences on that printer, the "Flip on
Long Edge" attribute stays selected.
Any help would be truly appreciated.
--
Owen Beckley
Clarity Communication Systems
