I was recently looking at all the drama with WannaCry ransomware and was considering disabling SMB1 on all my servers. Unfortunately when I turned this off on my Synology NAS, my MrMC on my ATV4 could no longer see my content there. Can you confirm if MrMC can use SMB2 or higher for server connections or did I miss a step?

Hey team, thanks for the replies. I found that this problem also exists in the mainline Kodi v17.1 "Krypton" on my Mac as well. Looking at their forums the same question seem to have come up on this thread: http://forum.kodi.tv/showthread.php?tid=314350.

For my part in the MrMc debug logs the following message appears for connection to SMB2/SMB3 mounts:

In the meantime I enabled NFS on my NAS with the instructions here: http://kodi.wiki/view/NFS. The only change I made was to set the access to read only instead of read/write on my Synology setup and I am able to connect and browse content in MrMc.

What I have noted however is that for large libraries like the one I have the refreshing of new content takes quite a bit longer than when I was using SMB. I will see how it goes.

Okay this thread explained a lot for me as I was in the same boat, I bought a Synology NAS and was having all kinds of strange problems, couldn't see the server until I enabled libdsm but I also turned off SMB v1 leaving v2/3 enabled and couldn't connect, it would give errors so this explains why.

Before stumbling upon this thread I gave NFS a try, I mistakenly followed the Kodi NFS wiki and could not connect but your MrMC NFS wiki guide is more up to date with the right settings to use and it works great so anyone else reading this hopefully avoids the same mistake.

I've also read MS are dropping SMB v1 support from Windows 10 in the fall creators update so that's something to watch out for if shares stop working.

Okay this thread explained a lot for me as I was in the same boat, I bought a Synology NAS and was having all kinds of strange problems, couldn't see the server until I enabled libdsm but I also turned off SMB v1 leaving v2/3 enabled and couldn't connect, it would give errors so this explains why.

Before stumbling upon this thread I gave NFS a try, I mistakenly followed the Kodi NFS wiki and could not connect but your MrMC NFS wiki guide is more up to date with the right settings to use and it works great so anyone else reading this hopefully avoids the same mistake.

I've also read MS are dropping SMB v1 support from Windows 10 in the fall creators update so that's something to watch out for if shares stop working.

We have something in the oven regarding solving SMB issues once and for all. No ETA as yet.

I have a Synology/ATV4 setup but NFS never worked well for me. SMB worked fine unless I access folders with a lot of content. Accessing such folders would take 20-30 seconds to list the content.
Last week though, I was trying some other settings which really improved loading times (8-10 seconds at the very most now!)