samba - Feb 2012 - APW and Windows 7

Hi,

I have set up my samba server as a print only server.  Nothing specific 
is wrong.  The print server is working but I have a couple of questions 
about using APW to install printer drivers and Windows 7.

Linux server: Centos 6
Samba version: 3.6.3 - Default install (./configure; make && make
install)

I did the usual,
net use \\myprinter\print$ /user:root

Browse to \\myprinter.  In my case a Windows 7 (32-bit) client shows 41 
print queues.  I then click on "View remote printers" which takes me
to
the place where I can actually install the drivers for each queue.  Now, 
I don't see 41 queues.  If I refresh the page I see 31 queues.  On other 
Win7 clients I see more or less queues.  My "temp" solution is to 
shutdown the samba server, remove the cache (rm -rf 
/usr/local/samba/var/locks), restart samba and all is well - for a while 
at least.  It's clearly not a solution, but it does work.  Can anyone 
tell me how this list is generated?

Also, once you've installed a printer driver via APW (i.e. right click 
print queue/Properties/Advanced/ New Driver), the name of your print 
queue gets changed to the name of the driver after successful 
installation.  I had the same problem on my old samba 3.0.33 samba 
server, so I know you can just refresh your window and then get 
Properties on the newly named queue and simply rename it.  What I 
haven't figured out (but have managed to work around) is that when you 
install the driver via APW, it presents a list of Manufacturers and 
Printer Models.  If I do the above from a Win7 (32-bit) client 
everything works as you would expect.  If however I do the above from a 
Win7 (64-bit) client I do not get presented with the 
Manufacturers/Models window.  Instead the "drivers" windows says
"No
drivers found for your device".  Does this have something to so with how 
the Windows Active Directory views \\myprinter as either a 32-bit or 
64-bit server when I joined it to the domain?

smb.conf for reference

[global]
    server string = CMS Print Server
    netbios name = MYPRINTER
    log file = /var/log/samba/%m.log
    max log size = 50
    log level = 5
    security = ads
    realm = MYDOM.COM
    workgroup = MYDOM
    domain master = no
    name resolve order = host
    socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
    winbind enum users = yes
    winbind enum groups = yes
    idmap config * : range = 1000000-1999999
    cups options = raw
    printing = cups
    printcap name = cups

[print$]
    comment = Printer Driver Download Area
    path = /usr/local/samba/drivers
    browseable = no
    guest ok = no
    read only = yes
    write list = root

[printers]
         comment = All Printers
         path = /var/spool/samba
         browseable = no
         guest ok = no
         writable = no
         printable = yes

Cheers,
Mike Vallabh

On Tue, Feb 7, 2012 at 6:07 PM, Mike Vallabh <mike at waikato.ac.nz>
wrote:
> ?What I haven't figured out (but have managed to work around) is that
when
> you install the driver via APW, it presents a list of Manufacturers and
> Printer Models. ?If I do the above from a Win7 (32-bit) client everything
> works as you would expect. ?If however I do the above from a Win7 (64-bit)
> client I do not get presented with the Manufacturers/Models window.
?Instead
> the "drivers" windows says "No drivers found for your
device". ?Does this
> have something to so with how the Windows Active Directory views
\\myprinter
> as either a 32-bit or 64-bit server when I joined it to the domain?
Didn't have a local 32 bit client to test with but I can duplicate the
APW problem with a raw queue and a 64 bit client. I normally would not
run across this as I use cupsaddsmb to add drivers but decided to
create a raw print queue and give it a shot. In following the
instructions at:
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#id2627720
which I've used successfully many times in the past (with older
versions of Samba and 32 bit clients) the APW does not provide a
driver list. If I ignore "Do not click on Yes! Instead, click on No in
the error dialog." and click on "Yes" the APW will present a
driver
list, but unless things have changed we know method that is incorrect.

Suggest you create a bug report for this.

Also it's been mentioned many times on this list that with a modern
distro the "socket options = " should not be specified. I don't
know
that distro but you may be hurting performance by using it.

Chris