samba - May 2006 - Samba Print Problem (Everything Looks Right)

I'm trying to get Samba to print with CUPS and the universal postscript 
driver.  I've followed the HOWTO at

http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/CUPS-printing.html

(a truely great work, IMO).  However, I cannot get a WinXP or Win2K 
machine to automatically install the driver when I double-click on the 
printer after browsing the share.

I've done everything up to and including step #10.  I can use 
"rpcclient" and see the driver installed.

The only difference I see is that "cupsaddsmb" (v1.2) put the driver 
(cups-windows v6.0) under the "3" subdirectory instead of the
"2" directory.

   titan:/var/log/samba$ rpcclient -Ubcwhite%secret -c 'getdriver Doyle'
share

[Windows NT x86]
Printer Driver Info 3:
         Version: [3]
         Driver Name: [Doyle]
         Architecture: [Windows NT x86]
         Driver Path: [\\SHARE\print$\W32X86\3\pscript5.dll]
         Datafile: [\\SHARE\print$\W32X86\3\Doyle.ppd]
         Configfile: [\\SHARE\print$\W32X86\3\ps5ui.dll]
         Helpfile: [\\SHARE\print$\W32X86\3\pscript.hlp]

         Dependentfiles: [\\SHARE\print$\W32X86\3\cupsui6.dll]
         Dependentfiles: [\\SHARE\print$\W32X86\3\cupsps6.dll]
         Dependentfiles: [\\SHARE\print$\W32X86\3\cups6.ini]
         Dependentfiles: [\\SHARE\print$\W32X86\3\pscript.ntf]
         Dependentfiles: [\\SHARE\print$\W32X86\3\pscript.hlp]
         Dependentfiles: [\\SHARE\print$\W32X86\3\ps5ui.dll]
         Dependentfiles: [\\SHARE\print$\W32X86\3\Doyle.ppd]
         Dependentfiles: [\\SHARE\print$\W32X86\3\pscript5.dll]

         Monitorname: []
         Defaultdatatype: [RAW]

Not only that, I've connected with smbclient and retrieve one of those 
files back to my hard drive (always as "bcwhite"), so I know they
exist
and are readable.

I've tried setting the sambal "log level" to 65535 and examing the
logs.
  I can't even see it making any reference to the "print$" share.

[print$]
	comment = Printer Drivers
	path = /etc/samba/drivers
	browseable = yes
	guest ok = no
	read only = yes
	write list = admin

Any ideas?  Thanks!

                                           Brian
                                  ( bcwhite@precidia.com )

-------------------------------------------------------------------------------
           Until we are first independent, we cannot be interdependent.

> (a truely great work, IMO).  However, I cannot get a WinXP or Win2K 
> machine to automatically install the driver when I double-click on the 
> printer after browsing the share.
Actually, now that I think about it...  Perhaps I'm not completely 
accurate with that statement.

In fact, when I double-click to open the printer, it does connect and 
give me a print-queue window.  It's only when I trying to bring up the 
properties for that printer that it tells me no driver is installed and 
asks if I want to search for one.

However, even if I say "no", the properties dialog does come up (just 
the print queue settings -- no printer driver options) and I can 
successfully print a test page.

So...  What am I missing?

                                           Brian
                                  ( bcwhite@precidia.com )

-------------------------------------------------------------------------------
           Until we are first independent, we cannot be interdependent.

> Try to put this:
> 
> 	use client driver = yes
> 
> it's work with me.
Unfortunately that option will (I assume) only work if you're using
client drivers, i.e. *not* the driver sitting on the Samba server.

From the manpage:
> This parameter MUST not be able enabled on a print share which has
> valid print driver installed on the Samba server.
Since the driver *is* installed on the server, I'm not sure what would
happen if you enabled it...  I'm guessing you'd have to manually choose
which driver you want to use on the client PC (e.g. the driver that
came with the printer) so you wouldn't end up using the CUPS driver.

Cheers,
Adam.

> I read your posts on samba mailing list.
> I have the same problem:
> I can print, but I can't open the printer properties page ("no
driver"
> message...).
> For me also, the drivers are read from samba server e written on 
> C:\WinNT\System32\spool\drivers\... (I have removed him in advance to 
> test this).
There was a bug in the cupssmbadd program that stripped all end-of-line 
characters during the conversion.  (Many thanks to Vincent Nicolas for 
catching this!)  See http://www.cups.org/str.php?L1750

                                           Brian
                                  ( bcwhite@precidia.com )

-------------------------------------------------------------------------------
               BREAKFAST.COM Halted...  Cereal Port Not Responding