Samba no longer working after switch to MX-23 AHS

Message
Author
Joerg
Posts: 113
Joined: Tue Jan 14, 2020 3:13 pm

Samba no longer working after switch to MX-23 AHS

#1 Post by Joerg »

Maybe I didn't use the right search terms but could not find relevant info. After installing MX-23 AHS Samba (and some other stuff) got broken here and I am having a hard time. Firewall is turned off and I have set a Samba password. Permissions for the directories to be shared have also been set accordingly. Workgroup is the same as always. I have not touched smb.conf. Other machines do see the MX-23 machine in Thunar but when trying to access shares all I get is a message that they can't be accessed. The two shares I have set in the Samba Config of MX Tools won't even show up in Thunar on the other machines, only the MX-23 machine itself does.

Setting shares via MX Tools edits usershares and not smb.conf. According to this documen it is discouraged to mess with the smb.conf file that comes with the MX-23 distro, which is why I didn't:

https://fullscale4me.com/MX-Linux-to-Wi ... haring.pdf

Further searching on the web indicates that this line should be in smb.conf but it isn't:

usershare path = /usr/local/samba/lib/usershares

Do I need to add this line or are there any other incantations necessary to make file sharing via Samba work again like it did in MX-19?

Quick system info:

Code: Select all

System:
  Kernel: 6.5.0-1mx-ahs-amd64 [6.5.3-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1mx-ahs-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_ahs_x64 Libretto October 15  2023 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Desktop System: HP product: HP Slim Desktop S01-aF0xxx v: N/A serial: <superuser required>
    Chassis: type: 3 serial: <superuser required>
  Mobo: HP model: 876C v: SMVB serial: <superuser required> UEFI: AMI v: F.21 date: 03/25/2021
CPU:
  Info: model: AMD Athlon Silver 3050U with Radeon Graphics bits: 64 type: MCP arch: Zen/Zen+
    note: check gen: 1 level: v3 note: check built: 2019 process: GF 12nm family: 0x17 (23)
    model-id: 0x18 (24) stepping: 1 microcode: 0x8108109
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 192 KiB desc: d-2x32 KiB; i-2x64 KiB
    L2: 1024 KiB desc: 2x512 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 1500 high: 1603 min/max: 1400/2300 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1397 2: 1603 bogomips: 9182
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT disabled
  Type: spec_rstack_overflow mitigation: SMT disabled
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series] vendor: Hewlett-Packard
    driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3
    speed: 8 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1 empty: none bus-ID: 04:00.0
    chip-ID: 1002:15d8 class-ID: 0300 temp: 50.0 C
  Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-6.1:5
    chip-ID: 046d:0825 class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1024x1536 s-dpi: 96 s-size: 271x406mm (10.67x15.98") s-diag: 488mm (19.22")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,top model: HP vs15 serial: <filter>
    built: 2005 res: 1024x768 hz: 60 dpi: 87 gamma: 1.4 size: 300x220mm (11.81x8.66")
    diag: 372mm (14.6") ratio: 4:3 modes: max: 1024x768 min: 720x400
  Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: bottom model: XGA serial: <filter> built: 2003
    res: 1024x768 hz: 60 dpi: 86 gamma: 1.86 size: 304x228mm (11.97x8.98") diag: 50mm (2") modes:
    max: 1024x768 min: 720x400
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon Graphics (raven2 LLVM 15.0.6 DRM
    3.54 6.5.0-1mx-ahs-amd64) direct-render: Yes
Audio:
  Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Hewlett-Packard driver: snd_hda_intel
    bus-ID: 1-6.1:5 v: kernel chip-ID: 046d:0825 pcie: class-ID: 0102 gen: 3 speed: 8 GT/s
    serial: <filter> lanes: 16 bus-ID: 04:00.1 chip-ID: 1002:15de class-ID: 0403
  Device-2: AMD Family 17h/19h HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo
  Device-4: Texas Instruments PCM2901 Audio Codec type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-6.2.2.2:25 chip-ID: 08bb:2901 class-ID: 0300
  API: ALSA v: k6.5.0-1mx-ahs-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter vendor: Hewlett-Packard
    driver: rtw_8821ce v: N/A modules: rtw88_8821ce,wl,rtl8821ce pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 02:00.0 chip-ID: 10ec:c821 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth 4.2 Adapter type: USB driver: btusb v: 0.8 bus-ID: 1-4.2:30
    chip-ID: 0bda:b00a class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 16 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
    sub-v: f098 hci-v: 4.2 rev: 75b8
  Info: acl-mtu: 1021:8 sco-mtu: 255:12 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
Drives:
  Local Storage: total: 462.05 GiB used: 121.02 GiB (26.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: KIOXIA model: N/A size: 238.47 GiB block-size:
    physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: AGHA4101
    temp: 37.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 model: SATA SSD size: 223.57 GiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3 scheme: MBR
Partition:
  ID-1: / raw-size: 48.83 GiB size: 47.76 GiB (97.81%) used: 7.34 GiB (15.4%) fs: ext4
    dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-2: /boot/efi raw-size: 499 MiB size: 495 MiB (99.20%) used: 25.7 MiB (5.2%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 128.05 GiB size: 124.99 GiB (97.60%) used: 8.55 GiB (6.8%) fs: ext4
    dev: /dev/nvme0n1p7 maj-min: 259:7
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 9.77 GiB used: 920.9 MiB (9.2%) priority: -2
    dev: /dev/nvme0n1p6 maj-min: 259:6
Sensors:
  System Temperatures: cpu: 49.2 C mobo: N/A gpu: amdgpu temp: 49.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2146 libs: 1123 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://la.mxrepo.com/mx/repo/ bookworm ahs
Info:
  Processes: 264 Uptime: 6d 2h 12m wakeups: 57 Memory: 5.7 GiB used: 4.42 GiB (77.5%)
  Init: SysVinit v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0
  alt: 12 Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
smb.conf that came with MX-23 AHS:
#
# 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
Regards, Joerg

User avatar
FullScale4Me
Posts: 1124
Joined: Fri Jan 08, 2021 11:30 pm

Re: Samba no longer working after switch to MX-23 AHS

#2 Post by FullScale4Me »

What is the output of 'net usershare info --long' ?
Joerg wrote:Permissions for the directories to be shared have also been set accordingly.
Tell us more about any changes made.
Last edited by FullScale4Me on Sat Jan 06, 2024 1:47 am, edited 2 times in total.
Michael O'Toole
MX Linux facebook group moderator
Dell OptiPlex 7050 i7-7700, MX Linux 23 Xfce & Win 11 Pro
HP Pavilion P2-1394 i3-2120T, MX Linux 23 Xfce & Win 10 Home
Dell Inspiron N7010 Intel Core i5 M 460, MX Linux 23 Xfce & KDE, Win 10

User avatar
FullScale4Me
Posts: 1124
Joined: Fri Jan 08, 2021 11:30 pm

Re: Samba no longer working after switch to MX-23 AHS

#3 Post by FullScale4Me »

Joerg wrote: Sat Jan 06, 2024 12:29 am
Further searching on the web indicates that this line should be in smb.conf but it isn't:

usershare path = /usr/local/samba/lib/usershares

Do I need to add this line or are there any other incantations necessary to make file sharing via Samba work again like it did in MX-19?
Short answer = no.

MX Linux uses the Debian path for those Samba share files.

From the Help File https://mxlinux.org/wiki/help-files/help-mx-samba-config/
File share definitions can be found in /var/lib/samba/usershares, each share in an individual file. Files are owned by the user that creates them.
Michael O'Toole
MX Linux facebook group moderator
Dell OptiPlex 7050 i7-7700, MX Linux 23 Xfce & Win 11 Pro
HP Pavilion P2-1394 i3-2120T, MX Linux 23 Xfce & Win 10 Home
Dell Inspiron N7010 Intel Core i5 M 460, MX Linux 23 Xfce & KDE, Win 10

Joerg
Posts: 113
Joined: Tue Jan 14, 2020 3:13 pm

Re: Samba no longer working after switch to MX-23 AHS

#4 Post by Joerg »

Hello Michael,

Thanks for responding. The permissions are set as shown in the attached Thunar screen shot. When I click on the computer named "Lab" (the one with the new MX-23 where Samba no longer works) from another machine I get the response in the second screen shot, no access.

/var/lib/samba/usershares has two shares. For example, the one named "Public" meant to be accessible by everyone looks like this and was set via MX Tools:
#VERSION 2
path=/media/joerg/1588DF2332312B2B/Public
comment=
usershare_acl=S-1-1-0:f,S-1-5-21-2874501325-2126276707-2563377044-1000:f
guest_ok=y
sharename=Lab Public
What can I do to find out what's broken?

Regards,

Joerg
You do not have the required permissions to view the files attached to this post.

User avatar
razor2021
Posts: 499
Joined: Mon Feb 08, 2021 4:49 pm

Re: Samba no longer working after switch to MX-23 AHS

#5 Post by razor2021 »

Its not broken, and more deprecated due to security issues. Others might know more.

Since version 4, both Samba Server & Samba Clients do not allow an older level of protocols negotiation. You have to enable them in smb.conf file to support lower NT protocol e.g. SMB2 or SMB3 (shown below). Others would say its not safe to do so and you need to update your Samba server/clients to higher. From above, I think you indicate v2.

Edit /etc/samba/smb.conf file (need root permissions)

in the [global] section, add the following line(s)

client min protocol = SMB2
client max protocol = SMB3

Save the file and exit the editor.
You must restart the Samba Service for this change to take effect. In a terminal, enter this command:

sudo service smbd restart
Mixed of desktops and laptops, I have a Gravis Ultrasound Classic card (unfortunately its ISA-slot based) ... - I must be a dino. :popcorn:
Running on my DesktopPC - MX-23.4 AHS with latest Kernel: 6.12.17-1-liquorix-amd64

User avatar
FullScale4Me
Posts: 1124
Joined: Fri Jan 08, 2021 11:30 pm

Re: Samba no longer working after switch to MX-23 AHS

#6 Post by FullScale4Me »

Stay with me on this, OK?

Also, create a share in the user's home directory.
FullScale4Me wrote:What is the output of 'net usershare info --long' ?
This uses Samba to look at the local machine's shares. Are they visible in Thunar? At a minimum 'nobody' and 'print$' should be seen.

What is the output of:

Code: Select all

 sudo ufw status
Michael O'Toole
MX Linux facebook group moderator
Dell OptiPlex 7050 i7-7700, MX Linux 23 Xfce & Win 11 Pro
HP Pavilion P2-1394 i3-2120T, MX Linux 23 Xfce & Win 10 Home
Dell Inspiron N7010 Intel Core i5 M 460, MX Linux 23 Xfce & KDE, Win 10

User avatar
FullScale4Me
Posts: 1124
Joined: Fri Jan 08, 2021 11:30 pm

Re: Samba no longer working after switch to MX-23 AHS

#7 Post by FullScale4Me »

razor2021 wrote: Sat Jan 06, 2024 6:42 pm ...Since version 4, both Samba Server & Samba Clients do not allow an older level of protocol negotiation. You have to enable them in smb.conf file to support lower NT protocol...
Yes, for the last 10+ years, Samba has been slowly plucked of the remaining SMB version 1 support. Fresh Windows 10 installs starting with the Fall 2018 edition lost SMB1 sharing [hosting] support. Editing smb.conf is NO LONGER needed.
razor2021 wrote: Sat Jan 06, 2024 6:42 pm SMB2 or SMB3 (shown below). Others would say it's not safe to do so and you need to update your Samba server/clients to higher.
With the current [MX21 & MX23] MX Samba Configuration Tool versions, the result is it just works, as is, with NO tweaks AT ALL. Create a share in the user's home area and you are good to go.

All of the user problems that come to this forum are a dog's breakfast of [obsolete/don't apply] internet how-two articles advice and older MX [18] practices that refuse to fade away.

Of all the old behavior modalities only ONE is justifyable and that is ONLY when some network device has no support for SMB2 or SMB3.
razor2021 wrote: Sat Jan 06, 2024 6:42 pm
From above, I think you indicate v2.
IIRC this indicates the 2nd incarnation of the Samba Configuration tool [1st Red Hat?] and not the SMB protocol version 2 as you have inferred.
razor2021 wrote: Sat Jan 06, 2024 6:42 pm in the [global] section, add the following line(s)

client min protocol = SMB2
client max protocol = SMB3
This is a quote of Microsoft's recommendation from a few years back. It is still valid for enhancing security. Won't fix this issue... Stop using SMB1

I am the author/maintainer of the below document - updated several times a month.
MX Linux to Windows and Mac File Sharing updated: January 01, 2024
Michael O'Toole
MX Linux facebook group moderator
Dell OptiPlex 7050 i7-7700, MX Linux 23 Xfce & Win 11 Pro
HP Pavilion P2-1394 i3-2120T, MX Linux 23 Xfce & Win 10 Home
Dell Inspiron N7010 Intel Core i5 M 460, MX Linux 23 Xfce & KDE, Win 10

Joerg
Posts: 113
Joined: Tue Jan 14, 2020 3:13 pm

Re: Samba no longer working after switch to MX-23 AHS

#8 Post by Joerg »

Michael, here is the net usershare info from the MX-23 machine:
joerg@Lab:~
$ net usershare info --long
[Lab Public]
path=/media/joerg/1588DF2332312B2B/Public
comment=
usershare_acl=Everyone:F,LAB\joerg:F,
guest_ok=y

[Lab Data]
path=/media/joerg/1588DF2332312B2B/Data
comment=
usershare_acl=LAB\joerg:F,
guest_ok=n

[Joerg_Home]
path=/home/joerg
comment=
usershare_acl=LAB\joerg:F,
guest_ok=y
Unfortunately they don't show up on any other machine. All the others show is that the computer "Lab" does exist on the LAN but trying to access it on their Thunar only produces the "Failed to open "Lab"" error message..

I turned the firewall off, at least until Samba and some other stuff that broke is sorted out:
joerg@Lab:~
$ sudo ufw status
[sudo] password for joerg:
Status: inactive
Razor2021, I tried "client min protocol = SMB2" and "client max protocol = SMB3" under [global] but no dice, that did not make it work. I had also tried dropping min to NT1 but no luck :-(

Regards,

Joerg

User avatar
FullScale4Me
Posts: 1124
Joined: Fri Jan 08, 2021 11:30 pm

Re: Samba no longer working after switch to MX-23 AHS

#9 Post by FullScale4Me »

Does an MX Linux 19/21/23 boot USB booted & running on this 'Lab' PC show up on the other PCs on the network?

On a Windows PC in a CMD window: net view \\mx1
Michael O'Toole
MX Linux facebook group moderator
Dell OptiPlex 7050 i7-7700, MX Linux 23 Xfce & Win 11 Pro
HP Pavilion P2-1394 i3-2120T, MX Linux 23 Xfce & Win 10 Home
Dell Inspiron N7010 Intel Core i5 M 460, MX Linux 23 Xfce & KDE, Win 10

Joerg
Posts: 113
Joined: Tue Jan 14, 2020 3:13 pm

Re: Samba no longer working after switch to MX-23 AHS

#10 Post by Joerg »

Yes, in MX-19 sharing works from the "Lab" PC. Also, on this "Lab" PC I can still see and access shares from other PCs even while running MX-23. It just won't share anything itself. The other PCs still run MX-19.

Regards, Joerg

Post Reply

Return to “Software / Configuration”