After i changed the System to deliver Printers and the Printer Config from Samba-Server, Printer change requests are (depending on Printer Driver) can be very slow.
Affected Versions are at least samba 3.020 with cups 1.1.23 and samba 3.026a with cups 1.2.11.
If i change the Printer in a Windows (XP or W2K) Application (notepad, word, OO) to something like Apple Postscript or Epson 9 dot or 24 dot, reaction follows immediately.
But if i change the Printer to maybe a Kyocera FS 1030 (KX-Driver) or Canon IP5200, reaction needs some seconds (on a AMD 5200 double core, Server and Client, around 2 Seconds, on the old Server, AMD 3000, around 5 to 15 Seconds).
Also Word needs this as Start-Time, if maybe the Kyocera is DefaultPrinter.
A tcpdump of the Conversation between Client and Server for only one Printer Change to Kyocera KX-Driver shows around 4050 lines (= packets), the cups-access-log shows around 1050 lines, containing:
localhost - - [01/Oct/2007:00:50:13 +0200] "POST / HTTP/1.1" 200 189 Get-Printer-Attributes successful-ok
and every 6th line contains instead of successful-ok client-error-not-found.
So, because the AMD 50000 is not available on normal ways (without a Time Machine), i'd like to request for some Caching of these Cups-Requests or (so far i can see, Printer Configs are stored in samba) maybe the Cups-Request are not neccessary, what should speed up Printer Change in this centralized Printer Configuration by magnitudes:-)
I hope to have declared that all clearly enough, if not, please send me a mail.
I have the same problem with HP LaserJet 3000 printer.
this is the log of samba process: https://mail.comune.trezzosulladda.mi.it/log.samba-printer.gz
my samba version is 3.0.26a
Same problem for one month with version 3.0.13!
Very slow printings and a long delay to show printers properties.
Printer models : Kyocera, Lexmark and HP.
What is that hell ?
domain server samba version is samba-3.0.23d-2.6mdv2007.0
cups server samba version is samba-3.0.13-2.1.102mdk
Sorry, it was a samba configuration problem.
The cups server has some authentification problems
which slowed the communication between cups
and printers. It works fine now.
Thanks for the update. CLosing now.