How to make openSUSE and Samba friends?

Question

linux

The situation is crazy. There is a machine, home, it has been installed for 3 months openSUSE Leap 15.2. At home there is a router with a USB port, which was quickly adapted to the home ball. The problem is this.
Samba is installed and configured on the machine (since the router fumbles with an external screw using the ancient smb1 protocol, I had to write a couple of lines in the config on all Linux devices). From all machines and systems, an overview of the spherical folders is available, but not from the subject folder, with a chameleon on board.

What exactly - when you go to the explorer (dolphin) and then to the section with networks - SMB - it searches for a long time and does not find anything.
Minor command output

systemctl status smb.service

gives this:

Click to open spoiler with output

● smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2020-12-29 21:14:59 EET; 5s ago
Process: 7429 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Process: 7425 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
Main PID: 7429 (code=exited, status=1/FAILURE)

Dec 29 21:14:59 localhost.localdomain systemd[1]: Starting Samba SMB Daemon...
Dec 29 21:14:59 localhost.localdomain systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Dec 29 21:14:59 localhost.localdomain systemd[1]: Failed to start Samba SMB Daemon.
Dec 29 21:14:59 localhost.localdomain systemd[1]: smb.service: Unit entered failed state.
Dec 29 21:14:59 localhost.localdomain systemd[1]: smb.service: Failed with result 'exit-code'.

It does not start and that's it, even if you try to start it manually. Same error. Googling the question leads to a dead end, because all the available solutions, firstly, do not work, and secondly, they look meaningless.

I note that when manually driving in the address of the server with the ball in the explorer itself, it works. I successfully connect to a specific server, fully get access to files. Some nonsense.
smb://192.168.1.1/video - voila, connects, but browsing and searching for third-party machines does not work.
As far as I can remember, even on version 13.1 of the system, I encountered this tambourine, but I never solved it. And now it is necessary:) Help, who faced.

UPD - I attach the samba config

spoiler

# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
[global]
client use spnego = no
client ntlmv2 auth = no
client min protocol = NT1
workgroup = WORKGROUP
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
usershare allow guests = Yes
netbios name = tecra
usershare max shares = 100
wins support = Yes
ldap admin dn =
security = share
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775

Answer 1

1) avahi configure
2) wsdd

Answer 2

Nakua output of ungodly systemd? The samba config would be more interesting...