Fedora-Fr

Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

installation de samba

[supprimé]

bonjour
je suis débutante dans linux et j'ai installé fedora 4
je voudrai configurer samba pour le reseau de mon entreprise en serveur de fichier et d'impression
et comme je n'y connais rien j'appelle à l'aide, comment on installe samba?
merci

c3r3b3llum

commence par faire des recherches sur le forum samba est un sujet qui a ete maintes fois traités !

[supprimé]

euh desolé mais il est ou le forum samba?

c3r3b3llum

excuse moi j'ai ete un peu vite , il fallait comprendre :

sur le forum sur samba , la fonction recherche du forum te donnera deja pas mal d'info .

tapioca

Bonjour,

Samba aurait pu être installé en même temps que ta FC4.
Pour l'installer à posteriori, tu tapes

yum install samba

dans un terminal (en root).
Pour configurer ton serveur, utilise la commande system-config-samba ou les menus Paramètres de système -> Paramètres de serveur -> Samba.
Ici, il n'y a pas de forum Samba mais tu peux faire une recherhe avec ce mot-clé.

[supprimé]

ok donc a priori le serveur samba etait installé
j'ai configuré comme tu ma dit et j'ai donc partagé mes fichiers
par contre les autres pc, sous windows 2000, ne voient pas le serveur et donc n'ont pas acces aux fichiers contenu sur celui-ci

j'ai aussi fait une recherche sur le forum avec le mot samba et je trouve que mon post 🙂
si quelqu'un pouvait m'indiquer un site ou forum qui explique bien la configuration car je suis une vraie débutante et comme je dois mettre ce serveur au point pour mon entreprise je me doit d'etre au point en 1 mois ou 2
ca va etre chaud ...

SoukoussMan

peut tu nous montrer ton smb.conf svp qui se trouve dans /etc/samba/smb.conf de souvenir.

[supprimé]

euh c tres long donc j'espere que cate servira je te copie tout :

# 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 made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = clairlogis

# server string is the equivalent of the NT Description field
server string = Samba Server

# 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.1. 192.168.2. 127.

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = /etc/printcap
load printers = yes

# 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
; printing = cups

# This option tells cups that the data has already been rasterized
cups options = raw

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

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# all log information in one file
# log file = /var/log/samba/smbd.log

# 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.
# Use password server option only with security = server
; password server = <NT-Server-Name>

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8

# 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
; smb passwd file = /etc/samba/smbpasswd

# The following are needed to allow password changing from Windows to
# update the Linux system 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* %nn *ReType*new*UNIX*password* %nn *passwd:*all*authentication*tokens*updated*successfully*

# Unix users can map to different SMB User names
; username map = /etc/samba/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/samba/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 SO_RCVBUF=8192 SO_SNDBUF=8192

# 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.12.2/24 192.168.13.2/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.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 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 = 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

# 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 = \%LProfiles%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 ==============================
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/false
username map = /etc/samba/smbusers
password server = None
winbind use default domain = no
[homes]
comment = Home Directories
browseable = no
writeable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /home/netlogon
; guest ok = yes
; writable = no
; share modes = no

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /home/profiles
; browseable = no
; guest ok = yes

# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
printable = yes

# 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 = Public Stuff
; path = /home/samba
; public = yes
; read only = yes
; write list = @staff

# 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

# A private directory, usable only by fred. Note that fred requires write
# 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 = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765

[nouveau fichier]
path = /home/serveur/nouveau fichier
writeable = yes
guest ok = yes

voila j'attends de tes news 🙂

[supprimé]

euh j'attends toujours une reponse

kapouere

Avant tout as-tu vérifié la conf de ton réseau ?

[supprimé]

ca depend ce que tu appelle la config du reseau
si c'est les adresses ip j'en est mis, mais a part ca au niveau du serveur samba jai rien trouvé dans la config
j'ai pu simplement partager un fichier sur le reseau
mais actuellement les postes windows ne voient pas le serveur, et le serveur ne voit pas les postes windows, il sait qu'il y a un reseau windows mais quand j'ouvre il n'y a rien dedans
et lorsque je ping le serveur a partir d'un poste windows il le voit sans probleme
j'espere que quelqu'un saura m'aider 🙁

kapouere

Lorsque tu ouvres Konqueror si tu saisis dans "Emplacement" :
le_nom_de_pc_windowsle_nom_du_partage, est-ce que tu as une fenêtre "Boite de dialogue d'autorisation". Si oui tu saisis le user windows et son mot de passe, et là tu dois avoir ton partage windows dans Konqueror.

aurelien

salut

dans ton fichier smb.conf

hosts allow = 192.168.1. 192.168.2. 127.

elle sont bizards tes ip

tu devrais avoir plutot

hosts allow = 127.0.0.1, 192.168.1.0/255.255.255.0, 192.168.2.0/255.255.255.0

a tu cree des users pour samba ?
a tu ouvert les ports sur ton firewall si il est activer ?

pas

les ports a ouvrir dans ton firewall et celui de ton routeur sont :

netbios-ns 137/tcp # NETBIOS Name Service
netbios-ns 137/udp
netbios-dgm 138/tcp # NETBIOS Datagram Service
netbios-dgm 138/udp

il faut que tu décommantes ces lignes 'dans smb.conf :

; printing = cups

; hosts allow = 192.168.1. 192.168.2. 127

;[public]
; path = /usr/somewhere/else/public (ou est le partage de fichiers)
; public = yes
; only guest = yes
; writable = yes
; printable = no

A+

[supprimé]

oula oula
bon alors pour commencer g testé le truc dans konqueror mais "nom de partage" c'est quoi? le nom du fichier a partager ds les pc windows?

ensuite je sais pas comment créé des user sur samba, et surtout les noms doivent corespondre a ceux d pc windows?

et pour le firewall je peux pas le desactivé, c un physique auquel j'ai pas acces et idem pour le routeur

je crois que je vais vous donner du fil a retordre ^^
encore merci de continuer a m'aider

aurelien

salut

si les pc sont relier a um modem router firewall ?
tu dois desactiver le firewall de ta fedora,
sur les clients windows si tu a XP SP2 desactive le firewall

pour cree tes user
vas dans
Application --> Parametres de systeme --> Parametres de serveur --> Samba

si tu ne la pas installe " system-config-samba "

iamaware

Voici comment j'ai installé le mien:
En 2 sites :http://www.trustonme.net/didactels/103.html
http://sambafr.idealx.org/samba/docs/man/Samba-Guide/simple.html#charitynet

Tu as toutes les directives pour ton linux et windows
et ça marche impec.
j'ai tjrs fedora core3 en serveur
2 postes en win98se
2 postes en winxp edition familial
1 portable HP sous XP aussi

Pour le partage de connexion j'utilise le parefeu FIRESTARTER facile à configurer.
a récupérer ici :http://www.fs-security.com/download.php

En espérant que ça t'aide.
Tiens moi au courant.

A+
GUI

pas

Si tu n' as pas les droits administrateur tu ne pourras jamais configurer ton partage.
A+
et pour iamaware firestarter est dans les dépôts.
Désolé.

[supprimé]

ok iamaware je vais tester ton truc et je vous tiens au courant
merci

[supprimé]

Je me permettrais d'ajouter un conseil. D'expérience, il est beaucoup plus facile de configurer Samba correctement lorsqu'on utilise SWAT, qui est une interface web permettant de bidouiller de manière relativement sécuritaire dans le fichier smb.conf.

Pour l'installer, il s'agit simplement de faire la commande suivante:

# yum install samba-swat

# apt-get update
# apt-get install samba-swat

Une fois installé, il suffit de taper l'URL suivante:

http://[ADRESSE_IP_DU_SERVEUR]:901/

Page suivante »