Nieuws:

Welkom, Gast. Alsjeblieft inloggen of registreren.
Heb je de activerings-mail niet ontvangen?

Auteur Topic: [OPGELOST] SAMBA-Server Configuraties  (gelezen 3928 keer)

[OPGELOST] SAMBA-Server Configuraties
« Gepost op: 2010/05/08, 23:22:49 »
Ik heb volgens mij wel ALLES gehad, maar ik kom maar NIET uit.

Ik heb samba geïnstalleerd alle configuraties toegepast (verschillende tutorials gevolgd). Zelfs via webmin ook nog geprobeerd maar ik krijg maar NIET voor elkaar om een share te bezoeken. Wilt namelijk mijn gebruiksnaam en wachtwoord NIET pakken.

Allemaal uitgeprobeerd:
http://www.youtube.com/watch?v=spJAzHOpz5U&NR=1
http://www.ubuntugeek.com/howto-setup-samba-server-with-tdbsam-backend.html
http://www.howtogeek.com/howto/ubuntu/install-samba-server-on-ubuntu/

Weten jullie misschien nog wat oplossingen?
« Laatst bewerkt op: 2010/05/09, 17:35:52 door shinger »

Re: SAMBA-Server Configuraties
« Reactie #1 Gepost op: 2010/05/09, 00:52:13 »
Ik heb nu deze ook gevolgd.. maar nog steeds krijg ik geen toegang.

http://www.webmin.com/samba-howto.html

Re: SAMBA-Server Configuraties
« Reactie #2 Gepost op: 2010/05/09, 01:03:02 »
Hier nog mijn smb.conf misschien dat jullie wat fouten in zien..

#
#sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]
log file = /var/log/samba/log.%m
guest account =
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
obey pam restrictions = yes
map to guest = bad user
encrypt passwords = yes
public = yes
passwd program = /usr/bin/passwd %u
passdb backend = tdbsam
dns proxy = no
server string = %h server (Samba, Ubuntu)
unix password sync = yes
workgroup = KOERDHOOD
os level = 20
syslog = 0
security = share
panic action = /usr/share/samba/panic-action %d
usershare allow guests = yes
max log size = 1000
pam password change = yes

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of

# server string is the equivalent of the NT Description field

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   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 = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.

# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects

# Cap the size of the individual log files (in KiB).

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.

# Do something sensible when Samba crashes: mail the admin a backtrace


####### Authentication #######

# security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using. 


# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe. 
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe. 
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
#   load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;   printing = cups
;   printcap name = cups

############ Misc ############

# 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 = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
#   socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
#   domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares.  This will share each
# user's home directory as \\server\username

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   read only = yes
;   locking = no
;   path = /cdrom
;   guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
#       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
;   preexec = /bin/mount /cdrom
;   postexec = /bin/umount /cdrom



[Troep]
guest account = shinger
valid users = shinger
writeable = yes
write list = shinger
path = /media/RAID1/Troep
allow hosts = 192.168.1.200

[homes]
writeable = yes
path = /media/RAID1/Home_Users

Offline chris.

  • Lid
    • http://www.linuxmintusers.be
Re: SAMBA-Server Configuraties
« Reactie #3 Gepost op: 2010/05/09, 11:06:46 »
even een paar gedachten,

na alles geinstalleerd te hebben en de rechten ingesteld te hebben heb je wel een herstart gedaan?
in mijn ervaring is dat nodig om alles goed aan de babbel te krijgen.

je draait idd nog steeds 9.10 zoals in je handtekening staat? want in lucid wil het bij mij ook nog niet [op die ene pc die er op draait, zal nog wel een fix voor komen].

probeer eerst eens een share op te zetten die helemaal open is, maw geen beperking of wachtwoord.
dit kan het simpelste door nautilus als root te openen en bijvoorbeeld de map openbaar met rechts te selecteren en te kiezen voor deeloptie's, en hier vervolgens alles aanvinken, drie vinkjes totaal, dan zou je op een andere pc niets hoeven op te geven en de share zo moeten kunnen benaderen.

Re: SAMBA-Server Configuraties
« Reactie #4 Gepost op: 2010/05/09, 11:59:44 »
OOh nee chris heheh.. Mijn handtekening is nog oud moet nog bewerkt worden. Op mijn computer draai ik zelf ubuntu desktop 10.04 op laptop is nog 9.10 (wacht nog op dat alle software voor 10.04 uit komt en nog stabiliteit.) Op mijn NAS was gewoon een Linux versie die door de fabrikant zelf gemaakt was. Ik heb nu dus Ubuntu server 10.04 32bit opgegooid. En jij zegt zelf dat het niet lukt of zo..

Ik heb zelf nu ook dat als ik dan probeer de gedeelde map weer te openen die op de server staat de server dan crasht is heeeeel raar.

zou jij misschien even link geven naar de bug??
« Laatst bewerkt op: 2010/05/09, 12:07:57 door shinger »

Re: SAMBA-Server Configuraties
« Reactie #5 Gepost op: 2010/05/09, 12:33:53 »
Moet je niet de # voor de regel weghalen als je hem toe wilt passen?
Of is dat hier niet het geval?

Re: SAMBA-Server Configuraties
« Reactie #6 Gepost op: 2010/05/09, 13:40:02 »
Welke regel verwijs je er precies naar??

Re: SAMBA-Server Configuraties
« Reactie #7 Gepost op: 2010/05/09, 17:18:08 »
Chris. Je zei dat je zelf ook problemen had met ubuntu 10.04 en de shares. Nou Het is mij gelukt!!. Ik heb veel mee moeten stoeien ben gisteren helemaal mee bezig geweest en vandaag voor grotendeels. Uiteindelijk keek ik of ik wel de laatste versie van samba had (3.4.7 staat op lucid). De nieuwste versie is 3.5.2 die heb ik geinstalleerd met behulp van een PPA.

https://launchpad.net/~a.bono/+archive/samba3.5

kijk of het jou ook zou lukken.

Offline chris.

  • Lid
    • http://www.linuxmintusers.be
Re: [OPGELOST] SAMBA-Server Configuraties
« Reactie #8 Gepost op: 2010/05/09, 18:05:46 »
tnx ook hier loopt t nu goed :)