Hi Corey, I was just playing with this, using the instructions in the 3.0/HEAD howto for manual driver addition using rpcclient.
It also works for 2.2.8a. However, the one caveat I have found is that I can't (with 2.2.8a or 3.0b3) get the properties for the printer set so new clients get the right printer configuration, but at least the printer drivers are auto-installed.[*] Mark [*] Despite much cursing with 'printer admin', turning on and off guest accesses, etc etc. The closest I got was being able to change the properties pages after adding the printer (rather than having greyed out choices), but they wouldn't apply back to the samba server. Setup is a workgroup with a mix of W9x and 2K machines and a central print server running samba 3.0b3 upgraded from 2.2.8a. Are there any known gotchas with the passdb backends during a migration ? It seemed the ACLs on the printers were everyone print, samba-server\root full control, but I couldn't find any way to change that, despite much experimentation with 'net use' and the acl options in smb.conf. On Wed, 2003-07-30 at 22:40, Corey Hart wrote: > Ok..I can not get any windows clients to see the printer drivers associated with > each printer on my Samba Server. I am running RH 8.0 and Samba 2.2.8a. I am > trying to utilize CUPS Printing + ESP Print Pro. Here is my smb.conf > > [global] > workgroup = STEDS > netbios name = EDSHARE > server string = Steds File Share > interfaces = 209.99.108.82 127.0.0.1 > bind interfaces only = Yes > encrypt passwords = Yes > log level = 2 > time server = Yes > socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 > printcap name = cups > add user script = /usr/sbin/useradd -d /dev/null -g 527 -c Machine -s > /bin/false -M %u > logon script = logon.bat > logon path = \\%N\prifiles\%u > domain logons = Yes > os level = 255 > preferred master = Yes > domain master = Yes > wins support = Yes > ldap server = ldap1.stedwards.edu > ldap port = 9111 > ldap suffix = dc=stedwards,dc=edu > ldap admin dn = cn=Manager,dc=stedwards,dc=edu > ldap ssl = no > invalid users = bin daemon sys man postfix mail ftp > admin users = root coreyh > printing = cups > load printers = yes > printcap name = cups > > > [printers] > comment = All Printers > path = /var/spool/samba > browsable = No > public = Yes > guest ok = Yes > writeable = No > printable = Yes > printer admin = root coreyh > > [print$] > comment = Printer Drivers > path = /usr/local/drivers > browsable = No > guest ok = No > read only = yes > write list = root coreyh > > Now in ESP Print I have all my printers setup and I run the Export Command to > export my Printers to Samba. The printers show up in samba, you can select the > printers and them to your local desktop (XP, 95/98 verified) but they do not have > a server side driver associated with them. How in the world do I get a driver > associated with a printer in samba so that my clients do not have to install a > driver themselves? > > > > -- > ---- > Corey Hart > Systems/Security Analyst > St. Edward's University > [EMAIL PROTECTED] > 512/428-1038 - voice > 512/448-8492 - fax > 512/470-8462 - cell -- Mark Cooke <[EMAIL PROTECTED]> -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
