samba - Aug 2025 - could not connect to, Unable to find suitable address

I'm using Samba version 4.13.13-Debian on both

Br
Matthias

Am Mittwoch, dem 27.08.2025 um 21:29 +0200 schrieb Matthias at
gmx.li:
> Hello,
> 
> I have two samba server in my LAN but can only access shares from the
domain master, fileserver
> but
> not from the other, athlux.
> I already disabled the iptables firewall.
> 
> ?* If I'm on athlux, I can mount shares from both, from athlux as well
as from fileserver
> 
> ?* If I'm on fileserver, I can mount shares from fileserver but not
from athlux:
> ?? mount -t cifs -o username=meyer //athlux/Backup4U /disk
> ?? Password for meyer@//athlux/Backup4U:
> ?? mount error(113): could not connect to 192.168.0.70Unable to find
suitable address.
> ?? 
> 
> 
> Is there something wrong with my configuration?
> 
> The working samba server (fileserver) have the [global] section in
/etc/samba/smb.conf:
> [global]
> hide unreadable = yes
> domain master = yes
> wins proxy = No
> hosts allow = 192.168.0.0/255.255.255.0
> unix password sync = yes
> socket options = TCP_NODELAY
> encrypt passwords = true
> hide special files = yes
> os level = 64
> oplocks = yes
> username map = /etc/samba/user.map
> log file = /var/log/samba/log.%m
> map to guest = Bad User
> max log size = 1000
> passwd program = /usr/bin/passwd %u
> logon home = \\%N\%U\profile
> domain logons = Yes
> preferred master = no
> server string = Samba Server %v
> workgroup = PrivateLAN
> logon script = logon.bat
> netbios name = FileServer
> 
> The not working samba server (athlux) have the [global] section in
/etc/samba/smb.conf:
> [global]
> unix password sync = yes
> passdb backend = tdbsam
> server string = %h server
> workgroup = PrivateLAN
> server role = standalone server
> obey pam restrictions = yes
> preferred master = no
> encrypt passwords = yes
> hosts allow = ALL
> panic action = /usr/share/samba/panic-action %d
> passwd program = /usr/bin/passwd %u
> log file = /var/log/samba/log.%m
> max log size = 1000
> os level = 20
> netbios name = AthLux
> pam password change = yes
> syslog = 0
> dns proxy = no
> username map = /etc/samba/user.map
> 
> Thanks in advance

On Thu, 28 Aug 2025 08:03:17 +0200
Matthias--- via samba <samba at lists.samba.org> wrote:
> I'm using Samba version 4.13.13-Debian on both
That probably means you are still running Debian Bullseye, which went
EOL 12 months ago and is now under LTS support, so it just gets
security updates. If you have hit a bug, unless it is security related,
it will not get fixed, Samba certainly will not fix it (unless it is
also in the current Samba supported versions, but then it very probably
wouldn't be backported).

I suggest you update everything.

The other problem is that you say that one of your machines is working,
but it appears to be running as a PDC, but without the required SMBv1,
so you could try adding the following two lines to both smb.conf files:

client min protocol = NT1
server min protocol = NT1

Rowland