Bonjour à tous,

Je pose ici car je souhaite monter un serveur samba, malheureusement après avoir suivi plusieurs tuto je n'arrive pas a voir mon serveur samba sur mes pc clients.

Je suis sous ubuntu 20.04

Voici mon fichier de configuration:

#
# 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. 

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

[global]

## Browsing/Identification ###

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

# server string is the equivalent of the NT Description field
        server string = %h server (Samba, Ubuntu)

# 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.
   dns proxy = no

#### 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
   log file = /var/log/samba/log.%m

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

# 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.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


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

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

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

   obey pam restrictions = yes

# 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.
   unix password sync = yes

# 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).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# 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'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

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

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or '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

############ 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

# 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

# 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
   usershare allow guests = yes

#======================= 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
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[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
[commun]
        path = /srv/samba
        browseable = yes
        read only = no
        writable = yes
        valid user = imprimante, seb31t
        create mask = 0773
        directory mask = 0777

Merci de m aider à comprendre mon erreur.

Cordialement.

Salut, normalement tu dois te trouver sur le même réseau et appartenir au même groupe NetBIOS.

Là tu spécifie un server WINS (qui est en plus farfelu pour son nom), alors que la plupart du temps, il n'y en a pas, les requêtes des noms des ordi sur le réseau sur fait via broadcast.

Si ton réseau est en ethernet tu as bien spécifié une interface réseau eth0, il faut que ce soit la bonne. Pour l'IP je mettrais en plus l'adresse IP sur le réseau, et bien sûr ton samba doit être sur le même réseau que les autres PC Windows.

Tu as une commande pour tester que ton ficher de config ne contient pas d'erreur de syntaxe.

testparm -s

Une fois la modification WINS changée il te faudra redémarrer le service smbd, mais là ça dépend si ton système utilise SysVInit ou systemd.

(systemd il me semble pour Ubuntu)

Donc ça serait une commande du type:

systemctl reload smbd.service

Bref il faut déjà que tu vois ton server samba sur le réseau Microsoft...Ensuite tu pourras gérer les dossiers/imprimantes/partages et les permissions...Dans un premier temps il faut que le nom de ton server se propage sur le broadcast du réseau local.

-
Edité par maroufle34 9 septembre 2021 à 18:52:14

Bonjour,

et merci pour ton retour et pour toute ces pistes,

Malheureusement je suis débutant en Linux et le je suis un peu perdu,

J'ai je pense résolu le probleme eth0.

sudo testparm -s
Load smb config files from /etc/samba/smb.conf
Unknown parameter encountered: "valid user"
Ignoring unknown parameter "valid user"
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
        bind interfaces only = Yes
        interfaces = lo eth0:192.168.1.62
        log file = /var/log/samba/log.%m
        logging = file
        map to guest = Bad User
        max log size = 1000
        obey pam restrictions = Yes
        pam password change = Yes
        panic action = /usr/share/samba/panic-action %d
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        passwd program = /usr/bin/passwd %u
        server role = standalone server
        server string = %h server (Samba, Ubuntu)
        unix password sync = Yes
        usershare allow guests = Yes
        idmap config * : backend = tdb


[commun]
        create mask = 0773
        directory mask = 0777
        path = /srv/samba
        read only = No

mais pour passer de wins a broadcast j'aurais besoin de tes conseil.

Merci d'avance.

Salut,

il faut te concentrer d'abord sur cette section [global]

le reste ne sera que de la config des users/partages.

Les autres ordis sont bien sur le même réseau? En 192.168.1.0/24 ( nommage avec masque de sous réseau, ça veut dire le réseau 192.168.1.* ou * est compris entre 1 et 254, le 255 étant l'adresse du broadcast.)

Tu peux mettre:

wins support = no

Et redémarrer les services smbd ET nmbd.

C'est peut être là que ça coince, nmbd est un service de noms pour les réseaux microsoft, donc un redémarrage du service peut être nécessaire aussi.

Normalement après ça et si tous les autres ordis sont sur le même réseau, en WiFi ou ethernet, ils devraient pourvoir voir ton Linux samba après un léger temps de propagation sur le broadcast.

The bind interfaces only = Yes is necessary to exclude TCP/IP session services (ports 135, 139, and 445) over the interfaces that are not specified. Please be aware that nmbd will listen for incoming UDP port 137 packets on the unlisted interfaces, but it will not answer them. It will, however, send its broadcast packets over the unlisted interfaces. Total isolation of ethernet interface requires the use of a firewall to block ports 137 and 138 (UDP), and ports 135, 139, and 445 (TCP) on all network interfaces that must not be able to access the Samba server.
https://www.samba.org/~ab/output/htmldocs/Samba3-HOWTO/NetworkBrowsing.html

ça c'est au cas où on veuille totalement isoler samba du réseau sur les autres interfaces, au départ si tu n'as qu'une seule interface, ce paramètre n'est pas utile.

-
Edité par maroufle34 10 septembre 2021 à 14:30:59

Bonjour,

Merci pour ton aide mais je n'arrive pas a demarer le service nmbd !

Voici les retours

 sudo systemctl status  nmbd.service 
● nmbd.service - Samba NMB Daemon
     Loaded: loaded (/lib/systemd/system/nmbd.service; enabled; vendor preset: enabled)
     Active: failed (Result: timeout) since Fri 2021-09-10 12:26:38 UTC; 18s ago
       Docs: man:nmbd(8)
             man:samba(7)
             man:smb.conf(5)
    Process: 61234 ExecStart=/usr/sbin/nmbd --foreground --no-process-group $NMBDOPTIONS (code=killed, signal=TERM)
   Main PID: 61234 (code=killed, signal=TERM)
     Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..."

sept. 10 12:25:07 srvprod systemd[1]: Stopping Samba NMB Daemon...
sept. 10 12:25:07 srvprod systemd[1]: nmbd.service: Succeeded.
sept. 10 12:25:07 srvprod systemd[1]: Stopped Samba NMB Daemon.
sept. 10 12:25:07 srvprod systemd[1]: Starting Samba NMB Daemon...
sept. 10 12:26:38 srvprod systemd[1]: nmbd.service: start operation timed out. Terminating.
sept. 10 12:26:38 srvprod systemd[1]: nmbd.service: Failed with result 'timeout'.
sept. 10 12:26:38 srvprod systemd[1]: Failed to start Samba NMB Daemon.

Merci pour ton aide.

Salut,

Pour ta config j'aurais juste mis eth0 sans adresse IP, je ne sais pas si tu as fait un testparm -s dessus, mais il semble que ton server nmbd ne prennent en compte que ton interface lo, qui en plus ne sert à rien dans la pratique.

Tu peux aussi regarder via ifconfig ou ip (vu que la commande ip a remplacé ifconfig) pour voir si ton interface eth0 est bien up dans sa config, qu'elle a bien l'adresse de ip de ton réseau sur lequel tu veux que ton samba diffuse son nom aux autres postes.)

-
Edité par maroufle34 12 septembre 2021 à 18:25:47