Zugriff auf SAMBA Server von einem WIN 10 PC nicht mehr möglich, Ping möglich

auf dem NAS:

Version 4.9.5-Debian

@Samba:~# testparm -v | grep protocol
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[Share]"
Loaded services file OK.
Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

client ipc max protocol = default
client ipc min protocol = default
client max protocol = default
client min protocol = CORE
server max protocol = SMB3
server min protocol = LANMAN1

WIN 10 Rechner:

sc.exe qc lanmanworkstation
[SC] QueryServiceConfig ERFOLG

SERVICE_NAME: lanmanworkstation
TYPE : 20 WIN32_SHARE_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : C:\WINDOWS\System32\svchost.exe -k NetworkService -p
LOAD_ORDER_GROUP : NetworkProvider
TAG : 0
DISPLAY_NAME : Arbeitsstationsdienst
DEPENDENCIES : Bowser
: MRxSmb20
: NSI
SERVICE_START_NAME : NT AUTHORITY\NetworkService

PS C:\WINDOWS\system32> Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol

EnableSMB1Protocol EnableSMB2Protocol
------------------
True True


Das scheint zu laufen

So sieht die Conf jetzt aus. Funktioniert leider immer noch nicht.


GNU nano 3.2 /etc/samba/smb.conf

[global]
map to guest = Bad Password
security = user
workgroup = WORKGROUP
server min protocol = SMB2

[homes]
comment = Home Directories
browsable = yes
read only = no
create mode = 0750

[Share]
path =/data/
public = yes
writable = yes
comment = smb share
printable = no
guest ok = yes
read only = no

So sieht bei mir die Fehlermeldung aus.

service smbd status:

• smbd.service - Samba SMB Daemon

Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-03-28 18:48:49 UTC; 9min ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 141 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
Main PID: 145 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 38248)
Memory: 16.7M
CGroup: /system.slice/smbd.service
|-145 /usr/sbin/smbd --foreground --no-process-group
|-175 /usr/sbin/smbd --foreground --no-process-group
|-176 /usr/sbin/smbd --foreground --no-process-group
`-192 /usr/sbin/smbd --foreground --no-process-group

Mar 28 18:48:49 Samba systemd[1]: Starting Samba SMB Daemon...
Mar 28 18:48:49 Samba systemd[1]: Started Samba SMB Daemon.
Mar 28 18:48:49 Samba smbd[145]: [2021/03/28 18:48:49.327481, 0] ../lib/util/become_daemon.c:138(daemon_ready)
Mar 28 18:48:49 Samba smbd[145]: daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections

service nmbd status:

• nmbd.service - Samba NMB Daemon

Loaded: loaded (/lib/systemd/system/nmbd.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-03-28 18:59:42 UTC; 10s ago
Docs: man:nmbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 320 (nmbd)
Status: "nmbd: ready to serve connections..."
Tasks: 1 (limit: 38248)
Memory: 2.3M
CGroup: /system.slice/nmbd.service
`-320 /usr/sbin/nmbd --foreground --no-process-group

Mar 28 18:59:42 Samba systemd[1]: Starting Samba NMB Daemon...
Mar 28 18:59:42 Samba systemd[1]: Started Samba NMB Daemon.
Mar 28 18:59:42 Samba nmbd[320]: [2021/03/28 18:59:42.146490, 0] ../lib/util/become_daemon.c:138(daemon_ready)
Mar 28 18:59:42 Samba nmbd[320]: daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections

XXX@Samba:~# findsmb

*=DMB
+=LMB
IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
192.XXX.178.XX SAMBA +[ WORKGROUP ]

XXX@Samba:~# smbtree
smbXcli_negprot_smb1_done: No compatible protocol selected by server.
smbXcli_negprot_smb1_done: No compatible protocol selected by server.

Soll das so ?

XXX@Samba:~# smbstatus

Samba version 4.9.5-Debian
PID Username Group Machine Protocol Version Encryption Signing

Service pid Machine Connected at Encryption Signing

No locked files

Ich habe langsam die Vermutung das es an dem Lanmanworkstation Dienst liegt.
Diesen bekomm ich einfach nicht zum Laufen: