I am running slack 14.2 on an intel box (hp p2-1124) and in general like this version. However, printing with CUPS was so hosed that after installing a printer via a web browser I was unable to print locally. I got some stderr to the effect that although the printer was marked as shared it wasn't published to the network. I solved this by deleting the printer in CUPS and installing it via the HP Device Manager. At this point samba is not behaving as it typically does. My age old, tried and true, smb.conf has one line the caused a fatal (?): "security = share". I changed this to security = user, created a user via adduser and smbpasswd and now I can print from a Mac Book Pro but the windows workstations (win 7 and win 10) cannot print. Win 10 (Dell Inspiron 15 / 7000) can see the printer, installed it, but printing fails with no error. Win 7 (old Toshiba Satellite) cannot connect at all. Does anyone have a smb.conf that is working (for printing) on a Slack64 14.2 box?
Here is what I have:
[global]
workgroup = SERVER_02
netbios name = LOCAL_PRINTER
security = user
printing = cups
printcap name = cups
hosts allow = 192.168.1. 192.168.2. 127.
load printers = yes

[printers]
comment = All Printers
path = /var/spool/samba
guest ok = yes
printable = yes
use client driver = yes
browseable = yes

testparm shows this:
/home/tag# testparm /etc/samba/smb.conf
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Loaded services file OK.
Server role: ROLE_STANDALONE

any help appreciated!

Hi,

Welcome to LQ & Slackware!

I suggest that you look at the sample; You can use this sample to configure your samba configuration in ;/etc/samba/smb.conf

Plus you can use some of this reference; http://docs.slackware.com/start?do=s...ulltext=Search

Hope this helps.
Have fun & enjoy!

Hi, thanks for the reply. Using the canned smb.conf - after some tweaks - I got the Win7 boxes printing but the two Win10 machines still could not print via Samba. Ultimately I abandoned that approach (using Samba) and used IPP via CUPS which works on all of the workstations. The problem is not on the Slack side of the equation. A few searches on google produced dozens of complaints indicating this is a known issue. And one not confined to Slackware - lots of Ubuntu ppl reported the same issue. Apparently Win10 is broken. Surprise, surprise...there was another problem with Win10 the other machines did not have: HP does not offer a driver download for the printer in question, when you select Windows 10 as the OS HP.com directs you to use the OS itself. The OS, of course, says it has no driver, pls insert disk (etc.). The solution was to connect each Win10 box, in turn, to the printer via a usb cable. Once the driver was installed the printer could be installed as a network device. Not exactly elegant as "solutions" go.

Thanks again for your help!

1 members found this post helpful.

I can't see which model of printer You have.
Maybe you can download driver by Windows Update when you adding printer in Windows 10.