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+
Hello
wait recalbox 7.0.1 tonight 9.00 pm CET France.
https://forum.recalbox.com/topic/21798/recalbox-7-0-1-on-rail
Please update your recalbox and try again after.
Thanks for the heads-up.
The problem still persists in v7.0.1
I tried a fresh install, same problem.
@Tosnic
Here below you will be able so source example working fine with 7.0
link : https://recalbox.gitbook.io/tutorials/v/francais/reseau/partage/charger-ses-roms-depuis-un-partage-reseau-samba-un-nas-par-exemple
Command line : sharenetwork_<nfs|smb><[0-9]>=<SHARE|ROMS|SAVES|BIOS|MUSIC|OVERLAYS|SCREENSHOTS|SHADERS|SCRIPTS>@<NAS>:<répertoire partagé>:<options>
sorry, I am not capable of French
@olivierdroid92 According to Google Translate, in this tutorial you would replace the SD card as the rom location. Plus, this tutorial seems to only affect EmulationStation. My problem is with Kodi.
Can anyone confirm whether my issue is with Recalbox v7 or stemming from my setup?
I found some strange things today, looking into my router's interface. There were 2 IP addresses associated with the Raspi system, but none of those MACs matched the MAC that Kodi presents. Kodi shows the same address as ifconfig via SSH.
After forcefully removing all static DHCP references from my router concerning my Raspi, it now is assigned random IP addresses (like in most setups). Now EmulationStation shows "connected" in its network settings.
Still, the problem persists.
I tried my previous installation of Recalbox v6.1.1 (thankfully, I used another SD card for v7). This installation still works fine regarding SMB.
If your nas support dlna try to activate unpp in settings menu in kodi ! I'm not sure but thinking it was active by default in previous releases now you have to activate unpp.
@dstroy It seems that way. In Kodi Krypton I could not find the option to toggle UPnP. In Kodi Leia the option is disabled by default.
But changing to DLNA would simply circumvent the issue, not solve it.
@Tosnic hi did you solve the problem?
i still can't go to my NAS and it says: "software caused connection abort",
@drpoucevert nope
do you have the same issue?
@Tosnic yes i have the same issue
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
maybe there is a way to force smb1
@drpoucevert
force into smb1 is not a good idea.
Should consider only smb2 and or smb 3
@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
@Tosnic thanks for that ,
i found a soureceforge page for the DNS 320 that allows me to force smb2 and 3 but it will screw my backup so there is no way i'm going threw a whole shifting my backup to have a proper working smb
is there anyway i can get to my samba settings in ms DNS320?
thank you
@drpoucevert said in SMB not working in Recalbox v7.0:
@Tosnic thanks for that ,
i found a soureceforge page for the DNS 320 that shows how to force smb2 and 3 but it will screw up my backup so there is no way i'm going through the whole process of shifting my backup to have a proper working smb
is there any way i can access my samba settings in ms DNS320?
thank you
I am not sure if I understood you correctly, so I took the liberty of changing your post how I understood it (above).
But I still do not understand how changing your NAS to SMBv2 or v3 impacts your backup. It seems like you should expand your research to a place dedicated to your NAS (or its OS).
BTW: In case anyone is wondering about my instructions from the previous post: I am running a Linux NAS (Open Media Vault).
After numerous experiments, it was found that the kodi cannot connect to the smb server if the user on the remote server does not have a password. Protocol version does not matter.
SMB-client in operating system work fine whith and whithout password.
I had the same problem trying to connect kodi to my NAS. I managed to workaround this issue by defining the minimum SMB version to 1 and the maximum to 3 in the kodi SMBclient configurations. The minimum was selected to 'none' - then suddenly I could browse my SMB shares like I did in the previous recalbox version. I hope this helps!
@Tosnic
Here below you will be able so source example working fine with 7.0
link : https://recalbox.gitbook.io/tutorials/v/francais/reseau/partage/charger-ses-roms-depuis-un-partage-reseau-samba-un-nas-par-exemple
Command line : sharenetwork_<nfs|smb><[0-9]>=<SHARE|ROMS|SAVES|BIOS|MUSIC|OVERLAYS|SCREENSHOTS|SHADERS|SCRIPTS>@<NAS>:<répertoire partagé>:<options>
