I ment that I installed the printerhardware in the YAST2 Configurationutility which is unique to the SuSE Linux distibution. I guess other Distris. have other tools like this.
When I startet the hardwaredetection the system says:
OKI Data OKI 610ex on queu lp installed. Printingqueue lp (or something in that way).
After that I started my Webbrowser and used webmin to vreate the printing share. I told the system that I am printing with cups and chose a CUPS printer driver.
In the field spool directory I typed in the "/var/spool/lpd" directory.
After that I changed to the directory "/var/spool" and made a "chmod 777 lpd" (everything as root in the console, of course).
Restarted samba via webmin and everything worked.

The directory you are using does exist ?
(Different distrib. have sometimes different dirs.)
Did you do the chmod 777 on that dir ?

My Printershare looks now like the following lines:

[oki610ex]
printer = lp
printable = yes
writeable = no
public = yes
path = /var/spool/lp

Looks a littel bit different to yours. If you make some changes so that it is suiteable for your configuration it may work (hopefully).

Im using redhat. I can print locally of the Linux box. I will try the webmin config.

I will let you know what happens!

Paul

ARGGGG! It still isnt working... even if I configure my print system to be LPD, i can print locally but not remotely! Does any one have any idea about a LPD client for windows that is free?

Don´t get me wrong, I still use CUPS on the Linux System.

But if it still doesn´t work with the chmod 777 you shurely made, I don´t know, either. Sorry.

ok, i'll have to do some more searching... thanx for you help anyway

Hey pnh73,

I just noticed you did not have the printcap name and load printers options in the Global share.

Add the following in the Global share:

hmm, this could be my solution...

let me see

ok here is my smb.conf at the moment:


[global]
workgroup = MSHOME
netbios name = WEBSERVER
server string = RH8 Server
security = SHARE
null passwords = Yes
obey pam restrictions = Yes
log file = /var/log/samba/%m.log
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printing = lprng
printcap name = /etc/printcap
load printers = yes

[laser]
path = /var/spool/lpd/ml-4500
guest ok = Yes
printable = Yes
public = yes

is this correct?

Im still not having any luck...

Can you post your smb.conf file once again.

Also, what version of RedHat are you using?
(In RedHat 7.3 and below, Samba does not support CUPS).

Can you print locally ?



P.S. consider adding the name and version of your distribution to your profile.

I am using Red Hat 8, and yes I can print locally...

You forgot to post your smb.conf.

Or

I will use the one right on top

Sorry . Here you go:

[global]
workgroup = MSHOME
netbios name = WEBSERVER
server string = RH8 Server
security = SHARE
null passwords = Yes
log file = /var/log/samba/%m.log
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printing = lprng

[laser]
path = /var/spool/lpd/ml-4500
guest ok = Yes
printable = Yes
printer name = lp

[global]
workgroup = MSHOME
netbios name = WEBSERVER
server string = RH8 Server

security = user
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*

log file = /var/log/samba/%m.log
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

printcap name = /etc/printcap
load printers = yes
printing = lprng


[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
guest ok = yes
writable = no
printable = yes


If this doesn't work, then it is possible that your guest user does not have permission to print.

You can:
Create a Linux user and then a Samba user (smbpasswd -a <username>)
OR
There is a file called smbusers, just re-assign the guest user to a valid Linux user.

Someone much earlier had the answer, but I think it got lost in the noise. Try the following under the appropriate [printer] section:

use client driver = yes

this stops the "unable to connect..." messsages

Before I added it, I could print to the samba printer from windows but I couldn't see any info about the printer itself. Now it works fine.