This issue was originally brought up by @Michael_Galusha in this thread (the screenshot originates from
The issue wasn’t picked up and addressed by Roon yet, so making it an official support request is in order.
You will find some information on the issue in the thread linked above.
Below are my findings findings:
—————
Connecting to NAS shares from within the Roon application no longer works and triggers the above shown error codes on the console display.
My NAS (Synology, DSM 7.3) only allows for SMB v2 and v3 connections which worked fine in the past with Bookworm.
So for debugging purposes, I re-enabled SMB v1 on the NAS, but still no luck connecting to the NAS. This indicates that the SMB v1 connection is already refused on the client side by the updated CIFS version of trixie and not on the server side.
Making connections manually through the operating system (either using mount commands or dietpi-drive_manager) works fine though, even without specifying a version in the mount options (see EDIT below!), and shows SMB v3 being used.
Most likely reason for this behavior is that Roon uses “vers=1.0” as default in the mount options when trying to make connections which has been tolerated by the Host Linux OS up to Bookworm, but no more with Trixie.
Time for Roon to update their code as this problem will affect more and more users with ongoing updates from bookworm to Trixie!
EDIT:
According to the man page, CIFS defaults to SMB v2.1 or higher, if no “vers=xy” attribute is passed.
To verify this, I tried a simple mount command from the console without specifying a version string, which was successful and shows no errors on the console and “SMB3” as protocol being used.
EDIT2:
Strangely enough, when enabling SMB v1 on the Server and manually mounting the share via the command line with “vers=1.0” you get the warning on the console (error code 95), but the connection is established with SMB1.
Same thing still doesn’t work when trying to add the network share via the Roon App with error code 13 (authentication failed). So SMBv1 works if it forced and isn’t blocked on client side by Trixie after all.
So Roon must be doing something more in the mount options that causes authentication to fail. Maybe forcing NTLMv1 password hashing in security attributes or something else that is no longer supported by modern OS’es?