• 1
  • 3
  • 4
  • 5
  • 6(current)
  • 7
Configuring & Adding SMB/Samba Network shares
#76
Hi,

I recently bought a new Windows 11 PC for my home network to share multiple drives and folders with Kodi (on my Nvidia Shield Pro 2019) by SMB.

Everything works in my two Windows 10 PCs but I cannot get the new Windows 11 PC to share its folders with the Kodi 21 (Omega) release.
I can get Window 11 folders to be shared in Kodi 20 (Nexus) but not in Omega.

The Windows 10 PCs can share the same folders in Nexus and Omega.

What am I doing wrong here?
I have Omega and Nexus being set up identical using the same shared folders.
But Omega always gives me the "invalid argument" error.

Any help would be greatly appreciated.
Many thanks.
Reply
#77
Hi,

somehow I cannot connect to Windows 11 shared folder.

Quote:2023-07-31 21:36:53.095 T:4750 error <general>: Unable to lookup host: '\Desktop-l4htj8d\l'
2023-07-31 21:36:53.096 T:4750 error <general>: SMBDirectory->GetDirectory: Unable to open directory : 'smb://USERNAMETongueASSWORD@%5cDesktop-l4htj8d%5cl/'
unix_err:'6f' error : 'Connection refused'

I have set user and password. I have enabled SMB version 1 as minimum version and version 3 as maximum version. Any ideas what is going on? I am using Kodi v20.2.
Reply
#78
Quote:2023-07-31 23:32:52.511 T:8180  warning <general>: localGetNetworkResources: Can't read shares for "\\\\Desktop-l4htj8d\l" by localGetShares(), fallback to old method
2023-07-31 23:32:52.528 T:8180     info <general>: localGetNetworkResources: Can't open network enumeration for "\\\\Desktop-l4htj8d\l". Error: 1203
2023-07-31 23:32:52.529 T:8180  warning <general>: XFILE::CWin32SMBDirectory::ConnectAndAuthenticate: Can't connect to "\\\\Desktop-l4htj8d\l" with username "Max Mustermann" and with password. Error code: 53
2023-07-31 23:32:52.529 T:8180    error <general>: XFILE::CDirectory::GetDirectory - Error getting smb://USERNAMETongueASSWORD@\\Desktop-l4htj8d\l/Just tried it with Kodi 20.2 on my Windows7 and not on an Android TV Box, but it still didn't work.
Actually, can't I edit my previous post above?
Reply
#79
(2023-07-31, 23:37)sOKRATEs100 Wrote: \\Desktop-l4htj8d\

... "\\Desktop-l4htj8d\" is not a valid hostname ... for any instance of using a computer
Reply
#80
Ok, I have resolved it.

Was typing this in the field "Shared folder". But did input now my computers IP adress in field "Server name". Thanks!
Reply
#81
Important update - instructions in OP no longer work:

The instructions in the original post in this thread do no longer work as desired with medium/high bitrate 4K movies (~20-30GB files) with a samba network shares. At least not on nVidia Shield 2019 Pro (FW 9.1.1) with currently latest version of Kodi (20.2).

If you follow those instructions, you'll get "Source too slow for continuous playback" error reported in Kodi when playing movies. The movie will pause and stutter throughout playback. That is regardless if you're server and network has high performance or not. E.g. I get the problem using a Windows 10 server PC with Intel 4670K CPU and 1 Gigabit Ethernet network using fixed cables.

How to solve:

* Remove any samba sources configured directly in Kodi. (Just so that you do not use them by mistake when adding media content in Kodi.)

* Configure the samba source in Android/nVidiaShield directly (instead of in Kodi), by following these steps:
1. Open the NVIDIA SHIELD device Settings.
2. Choose Storage & reset then Network Storage.
3. Under Available Network Storage, select your device and then choose Connect as a registered user.
4. Enter the username and password for the network location.
5. You can now verify that the location was mounted successfully: "1 mounted" will appear under Network Storage in the list. You can select that for details.

For reference the instructions above are from the section "Connecting to a Network Location (SMB)" on this page. Those instructions are for Plex, but work for Kodi too.

* After following the steps above, start Kodi and use the source you configured above when selecting media to use in Kodi (e.g. when adding movies, music, etc to your media library).

I've tried the above and it works perfectly. E.g. I can play 4K Blu-ray movie rip remuxes with size of 90+ GB without any problem at all. No "Source too slow for continuous playback" reported in Kodi any longer.
Reply
#82
(2023-08-26, 23:10)Fjodor2000 Wrote: Important update - instructions in OP no longer work:

The instructions in the original post in this thread do no longer work as desired with medium/high bitrate 4K movies (~20-30GB files) with a samba network shares. At least not on nVidia Shield 2019 Pro (FW 9.1.1) with currently latest version of Kodi (20.2).

If you follow those instructions, you'll get "Source too slow for continuous playback" error reported in Kodi when playing movies. The movie will pause and stutter throughout playback. That is regardless if you're server and network has high performance or not. E.g. I get the problem using a Windows 10 server PC with Intel 4670K CPU and 1 Gigabit Ethernet network using fixed cables.

How to solve:

* Remove any samba sources configured directly in Kodi. (Just so that you do not use them by mistake when adding media content in Kodi.)

* Configure the samba source in Android/nVidiaShield directly (instead of in Kodi), by following these steps:
1. Open the NVIDIA SHIELD device Settings.
2. Choose Storage & reset then Network Storage.
3. Under Available Network Storage, select your device and then choose Connect as a registered user.
4. Enter the username and password for the network location.
5. You can now verify that the location was mounted successfully: "1 mounted" will appear under Network Storage in the list. You can select that for details.

For reference the instructions above are from the section "Connecting to a Network Location (SMB)" on this page. Those instructions are for Plex, but work for Kodi too.

* After following the steps above, start Kodi and use the source you configured above when selecting media to use in Kodi (e.g. when adding movies, music, etc to your media library).

I've tried the above and it works perfectly. E.g. I can play 4K Blu-ray movie rip remuxes with size of 90+ GB without any problem at all. No "Source too slow for continuous playback" reported in Kodi any longer.

I have this problem , but I have firesticks 4K max. I see no way to do this like on the Shield. 🥹
Reply
#83
(2023-09-01, 04:53)crazyazz Wrote: I have this problem , but I have firesticks 4K max. I see no way to do this like on the Shield. 🥹

because it is not for "firesticks 4K max" which runs FireOS, it is for Android and the feature they are configuring is provided by Nvidia's version of Android

NVidia is not Amazon
Reply
#84
I know that, Im saying there is no LIKE option unfortunately on FireOS.
Reply
#85
I am on dune homatics box and running kodi omega
I can’t connect to my smb server on windows 11
I am using Ip address instead of name and also tried changing min. version
I get error 8216 not sure what is this error
Btw do I need to provide server or also path of media , for ex I m attaching multiple hdd in my laptop

Pls suggest
Reply
#86
Ok so seems I was missing for providing a name of shared fielder ( I thought this will browse all my shares once connected) Nad port setting is default zero, and I can’t edit and put 445
But now I see files suffering or in slow motion and other buffering issues “ source too slow issue” like Nvidia
Btw I m on ftvc3
Reply
#87
I have been using Kodi for several years, since smbV1 was blocked for sharing by Windows. That made useless the media boxes I used before.

I store my videos on my Windows 10 PC, and network them to the TVs or TV boxes (Shield Pro and Xiaomi) on other rooms.

But in the past weeks three of my Kodi installations (TVs and Xiaomi) stopped linking to my PC. The smbV3 setup I had written on each one was erased and now I can't seem to make them work again.

I feel lost, I just don't know what to write on the "Add Network Location" page, nothing seems to work.

Can anyone help me?
Reply
#88
as for mounting via Shield vs mounting vis Kodi, one small issue i found wth the Shield method (which increases speeds by a lot)  is that Kodi could scan/see the folders, but not the content. Found this fix and it is now working 100%.
- Nvidia Shield / settings / Apps / Kodi / Permissions / Files and media / Allow all the time

But..i just found another issue. When i try and export library, Kodi doesn't seem to have write abilities. Unable to write to folder is the warning i get. Doh.
Reply
#89
Hi,
I have Kodi 20.2 installed on a Firestick. It was able to play files from an WD external drive connected to a QNAP NAS. I ditched the NAS in favor of Ubuntu 22.04 on a computer.
The same external drive is now connected to the computer and shared via Samba.

Kodi can see the share, but I get "Error 2: Share not available" when I try to connect.

I set the SMB settings on Kodi to Minimum V1 and Maximum V3; no luck.

It works if I connect via UPNP, but I would like to avoid that if I can because it is less secure than SMB.
I feel it is a permissions issue, but I don't know how to fix it. Any ideas?
Reply
#90
I haven't been able to solve my Kodi issue here on the forum, with my Xiaomi box, in spite of sending my log file.

I wonder where else to go, since there's no Xiaomi TV box forum.
Reply
  • 1
  • 3
  • 4
  • 5
  • 6(current)
  • 7

Logout Mark Read Team Forum Stats Members Help
Configuring & Adding SMB/Samba Network shares0