Here is a working example (one of two) of Samba disk share from
a RH6.2 named James on a Win98 pier to pier network (no passwds)
that gives full acess to the directory /home/public.
>smb.conf from James the file server machine:
# /etc/smb.conf = config file for James
# 25Oct99 Larry copied from original
#
# This is the main Samba configuration file. smb.conf(5) manual page
# NOTE: Whenever you modify this file you should run the
# command "testparm smb.conf" to check for basic syntactic errors.
# =============================================== Global Settings ====
[global]
workgroup = FAMILY
hosts allow = 192.168.1. 127.
# use a separate log file for each machine that connects
log file = /var/log/samba/log.%m
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Security mode. Most people will want user level security.
# See security_level.txt for details.
security = share
# See speed.txt and the manual pages for better performance.
socket options = TCP_NODELAY
# Configure Samba to use multiple interfaces
interfaces = 192.168.1.1/24
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no
encrypt passwords = no
; smb passwd file = /etc/smbpasswd
# add users with smbpasswd command
password level = 0
preferred master = no
os level = 0
null passwords = no
dead time = 0
debug level = 0
domain master = no
comment = James - Tekram P5mvp P133
#========================================= Share Definitions ====
[public]
comment = access to the data space
path = /home/public
public = yes
read only = no
guest ok = yes
case sensitive = no
mangle casee = yes
preserve case = yes
browseable = yes
writable = yes
printable = no
create mode = 0777
#
==================================================
----- Original Message -----
From: Greg Schmidt <slugmail@gschmidt.net>
To: <slug@nks.net>
Sent: Sunday, July 15, 2001 2:54 AM
Subject: [SLUG] samba question
> I'm thinking it is probably easier to make other things work with
Microsoft
> stuff than it would be to make Microsoft stuff do something like run an
NFS
> client. (Done it; didn't like it. That BSD has no relation to Berkeley.)
That
> said, is there some way to make Samba serve up files with plain old
share-based
> authentication without opening wide security holes? It seems Samba always
> wants user-level security, or else wants to give the share to anyone who
> happens to be in the "neighborhood". I don't need no stinking NT domain
> controller. I don't want to sinc passwd files. I just want it so that if
you
> know the share's password you get it, and if you don't, you get to try
again.
> Your username wouldn't matter, just like sharing between Win9X boxen in a
> so-called "peer-to-peer" setup. I'll be doing it behind a NAT that
doesn't
> pass NETBIOS, so I think it would work well for me. I got a bet with a
buddy
> that it can't be done. :) Please prove me wrong.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:08:06 EDT