Re: [SLUG] print server for Windows

From: Daniel Jarboe (daniel.jarboe@gmail.com)
Date: Wed Jan 25 2006 - 10:47:21 EST


First recommendation, do Samba 3. Much cleaner integration with cups
than 2.2.x.

> Then set up Samba on the Linux box. The following are the relevant lines
> from my smb.conf:
>
> In the global section:
>
> printing = cups
> printcap name = /etc/printcap
> load printers = yes

use printcap name = cups

load printers = yes will automatically create shares for any printers
cups knows about when samba initializes. Otherwise, you need to
define individual print shares with printable = yes. You usually want
load printers = yes unless you have printers you don't want samba to
share.

> print command = lpr -P %p -o raw %s -r

you don't need the above. let samba use the cups api to submit jobs.

The path specified in the [printers] is used as a spool directory for
the windows jobs as they are being received by Samba. If you have no
preference then /tmp/ is good enough.

You also might want to consider setting printer admin in smb.conf so
you can cancel/pause print queues and other people's print jobs, etc.

In /etc/cups/mime.convs, make sure to uncomment the:
application/octet-stream application/vnd.cups-raw 0 -
line, and in /etc/cups/mime.types, make sure to uncomment:
application/octet-stream

These windows printers don't even have to be supported by a cups ppd,
samba is just pushing the printstream already generated by the windows
clients. The application/octet-stream (raw) allows users to send
print streams to the printer without any cups processing/intervention
(which CUPS default installation disables for security).

The only other question becomes if you want "point 'n print" driver
installation. If so, you must create a print$ share, and upload the
print drivers to the samba. Don't know what kind of lock down you
want, but you will need write access to upload the drivers initially,
and anyone who needs the ability to download the drivers read. Point
'n Print is not necessary, as you can just install whatever print
drivers you want locally on the windows client for the remote printer,
but I like the windows drivers stored on the server so I always use
it. There's more information in whatever Samba is calling it's
guide/howto these days... samba.org.

Then, fastest way from the windows client is to Run \\servername and
double click on the printer to install. You don't need to do any
mapping for LPT1 or anything like that. If you are making
administrative changes to the printer on the server, first hit the
Printers and Faxes (should be listed last), then right click on the
individual printers within.

~ Daniel

-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:09:08 EDT