Login at Kodi Home

**jjd-uk** · (This post was last modified: 2021-04-18, 14:40 by jjd-uk.)

See this HOW TO https://forum.kodi.tv/showthread.php?tid=362113

In addition on Android you need to set the Minimum protocol version and Maximum protocol version for widest compatibility set SMBv1 as Minimum and SMBv3 as Maximum, see https://kodi.wiki/view/Settings/Services/SMB_Client

**jjd-uk** · 2021-04-17, 15:22

Placeholder

**jjd-uk** · 2021-04-17, 15:22

Placeholder 2

hoppel118 · (This post was last modified: 2021-04-18, 09:50 by hoppel118.)

Great, well done!

One question: In which case does the zeroconf browser work?

For me it works perfectly with my Shield. It shows my smb and my nfs network shares automatically. This way you do not have to configure very much under Kodi. In the backend I use an Openmediavault NAS (Debian) for smb and nfs.

Regards Hoppel

kinggo · 2021-04-18, 10:51

had no idea that it takes so many steps on the windows side Shocked

A very long time since I did anything serious with windows.

**jjd-uk** · (This post was last modified: 2021-04-18, 10:55 by jjd-uk.)

(2021-04-18, 09:50)hoppel118 Wrote: One question: In which case does the zeroconf browser work?

I've been mainly a Windows man over the years, so SMB sharing was learnt by configuring it on Windows 7 and Windows Server 2008 devices. Then later setting it up on Qnap and Synology, and using LibreElec as a client.

The zeroconf browser approach is not one I'm familiar with, does that work SMB2/3 shares? On the Qnap and Synology I use WS-Discovery for discovery to my Windows machines. However Kodi does not yet support that across all platforms yet (was recently added to Kodi Windows build) so that's why the browse SMB doesn't work since the netbios approach became defunct with disabling of SMB1 on most devices.

**jjd-uk** · 2021-04-18, 10:59

(2021-04-18, 10:51)kinggo Wrote: had no idea that it takes so many steps on the windows side A very long time since I did anything serious with windows.

Probably looks long because of the create local account, since in Win 10 there's a lot of hoops to jump through as MS encourage use of a Microsoft Account for users. I use a separate account only for the share access as this is the most secure way to do it and is the way I've done for for over 12 years and never had a single SMB issue.

hoppel118 · (This post was last modified: 2021-04-21, 20:11 by hoppel118.)

(2021-04-18, 10:53)jjd-uk Wrote: The zeroconf browser approach is not one I'm familiar with, does that work SMB2/3 shares? On the Qnap and Synology I use WS-Discovery for discovery to my Windows machines. However Kodi does not yet support that across all platforms yet (was recently added to Kodi Windows build) so that's why the browse SMB doesn't work since the netbios approach became defunct with disabling of SMB1 on most devices.

The Zeroconf Browser works with nfs and smb at least for me.

Code:
hoppel118@omv4:~# smbstatus

Samba version 4.5.16-Debian

PID Username Group Machine Protocol Version Encryption Signing

----------------------------------------------------------------------------------------------------------------------------------------

24897 hoppel118 users XX.XX.XX.XX (ipv4:XX.XX.XX:XX:44262) SMB3_11 - partial(AES-128-CMAC)

How you can see, it uses SMB protocol version 3.11. I don't know how to find out the used NFS version.

Regards Hoppel

**Klojum** · (This post was last modified: 2021-04-21, 18:47 by Klojum.)

(2021-04-21, 18:01)hoppel118 Wrote: I don't how to find out the used NFS version.

In Linux OS'es, here are two examples.

For the NFS server:
rpcinfo -p localhost | grep nfs

Code:
    100003    3   tcp   2049  nfs

    100003    4   tcp   2049  nfs

    100003    3   udp   2049  nfs

For the NFS client:
mount <share>
server:/media/disks on /mnt/srvr1 type nfs4 rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.4.144,local_lock=none,addr=192.168.4.146)

hoppel118 · (This post was last modified: 2021-04-21, 20:09 by hoppel118.)

Thanks, I am running the same version of nfs as you:

Code:
omv4:~# rpcinfo -p localhost | grep nfs

100003 3 tcp 2049 nfs

100003 4 tcp 2049 nfs

100003 3 udp 2049 nfs

So it should be nfs v4 for tcp and v3 for udp connections. Do I understand this right?

Here is what I see, if I open the option "Zeroconf Browser":

This way I do not have to type any path specific parameters, only the username and the password.

Regards Hoppel

**Klojum** · 2021-04-21, 20:13

(2021-04-21, 20:06)hoppel118 Wrote: So it should be nfs v4 for tcp and v3 for udp connections. Do I understand this right?

3 and 4 are the supported versions. I assume OMV (as all file servers) and the NFS client will negotiate the highest supported version with eachother.

Dom61 · (This post was last modified: 2021-06-08, 09:14 by Dom61.)

Good morning.
Sorry for the question, after logging in to the SMB network I verified that
the credentials are saved in the folder: "mediasources.xml" and "passwords.xml"
If I have to transfer my database to another box android connected to the same network,
can I copy these files?
Thank you

**jjd-uk** · 2021-06-09, 10:53

Yes that should work.

Dom61 · 2021-06-09, 11:22

OK. Thank you.

Lotje1990 · 2021-09-15, 16:21

I tried all of these things.

I had to reset my android box. Kodi worked fine, but some other features didn't.
Before the reset i connected kodi 19.1 to my ds218+ with smb with no problems. I have to maps on my ds218. 1 is movies, 1 is series.

After a lot of trying, the mao with movies is now connected with smb. But kodi refuses to connect to my second map (series). Even when i try to change my working movie map, to my series map. On the ds218 all the settings are the same for both maps.

Can someone please help me? Kodi's response when i try to connect to the series mao is 'operation not permitted'. Even though all the settings are the same as the other working map...