Fedora-Fr

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

serveur samba

Fann

Bonjour

Voilà, pour créer un "échange" de fichiers entre mon portable sous Windows XP SP2 et mon PC sous fedora core 5, j'ai installé et configuré samba comme expliqué dans votre tutorial.

Le problème, c'est que je n'ai pas accès. Quand j'entre l'ip de mon pc sous fed', il cherche puis au bout de qqs minutes me dit qu'il trouve pas. L'entre alors l'ip suivit du nom du dossier, mais c'est pareil.

A noter que les dossiers apparaissent bien dans mon aboressence : favoris réseau/réseau microsoft Windows/mshome/localhost/ldb/share et l'autre que j'ai créé sur les mêmes paramètres. C'est juste qu'il arrive pas à aller dessus.

Quelqu'un peut-il m'aider s'il vous plaît ?

Merci par avance.

Raily

Bonsoir
Peut tu poster le contenu de ton smb.conf ?

Fann

oui le voilà :

[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = mshome

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

# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = share

# 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
load printers = yes

# you may wish to override the location of the printcap file
; printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, 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

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>

# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM

# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam

# 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.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m

# 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

# 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 = \%L\Profiles\%U

# 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 default is NO.
dns proxy = no
; encrypt passwords = yes
; guest ok = no
; guest account = nobody
; encrypt passwords = yes
; guest ok = no
; guest account = nobody

# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g

#============================ Share Definitions ==============================
[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 = /usr/local/samba/lib/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 = /usr/local/samba/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 = /usr/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writeable = no
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
; writable = yes
; printable = no
; 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

[SHARE]
comment = Partage en lecture et écriture pour tous
path = /home/ldb/SHARE/
writeable = yes
browseable = yes
guest ok = yes

[LDB]
comment = dossier home
path = /home/ldb
; writeable = no
browseable = yes
guest ok = yes

Paulove

Hello ...

Quelle réponse as tu à cela: smbclient -L localhost -U%
puis à cela: smbclient -L hostXP -Ucompte%motdepasse
et si tu ajoutes à ton smb.conf valid users = compte....
J'ai récemment installé Samba et Cups....regardes là
Sinon as tu crées tes comptes sur ton serveur Linux ?
As tu ajouté à ton fichiers hosts XP la correspondance nom/IP ?
Tu devrais valider la ligne encrypt passwords = yes .....
Essais de refaire un smb.conf moins touffus car c'est galère à lire ....sinon tu peux t'inspiré du mien...

#Fichier de configuration Samba : 04/02 /2007

[global]
#Nom du groupe de travail ou domaine
workgroup = Workgroup
#Nom netbios du serveur Samba
;netbios name = Gerard
#Commentaire affiché lors du parcours reseau
server string = serveur Gerard
#System d'impression utilisé
printing = cups
printcap name = cups
#Configuration des logs du serveur
log file = /var/log/samba/log.%m
max log size  = 50
#IP ou reseaux autorises si allow ou inverse si deny
;hosts deny = all
hosts allow = 192.168.0.
#mode d'authentification user==> mot de passe ou share ==> guest
security = user
;guest ok = yes
#Configuration des mots de passe
encrypt passwords = yes
#correspondance des codes caracteres
;client code page = 850
;character set = UTF-8
;show add printer wizard = yes
;printer admin = root
cups options = raw
#Ameliore les connections
;socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

[homes]
comment = Repertoires personnels
valid users = %S
#empeche le bit d'execution
map archive = no
browseable = no
read only = no

[printers]
;use client driver = no
writable = yes
;valid users = Gerard,Gwen
printable = yes
path = /var/spool/samba
;public = yes

#[print$]
;comment = pilotes d'imprimantes
;path = /var/lib/samba/driver

grosminet

si tu fais un ping sur le serveur fedora, je suppose que la réponse est correct.
il faut que le deux machines appartient au meme groupe de travail soit le onglet systeme du poste de travail.
il faut savoir que la couche Xp2 non professionnel est reduite et peu efficace.
la résolution peut s'améliorer en decommentant la ligne

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
wins support = yes

generalement aussi le serveur samba n'est pas actif
il faut le lancer par service smb start
service smb status
on peut aussi l'activer au demarrage par la commande
chkconfig --level 3 smb on
chkconfig --level 5 smb on