Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 09/11/2009, à 19:06

chat2gouttieres

[Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

Bonjour,

Ça fait plusieurs jours, voir plusieurs mois qu'il m'est impossible de partager des dossiers sur mon réseau. Pourtant c'est bête comme tout, mais ça ne fonctionne pas. Ça a commencé avec Ubuntu 9.04, alors qu'avant, je n'ai jamais eu aucun souci.

J'ai un PC A sous Ubuntu 9.10 et un PC B sous Ubuntu 9.10 aussi. J'ai besoin de partager des dossiers et sur l'un, et sur l'autre.

Je ne sais pas mais normalement, on choisit un dossier, un clic droit, et on partage. Même en mettant des permissions lecture/écriture à tout le monde ça ne fonctionne pas. Les utilisateurs sur le PC A sont créés aussi sur le PC B. Donc je pense avoir fait la bonne manip, mais hélas, lorsque je vais dans "Réseau" > "Réseau Windows", j'ai inlassablement ce message d'erreur :

Impossible de monter l'emplacement
L'obtention de la liste des partages du serveur a échoué

Je ne me vois même pas sur le réseau hmm

Alors, j'ai suivi des dizaines de sujets, très peu ont trouvé une réponse, mais à chaque fois elles ne correspondaient pas à mon cas et ne réglaient aucunement mon problème. J'avoue être dégoûté de devoir batailler avec quelque chose d'aussi simple, même sous Windows.

Je vous donne mes fichiers de configuration (qui ont été modifiés au fil des manipulations diverses et variées que j'ai tenté pour résoudre le problème) pour que vous puissiez y voir plus clair.

PC A :

/etc/samba/smb.conf :

# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# 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 most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
	workgroup = MAISON

# server string is the equivalent of the NT Description field
	server string = %h server (Samba, Ubuntu)

# 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 hosts

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
	log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
	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/Samba3-HOWTO/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

	obey pam restrictions = yes

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

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
	passwd program = /usr/bin/passwd %u
	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

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

# This option controls how unsuccessful authentication attempts are mapped 
# to anonymous connections
	map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

########## 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

############ 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/Samba3-HOWTO/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

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;	usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
	usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares.  This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = 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 = 0755

# 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 = 0755

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.  Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# 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
;   read only = yes
;   share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
	comment = All Printers
	browseable = no
	path = /var/spool/samba
	printable = yes
;	guest ok = no
;	read only = yes
	create mask = 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.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   read only = yes
;   locking = no
;   path = /cdrom
;   guest ok = 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

	map acl inherit = yes

[RAZ]
	path = /media/Divers/RAZ
	writeable = yes
;	browseable = yes
	guest ok = yes

/etc/hosts :

127.0.0.1	localhost
127.0.1.1	alfred-desktop
192.168.1.100	alfred-desktop
192.168.1.150	SERVEUR-UBUNTU

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

/etc/hostname :

alfred-desktop

PC B :

/etc/samba/smb.conf :

# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# 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 most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = MAISON

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# 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

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   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/Samba3-HOWTO/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

   obey pam restrictions = yes

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

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

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

# This option controls how unsuccessful authentication attempts are mapped 
# to anonymous connections
   map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

########## 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

############ 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/Samba3-HOWTO/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

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares.  This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = 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

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.  Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# 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
;   read only = yes
;   share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 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.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   read only = yes
;   locking = no
;   path = /cdrom
;   guest ok = 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

/etc/hosts :

127.0.0.1	localhost
127.0.1.1	SERVEUR-UBUNTU
192.168.1.150	SERVEUR-UBUNTU
192.168.1.100	alfred-desktop

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

/etc/hostname :

SERVEUR-UBUNTU

Dernière modification par chat2gouttieres (Le 10/11/2009, à 12:03)


Il y a 3 grands mensonges en informatique : ça fonctionne, c'est compatible, ça sort bientôt :p

Hors ligne

#2 Le 09/11/2009, à 20:01

richardsantoro

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

T'es deux machines se ping-t-elles?

Arrive tu a monter les dossiers concernés via raccourcis, se connecter à un serveur ?


Logiciels incontournables => Terminator : terminal divisible; GNS3 : Simulation de réseau avec IOS Cisco; DIA : Editeur de diagrammes pour réseaux et autres; VirtualBox : Emulateur d'ordinateur

Hors ligne

#3 Le 09/11/2009, à 20:14

chat2gouttieres

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

Alors oui, mes deux machines se ping mutuellement.

En faisant "Se connecter à un serveur", ça ne fonctionne pas, ni d'un côté, ni de l'autre, message d'erreur par exemple :

Impossible d'afficher l'emplacement « smb://MAISON;alfred@192.168.1.150/partage/Partage »
Impossible de monter le partage Windows.

J'ai essayé plusieurs combinaisons pour rentrer les informations de connexion, rien n'y fait.

Déjà aussi, je ne me vois pas dans le réseau. À partir du moment où je partage un dossier, je devrais apparaître.

Dernière modification par chat2gouttieres (Le 09/11/2009, à 20:15)


Il y a 3 grands mensonges en informatique : ça fonctionne, c'est compatible, ça sort bientôt :p

Hors ligne

#4 Le 09/11/2009, à 20:27

titi89

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

bonjour,
as tu essayé le menus raccourcis---->se connecter à un serveur
type de service:partage windows
dans serveur tu tapes :192.168.0.150
tu coches "ajouter un signet"
dans nom du signet tu mets ce que tu veux ex:PC1
tu ne tiens pas compte du message d'erreur
dans raccourcis tu ouvre et tu dois voir PC1 tu click dessus
que se passe t'il?

Hors ligne

#5 Le 09/11/2009, à 20:32

chat2gouttieres

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

Pareil, même message.


Il y a 3 grands mensonges en informatique : ça fonctionne, c'est compatible, ça sort bientôt :p

Hors ligne

#6 Le 09/11/2009, à 20:36

titi89

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

tu as bien pc1 dans les signets
et tu as bien partagé un dossier sur les 2 ordis

Hors ligne

#7 Le 09/11/2009, à 20:40

chat2gouttieres

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

oui


Il y a 3 grands mensonges en informatique : ça fonctionne, c'est compatible, ça sort bientôt :p

Hors ligne

#8 Le 09/11/2009, à 21:06

titi89

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

tu peux essayé de partager un autre dossier sur chaque ordi click droit options de partage et autoriser toutes les permissions et créer partage puis redémarrer les ordis je suis pas spécialiste des partages j'ai jamais été foutu de partager des dossiers depuis feisty et depuis jaunty et karmic comme cela ,cela fonctionne.
si ça marche pas faut quelqu'un de plus calé smile

Hors ligne

#9 Le 09/11/2009, à 23:29

chat2gouttieres

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

C'est justement le cas sur ces dossiers, ils ont toutes les permissions.


Il y a 3 grands mensonges en informatique : ça fonctionne, c'est compatible, ça sort bientôt :p

Hors ligne

#10 Le 10/11/2009, à 00:10

chat2gouttieres

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

C'est justement le cas sur ces dossiers, ils ont toutes les permissions.


Il y a 3 grands mensonges en informatique : ça fonctionne, c'est compatible, ça sort bientôt :p

Hors ligne

#11 Le 10/11/2009, à 10:11

titi89

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

désolé je ne peux t'aider plus
en fait j'avais le même problême jusqu'à hardy sans que j'ai jamais trouvé de solution
j'utilisais lanshark la version hardy fonctionne sur jaunty pas essayé sur karmic trouvé sur getdeb
peut-être une solution temporaire?
http://old.getdeb.net/search.php?search … s=lanshark

Hors ligne

#12 Le 10/11/2009, à 10:28

Grünt

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

Pourquoi tu ne tentes pas avec nfs, vu que (si j'ai bien compris) les deux PC sont sous Ubuntu? C'est la solution la plus logique wink


Red flashing lights. I bet they mean something.

Hors ligne

#13 Le 10/11/2009, à 10:57

chat2gouttieres

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

Merci titi, mais je ne suis pas très chaud pour getdeb.

Grunt : Non parce que j'ai des PCs portables en wifi qui se connecte en réseau qui sont soit sous XP, soit sous Vista, donc j'ai absolument besoin du partage samba.

Dernière modification par chat2gouttieres (Le 10/11/2009, à 11:03)


Il y a 3 grands mensonges en informatique : ça fonctionne, c'est compatible, ça sort bientôt :p

Hors ligne

#14 Le 10/11/2009, à 11:47

mloupiot

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

Bonjour,
les dossiers partagés seraient-ils sur des disques usb ?

Hors ligne

#15 Le 10/11/2009, à 11:54

chat2gouttieres

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

Alors j'avance un peu. Le problème ne vient pas du tout de samba. Ce matin j'ai lancé firestarter comme ça, par hasard, parce qu'il était installé sur 9.04, et que j'ai fait une distro upgrade. Du coup, il est encore là avec ufw qui le remplace.

Après avoir gratté un petit peu dans /etc/hosts/ sur PC A, je reboot et je fais un petit coup de "Raccourcis" >> "Réseau". Pam ! Une alerte dans firestarter oO Il m'a bloqué en sortie sur le réseau local (c'est bien mon IP locale, port : 137, protocole : UDP, service : Samba (SMB)).
C'est quoi cette absurdité ???????? Je sais encore où je mets les pieds, j'ai pas besoin d'être protégé comme ça, ou alors qu'on m'en informe ! Mais c'est ridicule !!! Voilà comment perdre 2 jours pour des c*****ies.
Bon, je vais sur PC B sous Ubuntu, je désactive ufw car là c'était une installation (pas de MAJ) de 9.10, et j'arrive pas à accéder à PC B. Re-belote ! Une alerte sur PC A dans firestarter, même port, même service mais pas même IP. Bon ! j'autorise l'IP, magie magie, j'arrive à accéder à PC B et PC B accède à PC A.
Donc conclusion, si vous voulez partager des dossiers sous Ubuntu, depuis 9.04, vous devez non seulement créer vos partages, mais, aussi, maîtriser firestarter/ufw, pas userfriendly pour un sou ce qui est censé être le cas pour Ubuntu. Gros coup de gueule ! À revoir ça chez Canonical !

À l'heure de l'UPnP (DLNA ou non), à l'heure où toute la maison est censée être communiquante, il serait tant qu'ils se mettent à développer ce côté.

Bon, étant donné que j'avais lu des dizaines de sujets sur CE même problème, et que très peu avaient une solution (qui en tout cas ne fonctionnait pas chez moi), je pense qu'il faudrait limite épinglé ce sujet quelques temps.

Dernière modification par chat2gouttieres (Le 10/11/2009, à 12:01)


Il y a 3 grands mensonges en informatique : ça fonctionne, c'est compatible, ça sort bientôt :p

Hors ligne

#16 Le 10/11/2009, à 11:55

chat2gouttieres

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

@mloupiot : non


Il y a 3 grands mensonges en informatique : ça fonctionne, c'est compatible, ça sort bientôt :p

Hors ligne

#17 Le 10/11/2009, à 14:00

titi89

Re : [Résolu] Impossible de partager un dossier Ubuntu <--> Ubuntu

j'avais oublié
mais j'ai installé firestarter sous karmic et autorisé les connexions des autres pcs
ce qui explique surement cela smile
de toute façon au début de chaque installation j'ai pris l'habitude de lancer firestarter et
de surveiller les bloquages et de les autoriser lorsque c'est nécessaire.
ceci dit j'ai pas déactivé le parefeu
avec ufw impossible de partager ma connexion internet c'est pourquoi j'espère que firestarter
restera encore longtemps.
heureux que tu avances
@+

Hors ligne