(2021-03-02, 21:39)damorsoft Wrote:

(2021-03-02, 20:40)jjd-uk Wrote: That included creating the share on the Win 10 PC. For the Kodi side less than 1 min.

All you need to do on Kodi is:

Check SMB Client settings under Services and make sure Min version is SMB1, you'll then never need to touch that again.

After that:

1. Add source

2. Browse

3. Add network location

4. Set server name to the Computer name ( no need to use ip address)

5.i. If share does not have a password:

Select username add any letter you want
Select password add any letter you want

5.ii. If share does have password protection use the account credentials of the user on pc assigned to share.

6. OK.

And that's it.

(2021-03-02, 21:53)jjd-uk Wrote: The used SMB version is controlled by the device where the share is setup, so yes you shouldn't be using SMB1 for that. On the client kodi side setting SMB1 as the min will just ensure it can connect to any SMB share on the network, as it says it's a minimum. So if if share is on Windows PC with SMB1 disabled it will always use SMB2/3.

(2021-03-02, 21:53)jjd-uk Wrote: The used SMB version is controlled by the device where the share is setup, so yes you shouldn't be using SMB1 for that. On the client kodi side setting SMB1 as the min will just ensure it can connect to any SMB share on the network, as it says it's a minimum. So if if share is on Windows PC with SMB1 disabled it will always use SMB2/3.

(2021-03-03, 00:50)dpw2atox Wrote: I had similar issues on the shield with Kodi 18.x when I had the shares mapped manually in Kodi, then I read on the Shield forums that it was advised to map the shares directly on the shield and after that I had no issues. For now I am back on 18.9 and not having any issues but its less than ideal to be stuck using old and unsupported software now.

(2021-03-03, 13:32)jjd-uk Wrote:

(2021-03-03, 00:50)dpw2atox Wrote: I had similar issues on the shield with Kodi 18.x when I had the shares mapped manually in Kodi, then I read on the Shield forums that it was advised to map the shares directly on the shield and after that I had no issues. For now I am back on 18.9 and not having any issues but its less than ideal to be stuck using old and unsupported software now.

I'm not aware of any issues with Kodi mounted shares for any other andoid device, so that sounds like something Nvidia needs to fix, it sounds like a cop-out on their part to advise using the OS mount shares, although admittely this probably now sounds like a cop-out on our part saying the Kodi moiunted shares should work with no issues. The problem is that the Shield is the only android device I'm aware of that can do easily do OS mounted shares, so it's not something someone without a Shield can replicate so even here where the Kodi software maybe at fault, it may need someone from the Nvidia dev team to investigate.

(2021-03-03, 19:33)dpw2atox Wrote: It might even be that the Shield is still on an older version of Android TV (it should be Android TV 9) and that could be causing the issues.

(2021-03-02, 00:39)damorsoft Wrote:

(2021-02-26, 00:00)EventDriven Wrote: Here is what I did to make this work. As others said, I needed to reference via IP instead of server name. Basically, I exported my library as a single file and changed all references from my server name to IP. I did the same in passwords.xml and sources.xml. Finally I copied the changed xml files, re-imported the library and then cleaned the library. Maybe there's a simpler way that will work for some but this is what worked for me. Here are the steps I used in a little more detail.

• Make sure your NAS has a static IP
  
• In SMB settings in Kodi, change the minimum required version to SMB1 if you don't currently have a value there
  
• Go into file explorer in Kodi and add a source to connect to your NAS share via IP. For example for SMB it would be smb://123.123.1.123/my_share or something like that. I think you need to use a username and password. In any case, I am.
  
• Navigate to your profiles directory. Copy passwords.xml and sources.xml to your share.
  
• Backup your library to your NAS as a single file
  
• Make a backup copy of all the stuff you copied to your NAS in case you need to restore them: the sources, passwords and the library backup.
  
• In each of passwords.xml, sources.xml and videodb.xml in your backup folder, using a text editor find and replace your_server_name with the IP address of your server, e.g, 123.123.1.123.
  
• Copy passwords.xml and settings.xml back to Kodi and restart Kodi.
  
• Import your library by pointing to the backup folder where you edited videodb.xml.
  
• Clean you library to remove duplicate entries that are referencing your server name instead of IP. This might take awhile if you have a large library so don't panic.
  

As I said, maybe there's an easier way that will work for some but this is what worked for me.

This is all well and done, it works, I had to put a password in my windows sign-on but it does work
The elephant in the room.....
IP ==smb://123.123.1.123/my_share or something like that
If you are on a router and the router is shut down ie power failure. Texas are you listening.
The router assigns a new ip to the server and the smb://123.123.1.123/my_share  is no longer a share.
So set up all shares over or
-you will have to set up a static IP on all the serving boxes.
Have you read the instructions to do this with win10

So really all this effort just to run a buggy version of KODI..

18.9 is looking better all the time.

Best if Kodi just works the way we like it.

(2021-03-03, 21:50)EventDriven Wrote:

(2021-03-02, 00:39)damorsoft Wrote:

(2021-02-26, 00:00)EventDriven Wrote: Here is what I did to make this work. As others said, I needed to reference via IP instead of server name. Basically, I exported my library as a single file and changed all references from my server name to IP. I did the same in passwords.xml and sources.xml. Finally I copied the changed xml files, re-imported the library and then cleaned the library. Maybe there's a simpler way that will work for some but this is what worked for me. Here are the steps I used in a little more detail.

• Make sure your NAS has a static IP
  
• In SMB settings in Kodi, change the minimum required version to SMB1 if you don't currently have a value there
  
• Go into file explorer in Kodi and add a source to connect to your NAS share via IP. For example for SMB it would be smb://123.123.1.123/my_share or something like that. I think you need to use a username and password. In any case, I am.
  
• Navigate to your profiles directory. Copy passwords.xml and sources.xml to your share.
  
• Backup your library to your NAS as a single file
  
• Make a backup copy of all the stuff you copied to your NAS in case you need to restore them: the sources, passwords and the library backup.
  
• In each of passwords.xml, sources.xml and videodb.xml in your backup folder, using a text editor find and replace your_server_name with the IP address of your server, e.g, 123.123.1.123.
  
• Copy passwords.xml and settings.xml back to Kodi and restart Kodi.
  
• Import your library by pointing to the backup folder where you edited videodb.xml.
  
• Clean you library to remove duplicate entries that are referencing your server name instead of IP. This might take awhile if you have a large library so don't panic.
  

As I said, maybe there's an easier way that will work for some but this is what worked for me.

This is all well and done, it works, I had to put a password in my windows sign-on but it does work
The elephant in the room.....
IP ==smb://123.123.1.123/my_share or something like that
If you are on a router and the router is shut down ie power failure. Texas are you listening.
The router assigns a new ip to the server and the smb://123.123.1.123/my_share  is no longer a share.
So set up all shares over or
-you will have to set up a static IP on all the serving boxes.
Have you read the instructions to do this with win10

So really all this effort just to run a buggy version of KODI..

18.9 is looking better all the time.

Best if Kodi just works the way we like it.

If you're storing your files on a win10 machine then you simply need to google "assigning a static IP on Windows 10". You will also want to be able to access your router so that you make sure the IP you assign is outside the DHCP address range so that you don't take the chance of running into IP conflicts at some point.

(2021-03-03, 23:46)damorsoft Wrote: Install kodi 19 go into system-services change SMB min to SMB1 and everything works. no ip screwing around no pw's just tv..

(2021-03-04, 18:37)gulian Wrote: inbuilt network browsing capability with SMBv2