This topic indeed has been produced, but the solution does not work for me.
My remarks are below. I do not use any passwords, so this does not work for me. Furthermore, the message I get is “not able to connect to the network server”. Before this everything really worked fine.
The issue you are currently experiencing with OSMC
I’m unable to access my SMB shares
What you were doing when this issue occurred
I had just rebooted after getting the latest update and tried to access an existing share.
Whether you can replicate this issue on demand. If you can, then please provide some steps on how an OSMC developer can reproduce the same issue.
I can reproduce it by trying to access an existing share again.This does not work.
The device you are currently running OSMC on
Raspberry Pi model 3
What peripherals are attached to the device?
None at the moment.
Has this issue been introduced by a new version of OSMC? When did the issue first appear and can you recall a time when it was not present?
Yes, it’s happened right after the latest update. Before that, everything was working fine.
Same here. Watching stuff - new updates - download and reboot. Shares all ask for username and password now, even though I do not use U/P for my network shares.
I guess this is to do with the Samba security update, but now it’s so secure I can’t access my non-password protected shares!
Help! I really don’t want to set usernames and password for the shares, as OSMC is not the only media player accessing them!
Are you using Windows? I posted a workaround here:
Since Win8 Windows also keep asking about password even if there wasn’t any, but we could bypass it using guest account (without joining to homegroup). Yesterday I wasn’t be able to use guest login on Kodi. Maybe empty pass field is unsupported, just guessing.
I have the same problem since this morning not to connect to a Samba share.
When I make a connection request with smbclient here is the error message I get.
Server does not support EXTENDED_SECURITY but 'client use spnego = yes and ‘cli ent ntlmv2 auth = yes’
“client lanman auth = yes” is now consistently
required for authenticated connections using the
SMB1 LANMAN2 dialect.
“client ntlmv2 auth = yes” and “client use spnego = yes”
(both the default values), require extended security (SPNEGO)
support from the server. That means NTLMv2 is only used within
NTLMSSP.
Seems like as part of the security fix for SMB1 additional security features are enabled.
Which server are you using?
Also did you installed the updates on your server to patch the badlock bug?
I guess you will need to update the samba server on the NAS as the badlock bug impacted the communication between the client and the server and as written above with the new security patch also additional security settings have been enabled on old protocols
the manufacturer no longer supports this and therefore no update possible.
But the trouble is that I tried on a windows share no login and no password.
And the problem is always the same
Same problem here. I’m getting a window titled ‘lock preferences for smb’ and then i have to enter password and username. On other devices i can access my shared files without any problems… Any solutions?
