Partage Samba ne marche plus

Messages postés
99
Date d'inscription
jeudi 9 février 2006
Statut
Membre
Dernière intervention
14 août 2019
-
Bonjour à tous :)

Ca marchait, ça ne marche plus.
Voici mon smb.conf :




#
# 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
netbios name = Deb-1155
hosts allow = 192.168.0.37 192.168.0.19
# .37 : Windows .19 : le 1155 sous Linux
security = user


# 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
# TRADUCTION
# Autoriser les utilisateurs ayant reçu des privilèges d’utilisateurs à créer des
# partages publics, pas seulement authentifiés
usershare allow guests = yes

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

[Partage-sur-1150] # Ce qui apparaîtra sur le réseau
comment = Dossier public
path = /home/partage/Public
browseable = yes
public = yes
writable = yes
read only = no
# valid users = A voir ! Page 2 du fichier "Etapes-tuto-boireau.odt"


[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.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes

# TRADUTION
# Par défaut, les partages \\ serveur \ nom d'utilisateur peuvent être connectés par n'importe qui
# avec accès au serveur samba.
# Le paramètre suivant permet de s'assurer que seul "nom d'utilisateur" peut se connecter à \\ server \ username
# Cela peut nécessiter des ajustements lors de l'utilisation de schémas d'authentification externes

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.)
# TRADUCTION
# Supprimer les commentaires suivants et créer le répertoire netlogon pour les ouvertures de session dans le domaine
# (vous devez également configurer Samba pour qu’il agisse également comme contrôleur de domaine.)

;[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

# TRADUCTION
# Supprimer les commentaires suivants et créer le répertoire de profils à stocker
# profils d'utilisateurs (voir l'option "chemin d'accès" ci-dessus)
# (vous devez également configurer Samba pour qu’il agisse également comme contrôleur de domaine.)
# Le chemin ci-dessous doit être accessible en écriture pour tous les utilisateurs afin que leur
# le répertoire du profil peut être créé lors de la première connexion

;[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
# TRADUCTION
# Les clients Windows recherchent ce nom de partage comme source de fichiers téléchargeables.
# pilotes d'imprimante
[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
# TRADUCTION
# Décommenter pour permettre l'administration à distance des pilotes d'impression Windows.
# Vous devrez peut-être remplacer "lpadmin" par le nom du groupe que vous avez choisi.
# utilisateurs admin sont membres de.
# Veuillez noter que vous devez également définir les autorisations Unix appropriées.
# au répertoire des pilotes pour que ces utilisateurs puissent y avoir des droits en écriture

; write list = root, @lpadmin




Les UC Linux se voient (voient leurs partages respectifs), mais.. plus la bécane Windows. Alors qu'elles accèdent sans problème au partages de la bécane Windows.

Règles ufw ouvrant en entrée/sortie les pots de Samba :

ufw allow in 137/udp
ufw allow in 138/udp

ufw allow out 137/tcp
ufw allow out 138/tcp

ufw allow in 139/tcp
ufw allow out 139/tcp

ufw allow in 445/udp
ufw allow out 445/tcp


Commande adduser partage, puis smbpasswd -a partage
Puis : /etc/init.d/smbd restart
Puis : chmod -R o=+r+w+X /home/partage/Public : accès leclture/écriture sur le partage.

Qu'arrive-t-il ?
Merci :(
Afficher la suite 

1 réponse

Messages postés
3455
Date d'inscription
jeudi 16 juin 2005
Statut
Membre
Dernière intervention
14 août 2019
913
0
Merci
Bonjour,

hosts allow = 192.168.0.37 192.168.0.19

Es-tu sûr que l'IP de ton client n'a pas changé, et est toujours l'une de ces deux-là ?

Xavier
LEVINE
Messages postés
99
Date d'inscription
jeudi 9 février 2006
Statut
Membre
Dernière intervention
14 août 2019
1 -
Bonjour :)

Oui. Mais je crois avoir compris ce matin.
Ca doit venir de la box.
Je vois tous les partages à nouveau, ce matin.
Vu que mon serveur Owncloud aussi pose problème (il consomme énormément de bande passante, même lorsqu'aucun user n'est connecté :/

Hier soir, serveur arrêteé, je pouvais à peine surfer. Quant à télécharger alors là...
Et puis, si je veux fixer une IP statique à une bécane, je vois son adresse MAC, mais pas systématiquement le hostname. Tout à fait anormal.

Sans doute parce qu'il y a beaucoup de machines qui passent par ma salle informatique.

Restauration usine ?
Commenter la réponse de Reivax962