Skip to main content

Hi

I installed 16.2, and now my local music library has disappeared. The music is held on a Windows Server 2022 file share which is NOT SMB1, it’s SMB2 or SMB3. I can see Windows Event Log errors showing:

 

An account failed to log on.

Subject:
    Security ID:        NULL SID
    Account Name:        -
    Account Domain:        -
    Logon ID:        0x0

Logon Type:            3

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:        HOME\Sonos
    Account Domain:        -

Failure Information:
    Failure Reason:        Unknown user name or bad password.
    Status:            0xC000006D
    Sub Status:        0xC0000064

Process Information:
    Caller Process ID:    0x0
    Caller Process Name:    -

Network Information:
    Workstation Name:    -
    Source Network Address:    10.10.10.124
    Source Port:        59138

Detailed Authentication Information:
    Logon Process:        NtLmSsp 
    Authentication Package:    NTLM
    Transited Services:    -
    Package Name (NTLM only):    -
    Key Length:        0
 

 

Yet I know the username and password are correct as I can use them to authenticate from a Linux box.

 

Help :(

 

Many thanks

 

 

Jim

I am accessing music direct from my Mac and still being told there’s a 913 error!!!!

 

Is yours an HTTP share? They told me these are not supported either. RIDICULOUS RUBBISH.

Seems the update killed my music share. It is giving me an error. Yes, rebooted my controller. Still the same error.  Seems this update wasn’t very thought out or didn’t get any testing as it’s terrible. 

Yeah, 913. NB this has worked brilliantly since I bought the Sonos kit just a couple of months ago; the Local Library just disappeared today and now I cjna’t add it back.

 

 

 

Can Sonos read your Linux smb share? 

And to be sure that my server is not using SMB1:

 

 

Fixed it!

The music library got cleared from my system. Trying to add it back yielded no success.

 

Despite the on-scren prompts suggesting you need to us a UNC path, e.g. \\Server\Share\Folder, you don’t, you have to use a CIFS path, e.g. //SRV01/Music/Music

Also, if sharing from Windows, do NOT include the domain or workgroup name (against all common sense….). So in my case I changed HOME\Sonos to just Sonos.

 

Now working again.

Thanks for a wasted few hours, Sonos

 

Jim

I checked my Mac; it’s set for SMB share. So, it’s being blocked by Sonos who broke the share link. 

I’ve also lost my music share from my Mac.  At first I thought it just couldn’t be re-indexed by the new app (which is an issue in itself), but even on my Mac controller, the library has just literally disappeared and when I try to add it back in I just get an error.

Sonos - I appreciate you are feeling overwhelmed with the negative feedback that is coming through.  But people have spent thousands of pounds on speakers and we can’t even play music on them.  Would an option be to let people downgrade to the previous versions just while you sort yourselves out perhaps?  I’m even considering fully downgrading to S1, if that is still even possible.  I just want music.  Nothing fancy.

I recently discovered that, unlike SMB1/NTLM1, Sonos can't connect to SMB2 and 3 with a domain name (e.g. Home\SonosUser) irrespective of whether the server is Windows or Linux. I had mine set up with a active directory server domain user which worked fin with SMB1, but refused to connect under 2 and 3. Changed the connection to a local user on my Synology and it worked.

Terms & ConditionsCookie settings