Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
1441 connectés 

 


 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

petit souci samba...

n°739470
kaillou38
mouton à numéro
Posté le 10-10-2005 à 16:43:45  profilanswer
 

bonjour,
 
j'ai reinstallé recemment mon serveur, et pour essayer de faire ca bien, j'ai choisi mes packages a la main (c'est vrai que ca boot plus vite)
 
par contre j'ai un probleme avec samba, qui avec le meme fichier de config que precedemment, et ben il chie un peu dans la colle :(
 
voici mon fichier de config :

Citation :


[global]
 
## Browsing/Identification ###
 
# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = MSHOME
 
# server string is the equivalent of the NT Description field
   server string = %h  
 
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its 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
 
# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no
 
# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast
 
 
#### Debugging/Accounting ####
 
# 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 = 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 #######
 
# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/ServerType.html in the samba-doc
# package for details.
   security = user
 
# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
   encrypt passwords = true
 
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam guest
 
   obey pam restrictions = yes
 
;   guest account = nobody
   invalid users = root
 
# 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 = no
 
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Augustin Luton <aluton@hybrigenics.fr> for
# sending the correct chat script for the passwd program in Debian Potato).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
 
# 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 = no
 
 
########## Printing ##########
 
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
;   load printers = yes
 
# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap
 
# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;   printing = cups
;   printcap name = cups
 
# When using [print$], root is implicitly a 'printer admin', but you can
# also give this right to other users to add drivers and set printer
# properties
;   printer admin = @ntadmin
 
 
######## File sharing ########
 
# Name mangling options
;   preserve case = yes
;   short preserve case = yes
 
 
[musique]
comment = share acces granted to everyone
path = /media/musique
browsable = yes
writable = yes
create mask = 0775
#means that the creator of the file has rwx rights on it, the group r-x and others r--
 
directory mask = 0775
#same meaning but for directories
 
mangled names = yes
#converts names in a DOS/Windows manner, with eight characters for the name and three for the extension
 
preserve case = no
#do no take case into account
 
 
[divers]
comment = share acces granted to everyone
path = /media/media/divers
browsable = yes
writable = yes
create mask = 0775
#means that the creator of the file has rwx rights on it, the group r-x and others r--
 
directory mask = 0775
#same meaning but for directories
 
mangled names = yes
#converts names in a DOS/Windows manner, with eight characters for the name and three for the extension
 
preserve case = no
#do no take case into account
 
[film]
comment = share acces granted to everyone
path = /media/media/film
browsable = yes
writable = yes
create mask = 0775
#means that the creator of the file has rwx rights on it, the group r-x and others r--
 
directory mask = 0775
#same meaning but for directories
 
mangled names = yes
#converts names in a DOS/Windows manner, with eight characters for the name and three for the extension
 
preserve case = no
#do no take case into account
 
 
 
############ 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
 
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
   socket options = TCP_NODELAY
 
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
 
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
;   domain master = auto
 
# 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
 
#======================= Share Definitions =======================
 
[homes]
   comment = Home Directories
   browseable = no
 
# By default, the home directories are exported read-only. Change next
# parameter to 'yes' if you want to be able to write to them.
   writable =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
 
# 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
;   writable = no
;   share modes = no
 
[printers]
   comment = All Printers
   browseable = no
   path = /tmp
   printable = yes
   public = no
   writable = no
   create mode = 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.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
;   write list = root, @ntadmin
 
# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   writable = no
;   locking = no
;   path = /cdrom
;   public = yes
 
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
#       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
;   preexec = /bin/mount /cdrom
;   postexec = /bin/umount /cdrom
 


 
j'ai donc choisi une connexion par utilisateur, sauf que depuis un poste windows, je met mon login /mdp qui marche puisque j'arrive me connecter en local avec, et ca ne veut pas...
 
donc j'ai eu l'idée d'aller voir les log, mais personnelement, ca m'avance pas beaucoup :(
 

Citation :


[2005/10/09 01:00:49, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/09 01:00:49, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/09 01:00:49, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2005/10/09 04:57:55, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/09 04:57:55, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/09 04:57:55, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2005/10/09 04:57:55, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/09 04:57:55, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/09 04:57:55, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2005/10/09 05:13:51, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/09 05:13:51, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/09 05:13:51, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2005/10/09 06:05:26, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/09 06:05:26, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/09 06:05:26, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2005/10/10 01:26:43, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/10 01:26:43, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/10 01:26:43, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2005/10/10 01:26:55, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/10 01:26:55, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/10 01:26:55, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2005/10/10 02:07:02, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/10 02:07:02, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/10 02:07:02, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2005/10/10 02:07:07, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/10 02:07:07, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/10 02:07:07, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2005/10/10 02:07:15, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/10 02:07:15, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/10 02:07:15, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2005/10/10 02:07:29, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2005/10/10 02:07:29, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer
[2005/10/10 02:07:29, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)


 
 
et je retrouve pas le tuto qui m'avait aidé a mettre en place mon samba la premiere fois :(
 
 
et j'arrive a me connecter depuis le serveur les partage windows des autres postes...
 


---------------
ras
mood
Publicité
Posté le 10-10-2005 à 16:43:45  profilanswer
 

n°739474
Phoenix
Posté le 10-10-2005 à 16:56:53  profilanswer
 

T'es en sécurity = user donc déja la 1ère première étape c'est de vérifier que t'as un utilisateur Unix, identique à ton utilisateur windows.
2 - Tu ajoute ton utilisateur Unix coté samba (smbpassword -a toto) et tu lui met le même password.

n°739476
kaillou38
mouton à numéro
Posté le 10-10-2005 à 16:57:45  profilanswer
 

ah voila, ca doit etre l'etape 2 que j'ai pas, je m'en doutais un peu que ce soit un truc du genre


---------------
ras
n°739482
kaillou38
mouton à numéro
Posté le 10-10-2005 à 17:11:02  profilanswer
 

c'est bon, c'etait bien ca
 
merci


---------------
ras
n°739495
Phoenix
Posté le 10-10-2005 à 17:22:48  profilanswer
 

padquoi  ;)


Aller à :
Ajouter une réponse
 

Sujets relatifs
Combat de titan partage samba et windows 2000 serverpetit souci partman
session sambasamba et user windows
[samba] lenteur à d'ouverture du partage via XP[Samba] probleme dans la config de la corbeille reseau
petit probleme sur whax (linux live version)!Samba, AD et Kerberos
probleme avec le serveur samba 
Plus de sujets relatifs à : petit souci samba...


Copyright © 1997-2022 Hardware.fr SARL (Signaler un contenu illicite / Données personnelles) / Groupe LDLC / Shop HFR