Hi All,
I would like some help here with my Samba-2.2.2 (it's working fine),
but let me tell you what is going on. Currently, we have two Windows 2000
machines running as file servers (drive letters F: and V:), and they
reside on a LAN segment of 169.254.x.x (as does eth1 of my machine which
does some file sharing duties at the moment, we are in test mode).
We have a lot of .dbf files which various users need to update,
and the clients mapping to the linux file server would be NT, Win2K,
95/98. So far, we have seen no problems (straight forward file copy
and access stuff), and we have done some limited testing with .dbf
files for access and modification (again without seeing a problem).
Here is my smb.conf file, which I would like some input on
how to improve for i/o and security issues, if someone would be
kind enuf to provide input. As for user authentication, i'm making
entries in /etc/passwd, and in smbpasswd to allow access (same
username/password that Win2K is using for auth).
# Global parameters
[global]
netbios name = LINUXSERVER
workgroup = WORKGROUP
server string = Linux File Server on OpenLinux 3.1
interfaces = xxx.xxx.xxx.217/24 169.254.1.217/16
hosts allow = xxx.xxx.xxx. 169.254. localhost
password level = 8
password server = something <--- what should this be?
username level = 8
security = Domain
encrypt passwords = Yes
# os level = 34
log file = /var/log/samba/log.%I
socket options = TCP_NODELAY
wins support = no
wins server = xxx.xxx.xxx.25
local master = no
name resolve order = hosts lmhosts bcast wins
dns proxy = no
time server = yes
guest ok = no
#
[homes]
comment = Home Directories
read only = No
browseable = No
[drivev]
comment = Network Files for Drive V:
path = /home/drivev
read only = No
writeable = Yes
# guest ok = Yes
create mask = 0777
force create mode = 0777
directory mask = 0777
force directory mode = 0777
[drivef]
comment = Network Files for Drive F:
path = /home/drivef
read only = No
writeable = Yes
# guest ok = Yes
create mask = 0777
force create mode = 0777
directory mask = 0777
force directory mode = 0777
[temp]
comment = Temporary File Space
path = /tmp
read only = No
guest ok = Yes
As you can see, I have a pretty simple smb.conf file, but would like
to know ways to improve it for i/o and security. I already block
access to 137-139 on eth0 (public IP address, will be going away if
it goes to full blown file server), and allow access in the 169.254/16
section on eth1). Does upper/lower case matter on the windows side
for linux drive shares in Samba? If so, do I need to use the preserve
case parameter?
-Bill