Best posts made by Tosnic

This issue has been resolved in Recalbox v7

Many people are using a NAS nowadays. Probably the most commonly used protocol is Server Message Block (SMB). This could be utilized since the XBox Media Center days. SMB is still available when adding a new source, but it is not working in Recalbox v7.0. It had been working in v6.1.1 just fine.

details:
When creating a new source, I choose SMB, but none of the sources on the network show. There are usually at least two: my NAS and my router.
When I create the source manually, I enter all details and when finished, Kodi instantly reports "software caused connection abort", therefore it seems that it is not even trying to connect. On the other hand, when my NAS is off, the error message reads something like "no route to server".

side note:
EmulationStation states in network settings that it is "not connected", even though wifi is connected and a LAN cable is plugged in. Yet Kodi tells that it is connected properly (in its network settings).
Another hint in this direction: when I manually create an SMB share, Kodi states "the connection to the network location couldn't be established. This could be due to the network not being connected. Would you like to add it anyway?"

The raspi is obviously connected to the network since it received its static DHCP IP address from the router and can play youtube videos. I can ping the raspi from my PC.

Hardware: Raspi 3b+

@drpoucevert said in SMB not working in Recalbox v7.0:

i think the problem comes from our smb protocol on our nas
mine has a smb1 and i think kodi leia has gone to smb2/3

This was a very good finding. The SMB version of the NAS was actually the culprit.
I had already set Kodi to not care about the minimum SMB version (nor the maximum SMB version), but it still did not work with my NAS, which turned out to run SMBv1. I wonder why the SMB version setting in Kodi does not work as I expected.
Maybe it would work if Kodi were set to "minimum version = 1". The setting can be found here:
Settings -> Services -> SMB Client

I solved the issue by changing the max SMB version in my NAS. Since it was running Samba 3.6.6, I needed to edit this file:
/etc/samba/smb.conf
I added this line to the global section:
max protocol = SMB2
Don't forget to restart after applying this change.

Source: https://wiki.samba.org/index.php/Samba_3.6_Features_added/changed#SMB2_support