Hello Noèl,
this is the pertinent section of smb.conf:
[global]
name resolve order = lmhosts host wins bcast
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
idmap gid = 15000-17000
obey pam restrictions = Yes
hosts allow = 192.168.43.
show add printer wizard = No
time server = Yes
passwd program = /usr/bin/passwd %u
dns proxy = No
netbios name = LEOPARD
map archive = No
invalid users = root
idmap uid = 15000-17000
default = CompanyFiles
workgroup = ROBLIN
os level = 20
hosts deny = ALL
auto services = CompanyFiles
security = user
max log size = 1000
log file = /var/log/samba/log.%m
load printers = No
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
include = /etc/samba/dhcp.conf
logon drive = M:
encrypt passwords = yes
passdb backend = tdbsam
template shell = /bin/bash
server string = File Server: %h (Samba %v)
valid users = irena, victor
syslog = 0
panic action = /usr/share/samba/panic-action %d
[dir]
writeable = yes
path = /srv/dir
force group = users
revalidate = yes
valid users = ... names of the allowed users ...
create mode = 0660
case sensitive = yes
directory mode = 0770
This file was generated with SWAT and worked flawlessly in the past,
i.e. until about three or four weeks ago. The Windows clients operate
under Windows XP (all Windows service packs installed).
Thanks,
Peter
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
