Hi,
I'm a bit new to the whole Samba printing thing and need some help. I am
running Caldera OpenLinux with Samba 2.2.4 and CUPS 1.1.10. I have
successfully managed to upload print drivers to the Samba server from a
Windows NT client. I have then managed to add the printers to several
windows clients without downloading drivers to them. This appeared to work
fine, with excellent integration into our network.
However, upon reboot of the Caldera server I have found that windows clients
who need to add the printers now no longer recognise that the printers have
drivers associated with them. This is pretty strange, as the drivers still
sit in the /var/spool/samba directory!!! Can anyone help with this problem?
Below is a copy of my smb.conf (with senxitive information removed):
# Global parameters
[global]
workgroup =
server string = Caldera Samba Server
security = DOMAIN
encrypt passwords = Yes
password server =
log file = /var/log/samba/%m.log
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = No
wins server =
winbind uid = 10000-20000
winbind gid = 10000-20000
winbind separator = +
printing = cups
printcap = cups
load printers = yes
[print$]
comment = Printer Drivers
path = /var/spool/samba
browseable = yes
guest ok = no
read only = yes
write list = (username is in here)
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
public = yes
guest ok = yes
writeable = no
printable = yes
printer admin = (username is in here)
Thanks very much for your time!
Mark Vodden
Don't know if this will help with your problem but I would change your printer driver path to someplace other than the print spool directory. Say '/etc/samba/drivers' or something else. See section 7.6 of the Samba Howto document. On Mon, 2002-08-05 at 09:40, Mark Vodden wrote:> Hi, > > I'm a bit new to the whole Samba printing thing and need some help. I am > running Caldera OpenLinux with Samba 2.2.4 and CUPS 1.1.10. I have > successfully managed to upload print drivers to the Samba server from a > Windows NT client. I have then managed to add the printers to several > windows clients without downloading drivers to them. This appeared to work > fine, with excellent integration into our network. > > However, upon reboot of the Caldera server I have found that windows clients > who need to add the printers now no longer recognise that the printers have > drivers associated with them. This is pretty strange, as the drivers still > sit in the /var/spool/samba directory!!! Can anyone help with this problem? > > Below is a copy of my smb.conf (with senxitive information removed): > > # Global parameters > [global] > workgroup = > server string = Caldera Samba Server > security = DOMAIN > encrypt passwords = Yes > password server = > log file = /var/log/samba/%m.log > max log size = 0 > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > dns proxy = No > wins server = > winbind uid = 10000-20000 > winbind gid = 10000-20000 > winbind separator = + > printing = cups > printcap = cups > load printers = yes > > [print$] > comment = Printer Drivers > path = /var/spool/samba > browseable = yes > guest ok = no > read only = yes > write list = (username is in here) > > [printers] > comment = All Printers > path = /var/spool/samba > browseable = no > public = yes > guest ok = yes > writeable = no > printable = yes > printer admin = (username is in here) > > Thanks very much for your time! > > > Mark Vodden > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba-- Curt Koehn ITS Operations System Analyst Bethel College St. Paul, MN 55112 (651) 635-8618
Hi again,
Regarding problems of Samba losing association with print drivers after a
reboot, I have found out the following:
I can query the tdb database files in my /var/lock/samba.d with rpcclient
(except the messages.tdb, does anyone know how to query this?). After I
have added one driver to the machine I can get the following output:
[root@caldera init.d]# rpcclient -U EALINGD+sysmv caldera -c
"enumdrivers"
Password:
cmd = enumdrivers
[Windows NT x86]
Printer Driver Info 1:
Driver Name: [HP LaserJet 4000 Series PS]
This results in the being able to add this printer using the Add Printer
Wizard on windoze clients. Which is as should happen. When I reboot the
server this happens:
[root@caldera init.d]# rpcclient -U EALINGD+sysmv caldera -c
"enumdrivers"
Password:
cmd = enumdrivers
[root@caldera init.d]#
Indicating there is no longer an association to that driver (and all others)
in the database, despite the drivers still being located on the driver
directory on the machine. If I restart Samba and Cups it still works fine,
only on reboot does it do this..... Any ideas?
Thanks very much people,
Mark.
> -----Original Message-----
> From: Mark Vodden
> Sent: 05 August 2002 15:41
> To: samba@lists.samba.org
> Cc: Chris Denton
> Subject: Samba Printing with CUPS
>
> Hi,
>
> I'm a bit new to the whole Samba printing thing and need some help. I
am
> running Caldera OpenLinux with Samba 2.2.4 and CUPS 1.1.10. I have
> successfully managed to upload print drivers to the Samba server from a
> Windows NT client. I have then managed to add the printers to several
> windows clients without downloading drivers to them. This appeared to
> work fine, with excellent integration into our network.
>
> However, upon reboot of the Caldera server I have found that windows
> clients who need to add the printers now no longer recognise that the
> printers have drivers associated with them. This is pretty strange, as
> the drivers still sit in the /var/spool/samba directory!!! Can anyone
> help with this problem?
>
> Below is a copy of my smb.conf (with senxitive information removed):
>
> # Global parameters
> [global]
> workgroup =
> server string = Caldera Samba Server
> security = DOMAIN
> encrypt passwords = Yes
> password server =
> log file = /var/log/samba/%m.log
> max log size = 0
> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
> dns proxy = No
> wins server =
> winbind uid = 10000-20000
> winbind gid = 10000-20000
> winbind separator = +
> printing = cups
> printcap = cups
> load printers = yes
>
> [print$]
> comment = Printer Drivers
> path = /var/spool/samba
> browseable = yes
> guest ok = no
> read only = yes
> write list = (username is in here)
>
> [printers]
> comment = All Printers
> path = /var/spool/samba
> browseable = no
> public = yes
> guest ok = yes
> writeable = no
> printable = yes
> printer admin = (username is in here)
>
> Thanks very much for your time!
>
>
> Mark Vodden
>
>