EDIT: I changed the title of this thread because it was a very specific use case that I was having issues with and guessing not a lot of people had that same combination.  After some extensive troublehsooting with the team over at Emby on why my server keeps timing out when trying to access via Kodi and the Emby for Kodi next-gen addon, they were able to surmise that I have a local networking issue as playback over WAN via Kodi works fine.  Is there anyone that could  help me troubleshoot my LAN setup to see if we can find the root cause of the problem?

 

 

Ever since I upgraded to Unraid OS +6.11, I lost the ability to connect to my Unraid server thru kodi using Emby Next Gen addon.  I started with help from the Emby community and basically after several troubleshooting attempts, they've determined the issue must be server side or within my Kodi configuration.

 

To summarize, whenever Emby Next Gen attempts to connect to my Emby media server, the server has a timeout. This doesn't happen with any other Emby configurations (e.g. AFTV Emby app, iOS app, Windows etc) on multiple devices.  The issue is exclusive to kodi (both v. 19.3 and 19.4 on two different clients - 2x AFTV's running 19.4 and an nVidia Shield TV Pro on 19.3).

 

What information could I provide to help troubleshoot?  Attached are two different kodi logs (regular and debug) after a timeout. The emby logs didn't show anything to the Emby team but happy to include here as well if needed.  Thanks in advance.

kodi debug log.txt kodi log.txt

Edited November 10, 20223 yr by betaman

Bumping this in the hopes someone can help me figure out what changed in my setup?

Man, nobody uses Kodi + Emby with their UnRAID server that might be able to weigh in here??  Must be a permissions issue somewhere but I can't find it as I'm not an experienced Kodi user.

Edited November 3, 20223 yr by betaman

Update: the team over at Emby have successfully tested my setup over WAN and found no issues playing my media library via Kodi. This points to a LAN issue. Anyone who might be able to help me troubleshoot my LAN setup (or software configuration changes within UnRaid or Kodi) would be appreciated. Thanks in advance.

Changed the name of the thread to see if I could find someone with more understanding of network configuration and local setttings.

I was a bit premature in thinking I had solved this. For some reason, I've got it working on one AFTV client (EDIT: now 2 AFTV clients different vintages and one wired with the other wireless but I can’t get another wired AFTV to work nor a Windows 10 version of Kodi as a well as my Nividia Shield TV Pro) but not on 2 others, a Win10 pc or my nVidia Shield TV Pro. I would think this would lend itself to a client side issue but I can't seem to figure it out.  The first AFTV client seemed to work after I made 2 changes:

1) I changed the min level SMB Client setting to v1 (from any)
2) I changed the SMB security setting on my "media" share from private (requires username and password) to secure (guest read only access).

The AFTV cleint that is working is a 1st or 2nd gen FireTV (the square box version with a wired connection) but one of the other AFTV's is the same vintage and the other is a FireTV Stick Lite.  The server timeout issue points to a permissions issue but I don't understand why I don't have issues with other apps on the same clients (e.g. the Emby app works fine)?

 

@Frank1940: I've been reading thru several of the threads you've created on SMB and UnRAID. Pretty helpful but I have a couple questions around best practices for setting up shares to be accessed by clients like my AFTV's and Shield Pro (e.g. secure vs private, netbios on/off etc). Seems Kodi adds another layer of complexity. Curious if you have any thoughts on things I might try to narrow down the issue?

Edited November 13, 20223 yr by betaman

Maybe this:

 

      

 

3 hours ago, Frank1940 said:

Maybe this:

 

      

 

Thanks for responding. I added ntlm auth = yes to my smb extra configuration in my UnRAID SMB settings but didn’t observe any change with the clients that are timing out. If I restrict smb to v1 min and max in Kodi then I can use smb to browse to my WORKGROUP but no further. On one of the unresponsive clients, with smb min setting to v1 and max to v3, I can actually browse my shares in Kodi but when Emby Next Gen tries to connect to it there’s a timeout. I’m really at a loss now since I have some clients working, one can browse the shares and the others show no signs of any connection at all. This is so frustrating…

 

Edit: at least now I can correlate when my clients lost connection to my server happened with the upgrade to 6.11. It has been over a month I’ve been trying to figure out what happened.

Edited November 13, 20223 yr by betaman

I tried downgrading to 6.10.3 but still have the same 2 clients that won’t connect (haven’t tried the Win 10 pc yet). The other 2 that were working under 6.11.3 are still working.