On Wednesday, June 25, 2003, at 11:51 AM, Dave Reed wrote:
On Wednesday 25 June 2003 09:47, Jorge Boscán Etura wrote:Hi
I have a little question about a shared printer i have using the configuration below and the problems is that the client sends the job but it does not print at all, the printer works well in Linux in both cups or lprng, if i switch to lprng it works, but with cups doesn't
thanks in advance..
# Global parameters [global] workgroup = home server string = Linux Rules! security = server encrypt passwords = Yes obey pam restrictions = Yes password server = passwd program = /usr/bin/passwd %u passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully* unix password sync = Yes log file = /var/log/samba/%m.log max log size = 0 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 load printers = Yes os level = 64 preferred master = No local master = Yes domain master = Yes dns proxy = No wins server = 192.168.166.1
[homes] comment = Home Directories valid users = %S read only = No create mask = 0664 directory mask = 0775 browseable = No
[hp] path = /tmp printable = Yes printing = cups
I'm guessing your client is a MS Windows machine and the printer is connected to a Linux machine running samba. If so, here's how I've got it working. Here's the relevant lines from the smb.conf file:
# if you want to automatically load your printer list rather # than setting them up individually then you'll need this printcap name = /etc/printcap load printers = yes
# It should not be necessary to spell out the print system type unless # yours is non-standard. Currently supported print systems include: # bsd, sysv, plp, lprng, aix, hpux, qnx printing = cups
[printers] comment = All Printers path = /var/spool/samba browseable = yes # Set public = yes to allow user 'guest account' to print public = yes guest ok = yes writable = yes printable = yes use client driver = yes
On the Linux machine that has the printer and the above info in the smb.conf file, create a second print queue for the printer and make it a "raw print" queue using redhat-config-printer Instead of choosing the model of the printer, choose the raw option. This way the windows machine will convert the file to the appropriate printer commands and the Linux/samba box just forwards the information through to the printer.
On the Windows machine, install the appropriate printer driver software for the printer and choose the remote raw print queue as the appropriate printer.
You will then need to edit one or both of
/etc/cups/mime.types and /etc/cups/mime.convs and uncomment the line that says application/octet-stream (you should find something like this in the file), but the one line will be commented out.
####################################################################### #
#
# Raw print file support...
#
# Uncomment the following type and the application/octet-stream
# filter line in mime.convs to allow raw file printing without the
# -oraw option.
#
application/octet-stream
Note, if you want to print directly from the Linux machine, you still use the non-raw print queue that was set up for it.
Restart cups and smb and see if it works.
HTH, Dave
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
I am not using the raw print file support or the guest account support. But the rest I have set up as you suggested. The print job shows on the Windows printer window, but disappears somewhere in the transfer to the server and the printer. access_log, error_log and page_log in /var/log/cups have no record of a job coming through.
