• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

Gelöst Debian 12 SMB-Freigabe

lewendi

Advanced Hacker
System Debian 12.5 KDE

Nachdem ich nun Debian installiert habe hatte ich schon einige Probleme.
1. KeepassXC von "Discover" nicht installieren, sonst geht das einfügen der BN und PW nicht. Ich habe das neuere
KeePassXC-2.7.9-x86_64.appimage von der Herstellerseite installiert, welches funktioniert.

2. Ich muß mich bein Starten immer mit meinen PW anmelden. Frage, wo kann ich das ändern, dass ich mich immer ohne PW einloggen kann?

3. Wenn ich nach den Start den Dateimanager (Dolphin) öffne und auf meine Daten-HD zugreifen will, so muß ich die immer erst einhängen und dann mit den root-PW freigeben.


4. das bis zum jetzigen Zeitpunkt -hoffentlich- letzte Problem ist die Samba-Freigabe, da komme ich wirklich nicht weiter. Wie kann ich hier die Berechtigung ändern.

Hier mal das Ergebnis vom SMb Status

Code:
alter@debian-12:~$ sudo systemctl status smbd.service
[sudo] Passwort für walter:
● smbd.service - Samba SMB Daemon
     Loaded: loaded (/lib/systemd/system/smbd.service; enabled; preset: enabled)
     Active: active (running) since Wed 2024-06-26 16:22:59 CEST; 20min ago
       Docs: man:smbd(8)
             man:samba(7)
             man:smb.conf(5)
    Process: 3189 ExecCondition=/usr/share/samba/is-configured smb (code=exited, status=0/SUCCESS)
    Process: 3192 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
   Main PID: 3196 (smbd)
     Status: "smbd: ready to serve connections..."
      Tasks: 3 (limit: 18993)
     Memory: 9.3M
        CPU: 1.075s
     CGroup: /system.slice/smbd.service
             ├─3196 /usr/sbin/smbd --foreground --no-process-group
             ├─3198 /usr/sbin/smbd --foreground --no-process-group
             └─3199 /usr/sbin/smbd --foreground --no-process-group

Jun 26 16:22:59 debian-12 systemd[1]: Starting smbd.service - Samba SMB Daemon...
Jun 26 16:22:59 debian-12 systemd[1]: Started smbd.service - Samba SMB Daemon.
Jun 26 16:26:43 debian-12 smbd[3319]: pam_unix(samba:session): session closed for user nobody
Jun 26 16:26:44 debian-12 smbd[3333]: pam_unix(samba:session): session closed for user nobody
Jun 26 16:26:44 debian-12 smbd[3335]: pam_unix(samba:session): session closed for user nobody
Jun 26 16:27:38 debian-12 smbd[3468]: pam_unix(samba:session): session closed for user nobody
Jun 26 16:34:19 debian-12 smbd[3867]: pam_unix(samba:session): session closed for user nobody
Jun 26 16:41:22 debian-12 smbd[3988]: pam_unix(samba:session): session closed for user nobody
Jun 26 16:41:48 debian-12 smbd[4063]: pam_unix(samba:session): session closed for user nobody
lines 1-27

Freue mich natürlich wie immer auf Eure Hilfe.

Gruß
lewendi
 

Anhänge

  • f1.png
    f1.png
    304,5 KB · Aufrufe: 8
  • f2.png
    f2.png
    294,5 KB · Aufrufe: 8
Zuletzt bearbeitet:

susejunky

Moderator
Teammitglied
Hallo @lewendi ,

Wenn ich nach den Start den Dateimanager (Dolphin) öffne und auf meine Daten-HD zugreifen will, so muß ich die immer erst einhängen und dann mit den root-PW freigeben.
Hängst Du diesen Datenträger über /etc/fstab ein? Wenn ja, zeige bitte das Ergebnis von
Code:
cat /etc/fstab
Unabhängig davon, wenn der Datenträger eingehängt ist, bitte noch das Ergebnis von
Code:
mount

das bis zum jetzigen Zeitpunkt -hoffentlich- letzte Problem ist die Samba-Freigabe
Zeige bitte das Ergebnis von
Code:
cat /etc/samba/smb.conf

Viele Grüße

susejunky

PS
Dir ist bekannt, dass ich ausschließlich openSUSE Tumbleweed verwende; d.h. ggf. sieht unter debian Vieles anders aus und die obigen Befehle liefern keine Ergebnisse. Dann musst Du warten, bis sich ein debian-Benutzer hier einbringt.
 
OP
lewendi

lewendi

Advanced Hacker
Danke susejunky, dass Du dich meldest.
Debian ist doch etwas schwieriger zum einrichten als Suse oder *buntu. Es ist noch eine große Baustelle, einige Sachen funktionieren nicht., so kann man "Timeshift" nicht starten, "Dolphin" funktioniert nicht mehr unter /root usw.
Wenn mich das weiter nervt, nehme eine andere Distri rauf. Aber mal schauen.

cat /etc/fstab

walter@debian-12:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb2 during installation
UUID=6c366c27-cd53-4c36-863b-c268cfd259cd / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sdb1 during installation
UUID=5F4C-399F /boot/efi vfat umask=0077 0 1
# /home was on /dev/sdb4 during installation
UUID=54c55400-f36b-47d4-8000-a7d70bb69105 /home ext4 defaults 0 2
# swap was on /dev/sdb3 during installation
UUID=09a2c354-6aef-485a-a08d-d07afe044175 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
walter@debian-12:~$

Datei eingehängt
mount


ist im Anhang!
mount - Filemail
 
Zuletzt bearbeitet:

susejunky

Moderator
Teammitglied
Hallo @lewendi ,

walter@debian-12:~$ cat /etc/fstab
# /etc/fstab: static file system information.
...
# / was on /dev/sdb2 during installation
UUID=6c366c27-cd53-4c36-863b-c268cfd259cd / ext4 errors=remount-ro 0 1

# /boot/efi was on /dev/sdb1 during installation
UUID=5F4C-399F /boot/efi vfat umask=0077 0 1

# /home was on /dev/sdb4 during installation
UUID=54c55400-f36b-47d4-8000-a7d70bb69105 /home ext4 defaults 0 2

# swap was on /dev/sdb3 during installation
UUID=09a2c354-6aef-485a-a08d-d07afe044175 none swap sw 0 0
...
walter@debian-12:~$
da werden nur "/", "/boot/efi", "/home" und "swap" eingehängt.

Warum hängst Du nicht auch /dev/sdc1 direkt beim Systemstart mit Hilfe eines Eintrags in /etc/fstab ein?

Viele Grüße

susejunky
 
OP
lewendi

lewendi

Advanced Hacker
Ich habe jetzt die Daten-Windows, Daten-linux und Timeshift mit eingebunden.

Die von Dir angesprochen /dev/sdc1 ist eine Windows Wiederherstellung, die habe ich gelassen.

Das Problem mit der SMB Freigabe ist aber deswegen immer noch nicht behoben, wie kann ich da die Rechte ändern (Bild 2).


Code:
walter@debian-12:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdb2 during installation
UUID=6c366c27-cd53-4c36-863b-c268cfd259cd /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sdb1 during installation
UUID=5F4C-399F  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/sdb4 during installation
UUID=54c55400-f36b-47d4-8000-a7d70bb69105 /home           ext4    defaults        0       2
# swap was on /dev/sdb3 during installation
UUID=09a2c354-6aef-485a-a08d-d07afe044175 none            swap    sw              0       0

/dev/sdd1   UUID=63C171AF3AE009AA             D-DATEN-LINUX                         TYPE=ntfs PARTUUID=b4de1107-8969-4700-ad6d-543e1e88cf51
/dev/sda1   UUID=36A1149E73BECA2B         D-DATEN-WINDOWS           TYPE=ntfs PARTUUID=aead4ded-3a29-974a-a3c5-bb77268521c1
/dev/sdd2   UUID=b8555ba4-594b-4f4d-9f54-dfff28001474  TIMESHIFT    TYPE=ext4 PARTUUID="a58a037f-f31a-2549-ba2f-4cf5229df10f"
/dev/sr0    /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/sr1    /media/cdrom1   udf,iso9660 user,noauto     0       0
 

susejunky

Moderator
Teammitglied
Hallo @lewendi ,

wie ich bereits sagte, ich kenne debian nicht, aber funktionieren diese fstab-Einträge

walter@debian-12:~$ cat /etc/fstab
# /etc/fstab: static file system information.
...
#
# <file system> <mount point> <type> <options> <dump> <pass>
...
/dev/sdd1 UUID=63C171AF3AE009AA D-DATEN-LINUX TYPE=ntfs PARTUUID=b4de1107-8969-4700-ad6d-543e1e88cf51
/dev/sda1 UUID=36A1149E73BECA2B D-DATEN-WINDOWS TYPE=ntfs PARTUUID=aead4ded-3a29-974a-a3c5-bb77268521c1
/dev/sdd2 UUID=b8555ba4-594b-4f4d-9f54-dfff28001474 TIMESHIFT TYPE=ext4 PARTUUID="a58a037f-f31a-2549-ba2f-4cf5229df10f"
...
tatsächlich?

Ich würde erwarten, dass ein fstab-Eintrag in etwa so aussehen muss:
Code:
UUID=63C171AF3AE009AA /mnt/D-DATEN-LINUX ntfs-3g rw,nofail,nodev,nosuid,noexec,uid=nnnn,gid=nnnn,windows_names         0  0

Was Dein SAMBA-Problem anbelangt, so kann ich dazu nichts sagen, solange ich den Inhalt Deiner /etc/samba/smb.conf nicht kenne.

Viele Grüße

susejunky
 
OP
lewendi

lewendi

Advanced Hacker
wie ich bereits sagte, ich kenne debian nicht, aber funktionieren diese fstab-Einträge
Ja das funktioniert.

Die smb.conf

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

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

# 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 = classic
# primary domain controller', 'server role = classic 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/useradd --create-home %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

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

[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.
# The following parameter makes 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/tmp
   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
 
OP
lewendi

lewendi

Advanced Hacker
Ich verabschiede mich von Debian und steige auf openSUSE Leap 15.6.
Habe auch die Anfrage auf "gelöst" gesetzt!
 
Oben