Re: [SLUG] Samba 3.0.2a printing issues

From: Backward Thinker (backwardthinker@juno.com)
Date: Sun May 02 2004 - 07:45:31 EDT


> > Everytime you make changes to smb.conf you must restart samba or
> > it will not recognize the changes.

Samba 3 is pretty good about reloading the smbconf file after it
changes automatically. You don't need to send a SIGHUP to all smbd's
like in 2.2.x. Even in 2.2.x you didn't need to restart, reloading
was sufficient (unless it was a major change, like telling samba to
listen on different interfaces, etc).

> I am having is that when I try to connect a windows box to the
> printer (via samba) I am getting 'Access Denied. unable to
> connect'. the printer driver is installed.

What is security mode in the [global] section? That's the first thing
to check :). The default is User, and in that case the windows box
must be able to log in before it connects to the share, even though
the share is public.

Is the driver installed locally on the client (intead of installed
from the samba print$ share)? Is the client W2K or higher? Does
printing actually succeed, though shows the '... unable to connect'
status? If you answered yes to a bunch of those questions, then
usually it's a matter of setting up the print$ share and adding the
driver to samba via the APW, or setting "use client driver = yes" in
smb.conf. If you have the time, setting up the print$ share is the
better solution than use client driver.

Anything of interest in the samba logs?

btw, there were a few print bugs in 3.0.2a, including a segfault
(sometimes). 3.0.3 is out now, though.

~ Daniel

________________________________________________________________
The best thing to hit the Internet in years - Juno SpeedBand!
Surf the Web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!
-----------------------------------------------------------------------
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:43:38 EDT