Samba Problem + win2k + NT4 PDC

Hallo Liste,

Ich habe ein Problem beim Zugriff auf ein Verzeichnis auf meiner FreeBSD
Büchse via Samba, was nur für einen speziellen User Read und Writeable
sein soll.
beim connecten auf das Verzeichnis in der Netzwerkumgebung kommt ein
hübsches popupfenster username und passwort eingeben.
Ich habe auf der BSD kiste via adduser einen user angelegt.
Mit dem Befehl
cat /etc/passwd | /etc/mksmbpasswd.sh > /usr/local/private/smbpasswd
gleiche ich die user des systems mit der smbpasswd ab.

Meine smb.conf sieht wie folgt aus:

--------------

[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4
   workgroup = VEBIS
   server string = Samba %v on FreeBSD 4.3-release
   remote announce = 192.168.0.66/Vebis
   os level = 2
   keep alive = 30
   security = share
   password server = 192.168.0.10
   encrypt passwords = yes

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
   hosts allow = 192.168.0. 127.

# Uncomment this if you want a guest account, you must add this to
/etc/passwd
# otherwise the user "nobody" is used
  guest account = nobody

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/sambalog.%m

# Put a capping on the size of the log files (in Kb).
   max log size = 100

# Security mode. Most people will want user level security. See
# security_level.txt for details.
# security = share

# Use password server option only with security = server
# password server = 192.168.0.10

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
# encrypt passwords = yes

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /usr/local/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
   socket options = TCP_NODELAY

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
   interfaces = 192.168.0.66/255.255.255.0

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes

# Preferred Master causes Samba to force a local browser election on
startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes

# Use only if you have an NT server on your network that has been
# configured at install time to be a primary domain controller.
; domain controller = <NT-Domain-Controller-SMBName>

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS
Server
; wins support = yes
    wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT
both
   wins server = 192.168.0.10

#============================ Share Definitions
==============================
#[homes]
# comment = Home Directories
# browseable = yes
# writeable = yes
# public = no

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
[tmp]
    path = /usr/local/samba/temp
    browseable = yes
    guest ok = yes
    public = yes
    writeable = yes

[mah]
    path = /usr/local/webserver
    valid users = mah
    browseable = yes
    guest ok = no
    public = yes
    writeable = yes

------------------------

tja ... wo ist das problem ?
rein theoretisch sollte er den user und passwort akzeptieren.

Mit freundlichem Gruß,
Marian

To Unsubscribe: send mail to majordomo(at)de.FreeBSD.org
with "unsubscribe de-bsd-questions" in the body of the message