serveur samba n'est pas accessible, vous ne disposez peut etre pas des - réseaux et sécurité - Linux et OS Alternatifs
Marsh Posté le 18-05-2006 à 11:21:07
Bonjour,
le debut de ton smb.conf nous donnerais des indications sur tes modes de sésurité (share, user....)
As tu ajouter les utilisateurs (smbpasswd) de TOUS tes utilsateurs?
Par ailleurs des fichiers de log (var/log/samba/) sont tres utiles pour trouver la cause de tes erreurs....
++
Marsh Posté le 18-05-2006 à 12:49:32
Comme j'ai dit : j'arrive à me connecter avec un PC Windows avec un login /passwd du serveur samba.
Cependant j'utilise samba en mode : securite=user
voici un bout de mon log smbd :
smbd version 2.2.12 started.
Copyright Andrew Tridgell and the Samba Team 1992-2002
[2006/05/18 01:13:25, 0] printing/print_cups.c:cups_printer_fn(107)
Unable to connect to CUPS server localhost - Connection refused
[2006/05/18 09:18:53, 0] smbd/server.c:main(791)
smbd version 2.2.12 started.
Copyright Andrew Tridgell and the Samba Team 1992-2002
[2006/05/18 09:18:54, 0] printing/print_cups.c:cups_printer_fn(107)
Unable to connect to CUPS server localhost - Connection refused
[2006/05/18 12:24:43, 0] smbd/server.c:main(791)
smbd version 2.2.12 started.
Copyright Andrew Tridgell and the Samba Team 1992-2002
[2006/05/18 12:24:43, 0] printing/print_cups.c:cups_printer_fn(107)
Unable to connect to CUPS server localhost - Connection refused
et mon smb.conf :
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4
workgroup = workgroup
# server string is the equivalent of the NT Description field
server string = Serveur de donnees
share modes = yes
netbios name = serveur
name resolve order = wins host lmhosts bcast
# 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, sysv, plp, lprng, aix, hpux, qnx
; printing = bsd
# 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/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 = user
# 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>
# Note: Do NOT use the now deprecated option of "domain controller"
# This option is no longer implemented.
# 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
# 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 = /usr/local/etc/smb.conf.%m
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
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.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 built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no
# Client codepage settings
# for Greek users
; client code page=737
# for European users (Latin 1)
; client code page=850
# for European users (Latin 2)
; client code page=852
# for Icelandic users
; client code page=861
# for Cyrillic users
; client code page=866
# for Japanese Users
; client code page=932
; coding system=cap
# for Simplified Chinese Users
; client code page=936
; coding system=cap
# for Korean Users
; client code page=949
; coding system=cap
# for Traditional Chinese Users
; client code page=950
; coding system=cap
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writeable = yes
valid user only
# Un-comment the following two lines to add a recycle bin facility to a samba share
# NOTE: It currently doesn't work with the [homes] virtual share, use a regular share instead
; vfs object = /usr/local/lib/samba/recycle.so
; vfs options= /usr/local/etc/recycle.conf.default
# 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
; writeable = 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 = /var/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
; writeable = 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
; writeable = 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
; writeable = 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.
[utilisateur]
comment = PC Directories
path = /usr/home/%U
valid users
public = no
writeable = 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 writeable 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
; writeable = yes
; printable = no
# Un-comment the following two lines to add a recycle bin facility to a samba share
; vfs object = /usr/local/lib/samba/recycle.so
; vfs options= /usr/local/etc/recycle.conf.default
# 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 writeable 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
; writeable = yes
; printable = no
; create mask = 0765
#######################
voilà en espèrant que ça apporte des réponses mais j'en doute !!! ;-(
Marsh Posté le 19-05-2006 à 12:02:49
je vois qu'il n'y a pas de solutions !!!
J'ajoute que maintenant je n'arrive pas à accèder au group de travail mais j'arrive à accèder à l'ordinateur windows (de windows à windows) lorsque je saisis soit son IP soit son nom.
par contre je n'ai pas d'accès au serveur samba ni par l'adresse IP ni par son nom.
C'est fou cette histoire car sur mes 3 machines sous XP j'ai une machine qui se connecte bien au serveur samba en passant par le favoris réseau mais les deux autres pc ont un message ; le compte n'est pas autorisé à se connecter depuis cette station.
Merci de faire des suggessions je prends tous ce qui vient lol
Marsh Posté le 19-05-2006 à 16:58:26
J'ai remarqué que sur les 2 PC WINDOWS XP dans les services : le service ouverture de session réseau ne fonctionne pas. Il ne démarre ni sur le WinXP Pro ni sur le WIN xp Home alors que sur WIN XP PRO qui arrive à se logger sur les 2 serveurs samba a ce service qui est démarré !:!!!
Peut etre un début de solution NON ?
Avez vous des infos la dessus ?
Marsh Posté le 04-06-2006 à 16:24:03
En ce qui concerne les XP home tu peux laisser tomber, tu ne pourra pas ouvrir de session. Pour les XP pro est ce que tu as modifier la base de registre avant de faire la jonction à ton domaine ?
Marsh Posté le 18-05-2006 à 10:03:33
Bonjour j'ai un gros problème réseau entre un serveur Samba et un ou plusieurs postes Windows XP (pro et home).
Le problème réside dans le message suivant :
"Serveur" n'est pas accessible. Vous ne disposez peut etre pas des autorisations necessaires pour utiliser cette ressource réseau. Contacter l'administrateur de ce serveur pour savoir si vous disposez des autorisations d'accès. Le chemin reseau n'a pas été trouvé.
Or, il se trouve que j'ai un PC Windows XP Pro qui a accès au serveur Samba. D'ailleurs, j'ai installé 2 serveurs samba sur freebsd 6.0 et sur freebsd 5.4 ils ont chacun un workgroup différent et ce pc windows arrive à se connecter et à ouvrir une session.
Les autres pc sous windows XP, qu'ils soient sous le meme workgroup ou non, ce terrible message apparait.
Alors pour éviter les réponses inutiles :
oui je suis sous le meme masque réseau
oui je suis sur la meme plage IP
oui je vois les serveurs samba depuis les windows dans le voisinage réseau (favoris réseaux)
Non je n'ai pas de firewall (ni sur les serveurs ni sur les postes windows)
Je pensais avoir bcp d'expérience mais là je PANNE...
Merci à ceux qui veullent bien se pencher sur le problème