Synology DSM 7.0 issue

[dranrabekim]

My BW T4 has for the last few years successfully stored all of it's recordings on a Synology DS415+ NAS in the "T4Recordings" share.

I recently upgraded the Synology NAS software to DSM 7.0 from DSM 6.2 and now the T4 can't see this NAS share (or any NAS share).

FYI - I had a similar problem with my Sonos music system being unable to connect and through google and the Sonos forum searches found that if I enabled NTLMv1 I could get the Sonos to connect (albiet with reduced security) and is now working fine.

I had hoped that this "fix" would also enable the T4 to connect/see shares, but you know how it goes and it didn't!!

The strange thing is that if I do a network search on the T4 (Setup>Network>network browser) it shows my NAS and drilling down shows the T4Recordings share and all without the little red x. This indicates to me that it is connected. So it appears connected BUT when I try to view the media (TV recordings) files I get a "Directory '/media/autofs/T4Recordings/' does not exist message".

Appreciate that this is really a Synology problem as all was good before moving to DSM 7.0, but has anyone out there any ideas or been able to resolve this issue before?

Thanks for any help.

[MrQuade]

It's likely that the NAS is enforcing a layer version of SMB and the T4 is just attempting to connect using SMB v1.

That world also mean that your T4 firmware is quite out of date.

The quickest fix (if that is the problem) is to edit your mount definition and add a new option "vers=2.1". What will force the T4 to connect to the NAS using the later version.

I would strongly advise you to update your T4 to the latest beta release via USB to take advantage of all the latest enhancements and bug fixes. Among those is that later versions of SMB are used by default.

[dranrabekim]

Hi MrQuade

Thanks for getting back to me.

My T4 is running Release 19.3, Build 20191106 (the latest as far as I know) and has been for quite a while.

The NAS has file services set with SMB1 as a min and SMB3 as a max, so should cover any SMB out there.

Out of interest I did add vers=2.1 to the mount, (so have rw,utf8,vers=2.1) but that made no difference.

Any other ideas cordially invited.

[Gully]

My T4 is running Release 19.3, Build 20191106 (the latest as far as I know) and has been for quite a while.

That's not the latest beta release. You need to go here.

Make sure you follow the instructions about updating to the beta feed and see how you go then.

[Grumpy_Geoff]

Any other ideas cordially invited.

Paul_oz53 should be along any time soon to suggest you try changing the mount type from autofs to fstab!

[MrQuade]

Any other ideas cordially invited.

One of the other things that came along with later SMB versions was a requirement to only use authenticated connections (at least in Windows).

Try connecting to the NAS using a recognised username and password (whatever users are configured on the NAS and have permissions to those shares),

[Paul_oz53]

Any other ideas cordially invited.

Paul_oz53 should be along any time soon to suggest you try changing the mount type from autofs to fstab!

Nah, it's a broken T4. I'm hoping whatever fixes this issue will help me!

My T4 is driving me insane with dodgy networking and FSTAB didn't fix it. Nor does vers=2.1.

It can access the Study U4 normally and playback perfectly but can't access the Lounge U4 for playback without serious delay in the order of minutes.

Conversely, both U4s and the T3 can see and playback from the T4 and from each other. Connections to the PCs work fine.

Both U4s have identical firmware, software settings and physical network configurations. No amount of reinstalling firmware has made the slightest difference.

I'm convinced it's affected by an evil spell!

[Teddles]

I recently upgraded the Synology NAS software to DSM 7.0 from DSM 6.2 and now the T4 can't see this NAS share (or any NAS share).

NVM, I was going to point out the need for NTLMv1 authentication, but I notice you've already done that

[dranrabekim]

Thanks for that Teddles, yes that was what got the Sonos going and able to connect. Apparently it's a security issue that Sonos hasn't fixed (like SMB1), but they aren't likely to apparently so it needs to be checked to get the Sonos to connect.

[IanL-S]

Cannot offer any help . But it encourages me to hold off on moving to DSN 7.0.

Ian

[MrQuade]

Thanks for that Teddles, yes that was what got the Sonos going and able to connect. Apparently it's a security issue that Sonos hasn't fixed (like SMB1), but they aren't likely to apparently so it needs to be checked to get the Sonos to connect.

Are you connecting from the T4 to the NAS using a username and password?

[dranrabekim]

Yes I am Mr Quade. I have both a username and password set and that hasn't changed since moving to DSM 7.0

[MrQuade]

Yes I am Mr Quade. I have both a username and password set and that hasn't changed since moving to DSM 7.0

You could also try adding the mount option
"sec=ntlmssp"

[dranrabekim]

Thanks to all who have provided suggestions to my dilemma, but would you believe it, I have now managed to fix it (hope it lasts).

All I did was delete the share T4Recordings on the T4 and then recreate it in Mount Manager>Add new network mount point using the original credentials. Somehow that seems to have got the NAS to accept the T4, who would think it!!

Also I didn't install the beta firmware, but I may now.

Thanks again for all the help.