[NTLUG:Discuss] samba guru needed

[Chris Cox]

Jay Urish wrote:
> At 02:25 PM 4/19/2004, you wrote:
> 
>> Jay Urish wrote:
>> ...problems with samba snipped...
>>
>> Does look authentication related. What do your logs show (log.smbd)?
>>
>> Did you create smbpasswd entries for everyone?
> 
> 
> It's a moot point now... My customer decided to move print services over 
> to his 2k3 server box.
> 
> But to answer your question, the logs didn't show anything..
> Thats why I bumped the debug level up...

No offense.. but I would say given the situation you described,
it's impossible that the logs revealed nothing.... something's
just not right at all on this.

Are you running a domain there on w2k+?

If so, you should use smbpasswd -j DOMAINNAME to join your boxes to
the domain and run (smb.conf) with security = domain and use
the password server = * to authenticate directly to
the domain controllers... no smbpasswd necessary, though
you may need to look at a smbusers file to map domain
users to Unix users if they're not the same.


> 
> I need more experience with samba and now cups. I should have been able 
> to make this fly.

I have this running in production today for a multi-million dollar
client.  With a couple of exceptions, all of their file and print
services are using Samba 2.2.8 and CUPS.  The problem areas are
with regards to text printing to certain printers where CUPS
could not correctly deal with it.  CUPS is excellent at graphics
and poor with text formats (a curious thing considering printing
under *ix used to be the other way around).

example for file shares:
http://home.comcast.net/~cjcox4/smb.conf.backups

example for printers:
http://home.comcast.net/~cjcox4/smb.conf.printers
(this one actually includes a share as well though)

We expose only certain printers to the domain using
a special smbprintcap file that just has those printers.
It's simply a list of printer queue names ending in colons:

e.g. /etc/smbprintcap (if printcap name = /etc/smbprintcap)
printer1:
printer2:

Where these correspond to the printer names from CUPS.

To get CUPS to work right, you have to enable the mime
types for raw printing to work:

in mime.types:
# Uncommented line below to allow raw printing from Windows clients.
application/octet-stream

in mime.convs:
*/*                     application/vnd.cups-raw        0       -


Shame this kind of stuff isn't well documented.  Should be
up front in a FAQ at least... I doubt too many would be interested
in a TOTALLY *ix based network implementation (surely there's
one Windows client out there).