RE: [Samba] Problems with printers
I am using cups, using the cups web interface to add printers, today I added 2 more printers. They do not show up in samba, I have restarted cups, smb nmb, everything except the machine itself. By, They do not show up in samba, is that from the Samba or Windows client? Sometimes Windows take a bit to notice, for best results try: smbclient -L localhost -U [user] and see if they show up. Do you have a [printers] share and a load printers = Yes? If not you need to add print share explicitly in smb.conf. ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems with printers
Rob, Sorry. Not enough information. What is in your smb.conf? Have are the printers set up? Are you using Raw interface on CUPS? - If so, did you enable application/octet-stream in CUPS /etc/cups/mime* Was samba-3.0.1 compiled and linked against the cups-devel libraries? - to find out run: smbd -b | grep CUPS If you have CUPS, you should not be using /etc/printcap at all. Samba talks directly to CUPS via a direct printing API. - John T. On Mon, 22 Dec 2003, Rob Sell wrote: I have samba 3.0.1 running and have successfully set it up to be a print spooler, which is working great, until I tried to add more than 5 printers. I am using cups, using the cups web interface to add printers, today I added 2 more printers. They do not show up in samba, I have restarted cups, smb nmb, everything except the machine itself. Samba is set to load /etc/printcap printers, my /etc/printcap is as follows. # This file was automatically generated by cupsd(8) from the # /etc/cups/printers.conf file. All changes to this file # will be lost. 7th_Dock_Laser: Edgeley_Inkjet: Edgeley_Laser: Eng_Laser: Eng_Laser_Color: Front_Office_Big_Laser: Front_Office_Laser: Michigan_Plotter: Any ideas why only the 1st 5 printers show up in samba? Rob -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Problems with printers
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, December 22, 2003 12:14 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [Samba] Problems with printers
I am using cups, using the cups web interface to add
printers, today I added 2 more printers. They do not
show up in samba, I have restarted cups, smb
nmb, everything except the machine itself.
By, They do not show up in samba, is that from the
Samba or Windows client? Sometimes Windows take a bit
to notice, for best results try: smbclient -L localhost
-U [user] and see if they show up.
Do you have a [printers] share and a load printers = Yes?
If not you need to add print share explicitly in smb.conf.
~ Daniel
-
Dan,
They do not show up using smbclient either. I have a printers share, and I
have load printers set to yes.
-
John,
Samba was compiled but not linked against cups. I didn't have the mime stuff
set in cups, I do now. But why does samba pick up my 5 printers without
being linked to cups?
Below is my smb.conf
# Samba config file created using SWAT
# from 192.1.1.100 (192.1.1.100)
# Date: 2003/12/22 13:05:38
# Global parameters
[global]
workgroup = DAC
interfaces = 192.1.1.60/255.255.255.0
security = DOMAIN
map to guest = Bad User
password server = dc
log level = 1
syslog = 0
time server = Yes
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
os level = 2
preferred master = No
local master = No
domain master = No
ldap ssl = no
admin users = robs
printer admin = robs
printing = cups
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
[homes]
comment = Home Directories
valid users = %S
read only = No
create mask = 0640
directory mask = 0750
browseable = No
[tmp]
comment = Temp Directories
path = /tmp/
read only = No
guest ok = Yes
[cgi]
path = /srv/www/cgi-bin/
read only = No
guest ok = Yes
[www]
path = /srv/www/htdocs/
read only = No
guest ok = Yes
[printers]
comment = All Printers
path = /var/tmp
printer admin = root, robs
create mask = 0600
guest ok = Yes
printable = Yes
[print$]
comment = Printer Drivers
path = /usr/local/samba/var/locks/printing
write list = @ntadmin, root, robs
force group = ntadmin
read only = No
create mask = 0664
directory mask = 0775
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Problems with printers
On Mon, 22 Dec 2003, Rob Sell wrote:
Dan,
They do not show up using smbclient either. I have a printers share, and I
have load printers set to yes.
-
John,
Samba was compiled but not linked against cups. I didn't have the mime stuff
set in cups, I do now. But why does samba pick up my 5 printers without
being linked to cups?
If samba was not linked with the cups-devel libraries, then do NOT set
printing = cups that will break things. You should either compile and
link against the cups-devel libraries, or else just use printing = bsd
or printing = sysv, depending on which commands you want to use.
If you use printing = sysv, then set printcap = lpstat -t.
Note: Only use printing = sysv if you have LPRng installed. This will
not work if your systems does not support the ATT command tools (lp,
lpstat).
- John T.
Below is my smb.conf
# Samba config file created using SWAT
# from 192.1.1.100 (192.1.1.100)
# Date: 2003/12/22 13:05:38
# Global parameters
[global]
workgroup = DAC
interfaces = 192.1.1.60/255.255.255.0
security = DOMAIN
map to guest = Bad User
password server = dc
log level = 1
syslog = 0
time server = Yes
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
os level = 2
preferred master = No
local master = No
domain master = No
ldap ssl = no
admin users = robs
printer admin = robs
printing = cups
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
...
[printers]
comment = All Printers
path = /var/tmp
printer admin = root, robs
create mask = 0600
guest ok = Yes
printable = Yes
[print$]
comment = Printer Drivers
path = /usr/local/samba/var/locks/printing
write list = @ntadmin, root, robs
force group = ntadmin
read only = No
create mask = 0664
directory mask = 0775
--
John H Terpstra
Email: [EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Problems with printers
John Terpstra wrote: ...or else just use printing = bsd or printing = sysv, depending on which commands you want to use. If you use printing = sysv, then set printcap = lpstat -t. Note: Only use printing = sysv if you have LPRng installed. This will not work if your systems does not support the ATT command tools (lp, lpstat). So I'm running a job control application on top of Solaris. Am I better off using printing = sysv or printing = bsd? (The vendor actually suggested using Samba as my front end!) -wde -- Will Enestvedt UNIX System Administrator Johnson Wales University -- Providence, RI -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
