Have just recently got my Panasonic K-XP4400 to work
with Slackware Linux 9.0 after following instructions
for LPD-O-Matic on linuxprinting.org.

Since I've got Samba running also, I thought I'd try to
print from Win2k to Linux. Followed setup as best I could
from HOW-TO but alas, it doesn't work. The samba log
file (the one with the windows machine suffix) reveals the
following:

[2003/04/11 10:28:56, 0] smbd/service.c:make_connection(599)
amdk7 (192.168.0.1) Can't change directory to /var/spool/lpd/kxp4410 (Permission denied)
[2003/04/11 10:28:56, 0] smbd/service.c:make_connection(599)
amdk7 (192.168.0.1) Can't change directory to /var/spool/lpd/kxp4410 (Permission denied)
[2003/04/11 10:28:56, 0] smbd/service.c:make_connection(599)
amdk7 (192.168.0.1) Can't change directory to /var/spool/lpd/kxp4410 (Permission denied)
[2003/04/11 10:28:56, 0] smbd/service.c:make_connection(599)
amdk7 (192.168.0.1) Can't change directory to /var/spool/lpd/kxp4410 (Permission denied)
[2003/04/11 10:28:56, 0] smbd/service.c:make_connection(599)
amdk7 (192.168.0.1) Can't change directory to /var/spool/lpd/kxp4410 (Permission denied)
[2003/04/11 10:28:56, 0] printing/printing.c:print_job_start(1045)
print_job_start: insufficient permissions to open spool file /var/spool/lpd/kxp4410/smbprn.000005.RLm9KH.

When I first got this message I immediately entered
'chmod 777 kxp4410' so the spool directory was world
writeable. This had no effect.

I do have the Win2k user properly setup in smbpasswd
(I told you Samba's working fine otherwise) and I've even
tried to change the 'security = server' setting to 'user' in
smb.conf; nothing seems to work.

In smb.conf, the printer is set up like this:

[global]
printcap name = /etc/foomatic
load printers = yes


[pkxp4400]
security = server
path = /var/spool/lpd/kxp4410
printer name = KXP-4400
writable = yes
public = yes
printable = yes
print command = lpr -r -h -Pkxp4410 %p %s


Can anyone suggest what may be wrong?

Try changing your spool to /tmp. It works for me. Make sure to restart Samba.

Actually this got a bit more complicated.

First of all, I couldn't really use the LPD-O-Matic
setup since I was printing from Windows using
a windows printer driver. Reading a little farther
into the HOW-TO, it appeared that I was going
to have to use the setup for raw printing:

raw:\
:rw:sh: \
:lp=/dev/lp0 \
:sd=/var/spool/lpd/raw \

so as not to filter the print output at all. In fact,
you have to set the print command in smb.conf
to send only binary output:

print command = lpr -b -P%p %s

I thought I had finally figured it out, except when
printing from windows, it took a long time for the
print command to finish and the samba.%m log file
kept giving me things like:

[2003/04/11 15:19:48, 0] smbd/service.c:make_connection(252)
amdk7 (192.168.0.1) couldn't find service ::{2227a280-3aea-1069-a2de-08002b30309d}

The CLSID appears to represent the 'Printers' info directory
for control panel. Nothing on the web suggested a fix for
this. I couldn't think of anything else to do, so I looked at
the [printers] section of the default smb.conf and the only
line I hadn't uncommented was 'guest ok = yes'.

When I uncommented this line, printing from windows
worked just fine.

I don't really understand why I need this, since all required
users and passwords are included in smbpasswd and
Samba otherwise works just fine. Must be something on
the windows side.

When I began using Linux, I was happy at the seemingly
endless and in-depth documentation that accompanied
my distro. Sadly, I realize now that it has caused me to
waste endless amounts of time running up blind alleys.

I hope it can only get better.

If you're not learning, you're dying. I guess CUPS doesn't support your printer?

CUPS is next.

Startup scripts actually want to start CUPS
first if it is installed. It's not.

I think the beta version of Slack 9 contained the
CUPS distribution, but this release does not. Or
I just can't find it.