Samba... HELP !!!!
toto24
-
jisisv Messages postés 3678 Statut Modérateur -
jisisv Messages postés 3678 Statut Modérateur -
Bon, je m'adresse en particulier à ceux qui ont réussi à avoir un réseau hétérogène Linux-Win$$$ avec Samba:
Après plusieurs tentatives, j'ai enfin réussi à configurer le fichier /etc/smb.conf (en ligne de commande avec vi car mon futur serveur nommé SERVER n'a pas d'interface graphique).
J'ai créé 3 répertoires partagés, homes, fourre-tout, et SVG
Le serveur apparait dans le voisinage réseau de win$$$ 98 et quand je clique sur le dossier 'homes', j'obtiens ce message d'erreur:
'\\SERVER\homes n'est pas accessible
Le partage est introuvable. Assurez-vous que le type a été entré correctement.'.
Apparemment, ce dossier ne peut être utilisé que par des machines UNIX...
Pour les deux autres dossiers, j'ai un autre message d'erreur:
'\\SERVER\fourre-tout n'est pas accessible
Accès refusé.'
Tous les partages sont publics.
Si quelque chose m'a échappé ou si quelqu'un a déjà rencontré ce problème, merci de me le signaler et de m'aider à le résoudre.
Après plusieurs tentatives, j'ai enfin réussi à configurer le fichier /etc/smb.conf (en ligne de commande avec vi car mon futur serveur nommé SERVER n'a pas d'interface graphique).
J'ai créé 3 répertoires partagés, homes, fourre-tout, et SVG
Le serveur apparait dans le voisinage réseau de win$$$ 98 et quand je clique sur le dossier 'homes', j'obtiens ce message d'erreur:
'\\SERVER\homes n'est pas accessible
Le partage est introuvable. Assurez-vous que le type a été entré correctement.'.
Apparemment, ce dossier ne peut être utilisé que par des machines UNIX...
Pour les deux autres dossiers, j'ai un autre message d'erreur:
'\\SERVER\fourre-tout n'est pas accessible
Accès refusé.'
Tous les partages sont publics.
Si quelque chose m'a échappé ou si quelqu'un a déjà rencontré ce problème, merci de me le signaler et de m'aider à le résoudre.
10 réponses
-
-
Il serait bon de fournir les extraits utiles de smb.conf.
Quel est le mode d'accès au serveur (user, je suppose ?)
Quel est le partage défini dans homes?
Y a-t-il des restrictions sur les utilisateurs , les adresses IP des clients?
Les domaines Win et Samba coïncident-ils?
Bref , il seait utile d'avoir la section globale et les extraits relatifs aux
partages.
Et les fichiers log de samba ?
Les messages d'erreur de Windows, c'est du folklore.
Fatal error:
Keyboard not found
Press any key to continue...
Je suis favoravle à l'utilisation d'un éditeur plutôt que d'utiliser SWAT
puisque smb.conf est bien documenté.
Si tu ouvres SWAT sur le réseau local ave une ligne du type
swat stream tcp nowait.400 root /usr/sbin/swat swat
dans /etc/inetd.conf
et une ligne
swat 901/tcp
dans /etc/services (suivi d'un killall -HUP inetd)
si tu n'utilises pas le nouveau super serveur inet dont je n'ai
plus le nom immédiatement en tête...)
il sera possible d'accéder à l'interface de configuration
de Samba depuis ton navigateur et environnement favori dan le réseau local.
(même avec lynx)
avec http://nom-unix-du-serveur-samba:901
Tell me more...
Johan -
Voici le fichier smb.conf, les ==> introduisent des commentaires faits par moi...
autre question: '; xxx' les ';' introduisent des commentaires ??
# 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 (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not many any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = serveur Linux ;>>
# 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
# Enabling internationalization:
# you can match a Windows code page with a UNIX character set.
# Windows: 437 (US), 737 (GREEK), 850 (Latin1 - Western European),
# 852 (Eastern Eu.), 861 (Icelandic), 932 (Cyrillic - Russian),
# 936 (Japanese - Shift-JIS), 936 (Simpl. Chinese), 949 (Korean Hangul),
# 950 (Trad. Chin.).
# UNIX: ISO8859-1 (Western European), ISO8859-2 (Eastern Eu.),
# ISO8859-5 (Russian Cyrillic), KOI8-R (Alt-Russ. Cyril.)
# This is an example for french users:
; client code page = 850
; character set = ISO8859-1
# CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK
# (as cups is now used in linux-mandrake 7.2 by default)
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = lpstat
load printers = no ===> g po d'imprimante partagée
# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx, cups
printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
guest account =
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Put a capping on the size of the log files (in Kb).
max log size = 50
# 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 = toto
# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 4
; username level = 4
# 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 = no
; smb passwd file = /etc/smbpasswd
# The following are needed to allow password changing from Windows to
# update the Linux sytsem password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
# Unix users can map to different SMB User names
username map = /etc/smbusers
# 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 = /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.1/24
# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.0.2 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.0.2 192.168.2.44
# 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 = 99
# 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 =
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
logon script = %m.bat
# run a specific logon batch file per username
logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# 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
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
; preserve case = no
; short preserve case = no
# Default case is normally upper case for all DOS files
; default case = lower
# Be very careful with case sensitivity - it can break things!
; case sensitive = no
#============================ Share Definitions ==============================
[homes]
comment = Repertoire principal
browseable = yes
writable = yes
guest ok = yes
valid users = zabou toto24
available = yes
path = /SVG
public = yes
create mode = 0777
[fourre-tout]
comment = Pour faire du menage
path = /home/Toto24
guest ok = yes
writable = yes
public = yes
security = share
create mode = 0777
[Profiles]
path = /home/profiles
browseable = no
guest ok = yes
# NOTE: If you have a CUPS print system there is no need to
# specifically define each individual printer.
# You must configure the samba printers as "Generic PostScript Printer"
# on your Windows clients.
# If you wish to configure the printers directly on the Windows clients
# (i.e. use the windows drivers on the clients) you must swap the
# 'print command' line below with the commented one.
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# to allow user 'guest account' to print.
guest ok = yes
writable = no
printable = yes
create mode = 0700
# =====================================
# print command: see above for details.
# =====================================
; print command = lpr-cups -P %p -o raw %s # using client side printer drivers.
print command = lpr-cups -P %p %s # using cups own drivers (use generic PostScript on clients).
lpq command = lpstat -o %p
lprm command = cancel %p-%j
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
[public]
comment = Repertoire public
path = /home/samba
public = yes
writable = yes
printable = no
browseable = yes
# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
/bin/bash: q: command not found
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
[myshare]
comment = autres données partagées
path = /usr/bin
public = yes
writable = yes
printable = no
create mask = 0765
-
Les clients:
Toto24 -- 192.168.0.3 -> en théorie, passke win me fout la pagaille ds tout çà..
zabou -- 192.168.0.2 -> celui-là, c bon !
Je n'ai fait que configurer smb.conf -
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question -
J'ai repris la config pour homes sur mon FreeBSD 3.2 avec Samba 2.0.7
Je te conseille d'utiliser:
security=users
C'est sur base de l'utilisateur que la permission sera accordée
Les permissions unix sur /SVG sont-elles correctes ?
Crée les passwords utilisateurs samba avec smbpasswd
( ces passwords n'ont rien à voir avec les passwords Unix)
voir: man smbpasswd
D'autre part, la ligne security=share est globale et ne doit pas être
présente dans un partage.
Synchronise les noms de domaine Win et samba
workgroup = "le workgroup de ta/tes bécanes win"
Pour les versions récentes de Win, mettre
encrypt passwords = yes
Pour tester la config :
"path-to-samba-bin"/testparm
Et toujours , lire les docs et man pages...
A+
Johan Daine -
Les premissions de /SVG sont plus ke correctes...
Est-ce vraiment indispensable de mettre des mots de passe ds smbpasswd ? Et de gérer au niveau de l'utilisateur ??
Le workgroup est synchronisé
-
-
-
Ben, j'ai installé la Mandrake 8.0 avec Samba 2...
Maintenant, mon serveur n'est même plus visible ds le voisinage réseau.... -
Je n'ai pas encore essayé Samba 2.0.9 ni 2.2.0.
Je me promets de le faire.
Tes machines Win sont elles visibles depuis linux:
smbclient -L "nom-win-net-bios de ta machine"
?
Johan