Willkommen Gast. Bitte einloggen oder registrieren. Haben Sie Ihre Aktivierungs E-Mail übersehen?
08.05.2021, 13:04:22

.
Einloggen mit Benutzername, Passwort und Sitzungslänge

Mitglieder
Statistiken
  • Beiträge insgesamt: 734027
  • Themen insgesamt: 59145
  • Heute online: 580
  • Am meisten online: 2287
  • (22.01.2020, 19:20:24)
Benutzer Online

Autor Thema:  Netzwerk: Windows 7 mit Windows XP oder Linux verbinden  (Gelesen 58246 mal)

0 Mitglieder und 1 Gast betrachten dieses Thema.

DeVIL-I386Threadstarter

  • Administrator
  • *****
Re: Netzwerk: Windows 7 mit Windows XP oder Linux verbinden
« Antwort #15 am: 24.06.2016, 02:05:49 »
Ich werde mal am Wochenende schauen, ob mein neuer Rechner (mit vorinstalliertem Windows 10) bei der Datenfreigabe mit Linux-Rechnern Probleme hat.
Und wenn ja, ob ich dafür eine einfache Problemlösung finde.



Ich verstehe nicht, warum Du die Heimnetzgruppe völlig ausschaltest
Weil so der Zugriff in beide Richtungen möglich war.



Den Zugriff auf den Win10-PC habe ich entsprechend
http://www.tipps-archiv.de/von-linux-mint-auf-eine-windows-freigabe-zugreifen.html
eingestellt.
Jetzt kann ich zwar auf die freigegebenen Windows-Ordner zugreifen, sehe aber den Linux-Rechner nicht.
Also keine zufriedenstellende Lösung.



Unter Linux Mint 18 MATE 64-Bit Beta hapert es ja schon daran, dass das Paket caja-share nicht installiert ist.
Wenn man das nachgeholt und sich ab- und angemeldet hat, steht bei einem Rechtsklick auf einen Ordner, die Freigabefunktion zur Verfügung.
Nachdem ich system-config-samba installiert habe, gibt es das nächste Problem. Das Programm startet nicht, weil die Datei /etc/libuser.conf nicht existiert.
Also sudo touch /etc/libuser.conf im Terminal ausgeführt und system-config-samba gestartet.
Dort eine neue Freigabe konfiguriert und das System neu gestartet (sudo service samba reload hätte bestimmt auch gereicht).
Nach dem Neustart lässt sich system-config-samba nicht starten. Diesmal wegen einem anderen Problem. Das ist mir zu buggy - das Programm scheidet aus.

Schon beim Versuch mit Caja das Netzwerk zu durchsuchen, erscheint eine Fehlermeldung:
Zitat
Einhängen des Ortes nicht möglich

Empfangen der Freigabenliste vom Server ist gescheitert: Datei oder Verzeichnis nicht gefunden


Mal davon abgesehen das die Beta von Linux Mint 18 MATE Probleme hat das Netzwerk zu durchsuchen, habe ich das Gefühl das Microsoft sich immer wieder was neues einfallen lässt, um es Linux-Nutzern schwer zu machen. Sei es beim Netzwerk oder solche Dinge wie Secure Boot.

SgH

  • *
Re: Netzwerk: Windows 7 mit Windows XP oder Linux verbinden
« Antwort #16 am: 20.08.2016, 16:08:41 »
Hallo,

ich habe leider auch ein Verbindungsproblem, wozu ich bisher keine Lösung gefunden habe  :(

Ich habe LM18/C (192.168.137.5)  und will mit einem Crossover-Kabel eine direkte Verbindung zu meinem Win7 Rechner (192.168.138.1)  herstellen. Es hat schon einmal vor der Neusinstallation von LM18 funktioniert, wo ich einen Datentransfer durchführen konnte.

Das Eigenartige ist, dass ich zwar die Internetverbindung auf dem LM18 via dieser Verbindung vom Win7 Rechner her nutzen kann - also funktioniert das Kabel, bzw. dass ich via ping vom Win7 Rechner den LM18 Rechner erreiche, aber nicht umgekehrt.

Hier meine LM18 Config:
ifconfig
eno1      Link encap:Ethernet  Hardware Adresse a0:8c:fd:20:ad:60 
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:0 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:0 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:0 (0.0 B)  TX-Bytes:0 (0.0 B)

lo        Link encap:Lokale Schleife 
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metrik:1
          RX-Pakete:80 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:80 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1
          RX-Bytes:6368 (6.3 KB)  TX-Bytes:6368 (6.3 KB)

wlo1      Link encap:Ethernet  Hardware Adresse c8:ff:28:fc:e4:fb 
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:0 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:0 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:0 (0.0 B)  TX-Bytes:0 (0.0 B)

Hat jemand dazu eine Idee? Danke!

[Edit]: Ich habe jetzt ein ping ausgelöst, während das Kabel abgesteckt war, dann angesteckt und bekomme folgende Meldung:

ping 192.168.137.1
PING 192.168.137.1 (192.168.137.1) 56(84) bytes of data.
From 192.168.137.5 icmp_seq=14 Destination Host Unreachable
From 192.168.137.5 icmp_seq=15 Destination Host Unreachable
From 192.168.137.5 icmp_seq=16 Destination Host Unreachable
64 bytes from 192.168.137.1: icmp_seq=17 ttl=128 time=23.2 ms
64 bytes from 192.168.137.1: icmp_seq=18 ttl=128 time=0.772 ms
64 bytes from 192.168.137.1: icmp_seq=19 ttl=128 time=0.944 ms
64 bytes from 192.168.137.1: icmp_seq=20 ttl=128 time=0.827 ms
^C
--- 192.168.137.1 ping statistics ---
75 packets transmitted, 4 received, +3 errors, 94% packet loss, time 74124ms
rtt min/avg/max/mdev = 0.772/6.449/23.253/9.701 ms, pipe 3

3 pings sind erfolgreich und dann ist es wieder vorbei  :-[
« Letzte Änderung: 20.08.2016, 22:35:36 von SgH »

SgH

  • *
Re: Netzwerk: Windows 7 mit Windows XP oder Linux verbinden
« Antwort #17 am: 21.08.2016, 23:24:35 »
Irgendwie habe ich es jetzt hingekriegt, dass ich zumindest von Win7 auf LM18 zugreifen und die Daten übertragen kann ...

Re: Netzwerk: Windows 7 mit Windows XP oder Linux verbinden
« Antwort #18 am: 04.02.2017, 22:09:51 »
Ich habe auch die Probleme das ich zu den Windows10 Rechner keine Verbindung bekomme.

Wo kann ich den unter LinuxMint Kde die Arbeitsgruppe eingetragen mir werden nämlich 3 angezeigt.

Und bei allen will er sich mit User und PW anmelden obwohl es bei den anderen Im Lokalen Netzwerk keine PWs gibt.

Re: Netzwerk: Windows 7 mit Windows XP oder Linux verbinden
« Antwort #19 am: 22.05.2018, 02:04:41 »
Allgemein: Heimnetzgruppe ist so oder so das letzte und bei Win10 (wenn nicht schon jetzt) bald auch nicht mehr vorhanden.
Alle Zugriffe gehen da wunderbar und störungsfrei OHNE diesen Unfug!

@silverstar: Bei der NAS könnte es sein, dass beim Mount ggf. die CIFS-Version eine Rolle spielt, beim Mount den Parameter vers=1.0 oder vers=2.x probieren. Mal ins Handbuch von der NAS schauen, welche Version da läuft.

Viele Geräte, wie Fritzbox, Drucker, usw. sind noch bei 1.0...  :o :o :o :o :o

Re: Netzwerk: Windows 7 mit Windows XP oder Linux verbinden
« Antwort #20 am: 22.05.2018, 02:07:03 »
Also wenn ich mich recht erinnere, kommt die Arbeitsgruppe in die SMB.CONF
Ich mein als Parameter "Workgroup=MeinNetzBlaBlaBlub" oder so...
Kann sein, dass das dann alles groß oder KLEIN geschrieben werden muss.

EDIT: Gerade noch mal rein geschaut... Ja, genau so und alles groß.
« Letzte Änderung: 22.05.2018, 02:10:36 von itChOW »

Re: Netzwerk: Windows 7 mit Windows XP oder Linux verbinden
« Antwort #21 am: 02.12.2018, 10:24:34 »
Ist bei mir auch alles großgeschrieben.
Trotzdem sehe ich nur die Linuxgeräte.
Windows Rechner, Fritzbox, Drucker sehe ich nicht. :(
Hier meine smb.cfg
#
# 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 = TEST

# 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

# This Option for Share Harddiskdrives
 
   usershare owner only = false

#### 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
« Letzte Änderung: 02.12.2018, 12:26:29 von Harald-RS »

Re: Netzwerk: Windows 7 mit Windows XP oder Linux verbinden
« Antwort #22 am: 26.10.2020, 18:03:49 »
Gibt es schon eine Lösung?


Hier meine neue smb.cfg



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


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


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


#Protocol


   client min protocol = SMB2
   client max protocol = SMB3


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


# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
   logging = file


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


   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 config * :              backend = tdb
;   idmap config * :              range   = 3000-7999
;   idmap config YOURDOMAINHERE : backend = tdb
;   idmap config YOURDOMAINHERE : range   = 100000-999999
;   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 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


#  This Option for Share Harddiskdrives
usershare owner only = false

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


[disk2]
    comment = Festplatte_2
    path = /home/harald/media/hdd/disk2/
    read only = No
    guest ok = Yes


[disk3]
    comment = Festplatte_3
    path = /home/harald/media/hdd/disk3/
    read only = No
    guest ok = Yes


# 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


[d$]
    comment = Disk_2
    path = /home/harald/media/hdd/disk2/
browseable = yes
    read only = No
    guest ok = Yes


[e$]
    comment = Disk_3
    path = /home/harald/media/hdd/disk3/
browseable = yes
    read only = No
    guest ok = Yes


# 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



DeVIL-I386Threadstarter

  • Administrator
  • *****
Re: Netzwerk: Windows 7 mit Windows XP oder Linux verbinden
« Antwort #23 am: 28.10.2020, 01:35:18 »
Mich nervt das Gefrickel bei der SMB-Dateifreigabe schon seit Jahren.
Ich habe mir die letzten Jahre lieber mal eben nen FTP-Server installiert.

Wenn es im Heimnetzwerk schnell gehen soll, dann vsftpd.

Dort kann man sich mit dem Benutzer/Passwort anmelden, der schon lokal im System hinterlegt ist.

Siehe auch: https://wiki.ubuntuusers.de/vsftpd/#Server-starten-stoppen

Re: Netzwerk: Windows 7 mit Windows XP oder Linux verbinden
« Antwort #24 am: 29.10.2020, 21:26:36 »
Also ich sehe jetzt zwar die Rechner nur wenn ich sie Freigeben möchte.


Bekomme ich diese Meldung:



(Error NT_STATUS_RESOURCE_NAME_NOT_FOUND)
Failed to connect with SMB1 -- no workgroup available