Hello, dear colleagues using SAMBA.
Who could possibly tell me what I am missing in order to make my SAMBA printer
share visible on the windows network( i.e., accessing it from a MS Windows
machine's explorer, for example )?
It is SAMBA 3.0.23 on Linux 2.4.33 machine(originally RedHat 7.3. based, but
so much upgraded, even to GLIBC-2.3.6).
here are the linked libraries:
================================#ldd /usr/local/samba/sbin/smbd
libcups.so.2 => /usr/lib/libcups.so.2 (0x40023000)
libpthread.so.0 => /lib/libpthread.so.0 (0x40056000)
libm.so.6 => /lib/libm.so.6 (0x400a8000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x400cb000)
libresolv.so.2 => /lib/libresolv.so.2 (0x400f8000)
libnsl.so.1 => /lib/libnsl.so.1 (0x40109000)
libdl.so.2 => /lib/libdl.so.2 (0x4011d000)
libpopt.so.0 => /usr/lib/libpopt.so.0 (0x40121000)
libc.so.6 => /lib/libc.so.6 (0x40128000)
libpthread.so.20 => /usr/lib/libpthre
And here, at last, my smb.conf:
[global]
log file = /usr/local/samba/var/log.%m
load printers = yes
socket options = TCP_NODELAY
username map = /etc/samba/user.map
interfaces = 192.168.0.1/27
domain master = yes
null passwords = yes
public = yes
wins support = true
guest account = nobody
dns proxy = no
netbios name = Samba
netbios aliases = Samba
printing = cups
server string = Samba
default = global
local master = yes
workgroup = QUBICA
os level = 65
printcap name = cups
security = share
max log size = 50
[Server_files]
map archive = no
writeable = yes
path = /mnt/nfs
hide dot files = no
public = yes
case sensitive = yes
[printers]
postscript = yes
printer = hp_LaserJet_3015
lpq command = lpstat -o %p
browseable = yes
printable = yes
print command = lpr -P %p -o raw %s -r
comment = All Printers
lprm command = cancel %p-%j
printer admin = root
======================My printer here is installed via HPLIP, CUPS is running
OK, everything's OK,
except that I can't see the printer through windows network browsing,
neither from linux, nor from windows machines. Of course, I did the RTFM
search and corrected everything accordingly, but still. The [Server_files]
share IS visible, the [printers] is NOT.
ANY IDEAS?
THANKS IN ADVANCE FOR YOUR KIND SUPPORT AND YOUR PRECIOUS TIME!
Kostya
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.samba.org/archive/samba/attachments/20060921/091ed65d/attachment.bin
Hi, And if you add something like that into the smb.conf: [global] disable spoolss = yes [print$] comment = Printer Drivers path = /var/lib/samba/printers [hp2300] path = /tmp writeable = yes browseable = yes printable = yes guest ok = yes what happens? -- Bruno On 9/21/06, Kostya Berger <bergerkos@yahoo.co.uk> wrote:> Hello, dear colleagues using SAMBA. > > Who could possibly tell me what I am missing in order to make my SAMBA printer > share visible on the windows network( i.e., accessing it from a MS Windows > machine's explorer, for example )? > It is SAMBA 3.0.23 on Linux 2.4.33 machine(originally RedHat 7.3. based, but > so much upgraded, even to GLIBC-2.3.6). > here are the linked libraries: > ================================> #ldd /usr/local/samba/sbin/smbd > libcups.so.2 => /usr/lib/libcups.so.2 (0x40023000) > libpthread.so.0 => /lib/libpthread.so.0 (0x40056000) > libm.so.6 => /lib/libm.so.6 (0x400a8000) > libcrypt.so.1 => /lib/libcrypt.so.1 (0x400cb000) > libresolv.so.2 => /lib/libresolv.so.2 (0x400f8000) > libnsl.so.1 => /lib/libnsl.so.1 (0x40109000) > libdl.so.2 => /lib/libdl.so.2 (0x4011d000) > libpopt.so.0 => /usr/lib/libpopt.so.0 (0x40121000) > libc.so.6 => /lib/libc.so.6 (0x40128000) > libpthread.so.20 => /usr/lib/libpthre > And here, at last, my smb.conf: > [global] > log file = /usr/local/samba/var/log.%m > load printers = yes > socket options = TCP_NODELAY > username map = /etc/samba/user.map > interfaces = 192.168.0.1/27 > domain master = yes > null passwords = yes > public = yes > wins support = true > guest account = nobody > dns proxy = no > netbios name = Samba > netbios aliases = Samba > printing = cups > server string = Samba > default = global > local master = yes > workgroup = QUBICA > os level = 65 > printcap name = cups > security = share > max log size = 50 > > [Server_files] > map archive = no > writeable = yes > path = /mnt/nfs > hide dot files = no > public = yes > case sensitive = yes > > [printers] > postscript = yes > printer = hp_LaserJet_3015 > lpq command = lpstat -o %p > browseable = yes > printable = yes > print command = lpr -P %p -o raw %s -r > comment = All Printers > lprm command = cancel %p-%j > printer admin = root > ======================> My printer here is installed via HPLIP, CUPS is running OK, everything's OK, > except that I can't see the printer through windows network browsing, > neither from linux, nor from windows machines. Of course, I did the RTFM > search and corrected everything accordingly, but still. The [Server_files] > share IS visible, the [printers] is NOT. > > ANY IDEAS? > > THANKS IN ADVANCE FOR YOUR KIND SUPPORT AND YOUR PRECIOUS TIME! > Kostya > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > > >
Well, it seems, I've got it at last ... But, my, it's far from being easy, to tell ye the truth! Perhaps, I didn't really need to install HPLIP? And Foomatic? As a matter of fact, I had all sorts of problems mentioned in various UNANSWERED mailing list threads while trying to organize driver upload to MS Win2000 hosts; ended up in "Quota limit reached" and no printing even with super-SUPER-user privilleges. Wanna share some solutions, you know; if any of you guys are being tormented by any of these problems, here is how I did it: 1)If your printer share is not visible in Konqueror's smb:// view, it still can be visible from Windows explorer; nothing to worry about. 2)installing drivers for upload via "rpcclient -adddriver" command ended up(after all) first in WERR_BADFILE, then in WERR_UNKNOWN_PRINTER_DRIVER and nothing could be done about the latter one. 3)Thankfully, for CUPS we have "cupsaddsmb -U root ..." command to install the uploadable Windows drivers; just a bit stumbled at "NT_STATUS_LOGON_FAILURE", which taught me a valuable lesson: it won't heart to get yourself a SAMBA password when working with SAMBA! Even if you think you are a "root" and even have the root password... 4)When at last all was set, the drivers installed and EVEN uploaded on-demand(!!!) , the nasty thing refused to print: "ERROR: Quota limit reached". Such message appeared at localhost:631 (print test page). After about 2 hours of ... I noticed that "lpstat -p" didn't really show my printer, to which the last week of my life was entirely dedicated! So, a very simple operation of reinstalling the printer via web-interface (setting /dev/lp0 instead of /dev/parport0) did it. What do I care now, if the driver upload (alas!) stopped working after that? Even all the Win2000 machines (not even talking about the XP monsters) now can print via SAMBA, and my SUSE-10.1 laptop -- via CUPS!!!!! JUST TELL ME NOW, PLEASE, WHAT ARE THE ADVANTAGES OF USING CUPS? It seems, things are easier printing from some Win2000 host. Where can I read about the advantages of CUPS in a short and understandable way? I mean, I beleive in CUPS, just how can I explain it to others? Thank everyone for help and patience, sorry for taking so much space. Kostya On Sunday 24 September 2006 22:43, Kostya Berger wrote: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20060926/eaf1e540/attachment.bin