NAS playlist skips songs often with share does not exist message

Forum|Forum|5 months ago
May 7, 2026
11 replies
109 views

This is a problem I’ve been having for several weeks. I do not know what changed to cause it.

Setup: Sonos 2 connect, Synology NAS, .all wired, m3u playlists

All software/’firmware is up-to-date and use various controller devices (macOS, Windows, Android). NAS has SMB 2 & 3 enabled and access is via admin level user name & password.

Problem:

I queue-up the playlist and many of the songs are skipped with the message:

“the share //Syn_NAS/Music” does not exist”.

Some songs play, and they are in that same library/folder as ones that are skipped and don’t play. The entries in the .m3u playlist file appear the same (format, location, etc) for the ones that play as the ones that don’t play..

Fixes tried (none worked):

Tried using IP of NAS instead of folder name
Removed and re-added the share
Rebooted router, NAS, Sonos Connect

Considering alternatives but they each have challenges for me (Plex, Roon, Jellyfin, WiiM, Bluesound/Node, etc)

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Best answer by Sotiris C.

Hello @alan278, welcome back!

I am sorry to hear you are experiencing issues with missing tracks on your playlist from your NAS drive.

May I ask, have you tried re-creating the same Playlist? Or simply create a new one with just a few of the missing tracks for testing purposes?

You’ve already done some basic troubleshooting steps that I would have suggested.

Best course of action would be to reproduce this issue, Submit Diagnostics within 5 minutes of doing so and then reach out to our Support Team for live troubleshooting.

They have tools at their disposal to provide you with information and advice specific to your Sonos system and what it reports.

I hope this helps.

Show previous replies

Stanley_4

Grand Maestro

@Stanley_4

Some ‘ characters are also not accepted. When I replaced them with the apostrophe on the keyboard all was well. You can hardly tell the difference between the one that isn’t allowed and the one on the keyboard. This issue was pretty rare.

That is the beauty of the catia vfs mapping function, you can work around SMB, Windows or Sonos naming issues without altering your original file name. I really like keeping the original file names for systems that can support them and doing on-the-fly remapping for the crippled systems use. Just have to have a character to hexadecimal table handy.

catia:mappings = 0x3a:0xf7

Sign up

Login to the community