Résolu le 12-12-18 Accés au Réseau WINDOWS ?

Assistance concernant Linux Mint
Avatar du membre
DUME06
Messages : 156
Enregistré le : sam. 11 févr. 2017 14:30
Localisation : Alpes Maritimes

Accés au Réseau WINDOWS ?

Message par DUME06 »

Bonjour à vous tous
Depuis mon PC LINUX Mint 18.1 serena ; j’accède bien à mon réseau Windows 7. Je vois bien le MODEM(Livebox) et les 2 PC Windows (Workgroup). Tous les dossiers du PC interrogé sont bien visibles; mais quand je les ouvre, ils sont tous marqués ' vides ' ​????
Avec ce PC ; J'utilise très bien mon imprimante " HP ENVY 4500 series (réseau) "

A partir de ce lien :
https://doc.ubuntu-fr.org/samba#ports_l ... mb_et_cifs" onclick="window.open(this.href);return false;

j'ai essayé de comprendre ? Mes manips correspondent bien à la démo; mais je n'y ai pas retrouvé le PB (dossier vide!)
Peut-être qu'une explication plus simple de votre part ; éclairera ma toute petite cervelle !!!!

En attendant je vous souhaite un agréable week-end
Amicalement Votre
DUME06
PC: ASUS N61vg - ram 4Go - Disk SSD Samsung 500Go = LINUX Mint 21.1 Vera 64bits Xfce.
ACER Aspire - ram 4Go - Disk SSD Sandisk 120Go = LINUX Mint 20.2 uma 64bits Xfce.
et un PACKARD-BELL easy-note ram 4Go Disk HDD 750Go = LINUX Mint 21.1 Vera 64 bits Xfce.
Imprimante HP-Envy 4500 series

' Le propre de la médiocrité est de se croire supérieur '

Avatar du membre
roromint
Messages : 2728
Enregistré le : dim. 28 févr. 2016 21:09
Localisation : ath

Re: Accés au Réseau WINDOWS ?

Message par roromint »

bonjour

as tu déjà recherche du moteur google ? oui ou non ? si non je te donne mots clés sur la google : "comment faire installer un samba ubuntu" (fr) ou installing samba ubuntu (ENglish) ou si oui tu sais apprendre le seule :)

https://help.ubuntu.com/lts/serverguide ... erver.html" onclick="window.open(this.href);return false;
https://www.youtube.com/watch?v=e2dd_Omd2OA" onclick="window.open(this.href);return false;

bien à toi
le proF roromint
cordialement,
Ro.
-------------------------------------------------------
PS à lire du attentif pour mon handicap : je suis malentendant Étant dyslexique, j'ai des problèmes quant à la rédaction de messages en français courant. Je vous prie dès lors d'accepter toutes mes excuses si mes interventions peuvent vous paraître étranges et je vous remercie d'avance pour votre compréhension.
PS: pour les membres, ne pas faire la message privé de moi svp ! merci

Avatar du membre
DUME06
Messages : 156
Enregistré le : sam. 11 févr. 2017 14:30
Localisation : Alpes Maritimes

Re: Accés au Réseau WINDOWS ?

Message par DUME06 »

Bonjour ROROMINT
Tout d'abord merci infiniment pour ta célérité et tes conseils.
Si j'ai bien compris; il me faut installer " samba " sur mon PC LINUX et ensuite le paramétrer afin de partager mes fichiers Windows....?
Avant toute manip, je vais bien revisionner la vidéo Youtube et ensuite procéder à l'install.
En te renouvelant tous mes remerciements; je te souhaite un très agréable week-end.
Bien amicalement
DUME06
Modifié en dernier par zeb le sam. 11 mars 2017 14:44, modifié 1 fois.
Raison : suppression d'une citation reprenant à 100% le message précédent.
PC: ASUS N61vg - ram 4Go - Disk SSD Samsung 500Go = LINUX Mint 21.1 Vera 64bits Xfce.
ACER Aspire - ram 4Go - Disk SSD Sandisk 120Go = LINUX Mint 20.2 uma 64bits Xfce.
et un PACKARD-BELL easy-note ram 4Go Disk HDD 750Go = LINUX Mint 21.1 Vera 64 bits Xfce.
Imprimante HP-Envy 4500 series

' Le propre de la médiocrité est de se croire supérieur '

Avatar du membre
DUME06
Messages : 156
Enregistré le : sam. 11 févr. 2017 14:30
Localisation : Alpes Maritimes

Re: Accés au Réseau WINDOWS ?

Message par DUME06 »

Bonjour ROROMINT
Suite à tes conseils; j'ai bien installé SAMBA sur mon PC 3 Linux.
=> Ouverture WORKGROUP => Mot de passe OK => PC 2 Windows => Ouverture dossiers = Tous Vides !!
Donc aucun changement constaté .....
Après l'installation SAMBA; je ne trouve pas dans les PRG le module qui je pense devrait me permettre d'effectuer sa configuration ??? Est-ce normal ?? ou bien faut-il installer d'autre paquets SAMBA??

=> A titre indicatif :
PC1 et PC2 sous Win7 sont parfaitement accessibles entre eux en écriture & lecture.

En te souhaitant une bonne journée; bien amicalement
DUME06
PC: ASUS N61vg - ram 4Go - Disk SSD Samsung 500Go = LINUX Mint 21.1 Vera 64bits Xfce.
ACER Aspire - ram 4Go - Disk SSD Sandisk 120Go = LINUX Mint 20.2 uma 64bits Xfce.
et un PACKARD-BELL easy-note ram 4Go Disk HDD 750Go = LINUX Mint 21.1 Vera 64 bits Xfce.
Imprimante HP-Envy 4500 series

' Le propre de la médiocrité est de se croire supérieur '

Avatar du membre
WarLocG
Messages : 96
Enregistré le : mer. 20 avr. 2016 18:39
Localisation : Belgique

Re: Accés au Réseau WINDOWS ?

Message par WarLocG »

faudrait que tu nous montres le contenu de /etc/samba/smb.conf (la partie avec ton partage). Egalement tu peux tester avec smbclient, lorsque tu es connecté tu peux faire ls dans l'invite pour afficher le contenu du/des dossier(s).

Bien à toi.

Avatar du membre
DUME06
Messages : 156
Enregistré le : sam. 11 févr. 2017 14:30
Localisation : Alpes Maritimes

Re: Accés au Réseau WINDOWS ?

Message par DUME06 »

Bonjour WarLocG
Tout d'abord, merci infiniment pour ta célérité et tes conseils...
Comme tu me le demandes; tu trouveras ci-dessous le contenu de mon fichier ' smb.conf '
Je suis un tout nouvel utilisateur de LINUX et j'ai beaucoup à apprendre.....

================================================================>

Code : Tout sélectionner

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
##
# 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. 

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

[global]

## Browsing/Identification ###

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

# 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

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

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

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

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or '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

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

# 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

# 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

# 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

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

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

[global]

## Browsing/Identification ###

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

# 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

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

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

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

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or '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

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

# 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

# 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

# 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
<<<===============================================================
Je te renouvelle mes remerciements et te souhaite une bonne journée
Bien Amicalement
DUME06
PC: ASUS N61vg - ram 4Go - Disk SSD Samsung 500Go = LINUX Mint 21.1 Vera 64bits Xfce.
ACER Aspire - ram 4Go - Disk SSD Sandisk 120Go = LINUX Mint 20.2 uma 64bits Xfce.
et un PACKARD-BELL easy-note ram 4Go Disk HDD 750Go = LINUX Mint 21.1 Vera 64 bits Xfce.
Imprimante HP-Envy 4500 series

' Le propre de la médiocrité est de se croire supérieur '

Avatar du membre
WarLocG
Messages : 96
Enregistré le : mer. 20 avr. 2016 18:39
Localisation : Belgique

Re: Accés au Réseau WINDOWS ?

Message par WarLocG »

Merci DUME06, mais pourrais-tu placer tout ce contenu entre balise code stp ?

Code : Tout sélectionner

[code]ton contenu
ou

Code : Tout sélectionner

...
ton contenu
...
[/code]
Je n'ai pas vu de partage dans ta conf (autre que ceux par défaut), tu ne partageais aucun dossier, tu voulais juste accéder au partage sous Win c'était bien ca ?

As-tu essayé la commande smbclient deja ?

Edit: Comme tu viens pour obtenir de l'assistance, tu pourrais également mettre ta configuration LM + matérielle dans ta signature afin qu'on puisse t'aider au mieux sans avoir à te redemander quel système, quel bureau, quel matos, etc ... (désolé debitant, mon coté modo qui fait surface ... ^^)

zeb
Messages : 16473
Enregistré le : ven. 19 juin 2015 22:13
Localisation : plus ici

Re: Accés au Réseau WINDOWS ?

Message par zeb »

Salut DUME06 ;)
Je viens de modifier ton message (mise en forme) j'ai mis en balises "code" le résultat que te demandait WarLocG, plus court comme ça ;)
J'ai aussi supprimé sa citation, car elle reprend son message dans son intégralité, et vu que tu y a répondu de suite, elle ne sert à rien :D

Voili, merci ;)

Avatar du membre
DUME06
Messages : 156
Enregistré le : sam. 11 févr. 2017 14:30
Localisation : Alpes Maritimes

Re: Accés au Réseau WINDOWS ?

Message par DUME06 »

Re-Bonjour WarLocG
Je viens de voir que ZEBULON avait placé le contenu entre les balises comme tu me le demandais.
Je te confirme bien que je veux accéder à mes fichiers présents sur les PC 1 et 2 WIN7.
En ce qui concerne la commande ' smbclient ' ; j'ai bien essayé ==>

dume@dume-Satellite-M70 ~ $ smbclient
WARNING: The "syslog" option is deprecated
Utilisation: smbclient [-?EgBVNkPeC] [-?|--help] [--usage]
[-R|--name-resolve=NAME-RESOLVE-ORDER] [-M|--message=HOST]
[-I|--ip-address=IP] [-E|--stderr] [-L|--list=HOST]
[-m|--max-protocol=LEVEL] [-T|--tar=<c|x>IXFqgbNan]
[-D|--directory=DIR] [-c|--command=CHAÎNE] [-b|--send-buffer=BYTES]
[-t|--timeout=SECONDS] [-p|--port=PORT] [-g|--grepable]
[-B|--browse] [-d|--debuglevel=DEBUGLEVEL]
[-s|--configfile=CONFIGFILE] [-l|--log-basename=LOGFILEBASE]
[-V|--version] [--option=name=value]
[-O|--socket-options=SOCKETOPTIONS] [-n|--netbiosname=NETBIOSNAME]
[-W|--workgroup=WORKGROUP] [-i|--scope=SCOPE] [-U|--user=USERNAME]
[-N|--no-pass] [-k|--kerberos] [-A|--authentication-file=FILE]
[-S|--signing=on|off|required] [-P|--machine-pass] [-e|--encrypt]
[-C|--use-ccache] [--pw-nt-hash] service <password>
dume@dume-Satellite-M70 ~ $


Mais je m'en excuse. Je ne sais pas comment en tirer profit (manque d'expérience)
Encore merci pour ton aide. Bien amicalement
DUME06
PC: ASUS N61vg - ram 4Go - Disk SSD Samsung 500Go = LINUX Mint 21.1 Vera 64bits Xfce.
ACER Aspire - ram 4Go - Disk SSD Sandisk 120Go = LINUX Mint 20.2 uma 64bits Xfce.
et un PACKARD-BELL easy-note ram 4Go Disk HDD 750Go = LINUX Mint 21.1 Vera 64 bits Xfce.
Imprimante HP-Envy 4500 series

' Le propre de la médiocrité est de se croire supérieur '

Avatar du membre
roromint
Messages : 2728
Enregistré le : dim. 28 févr. 2016 21:09
Localisation : ath

Re: Accés au Réseau WINDOWS ?

Message par roromint »

installer samba samba-common system-config-samba mais tu as déjà installer un samba ?
cordialement,
Ro.
-------------------------------------------------------
PS à lire du attentif pour mon handicap : je suis malentendant Étant dyslexique, j'ai des problèmes quant à la rédaction de messages en français courant. Je vous prie dès lors d'accepter toutes mes excuses si mes interventions peuvent vous paraître étranges et je vous remercie d'avance pour votre compréhension.
PS: pour les membres, ne pas faire la message privé de moi svp ! merci

Répondre