i get the following error

i am able to access the share using kodi
the services are running

# systemctl status smb.service 
● smb.service - Samba SMB Daemon
   Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-10-12 19:41:46 SAST; 11s ago
# systemctl status nmb.service 
● nmb.service - Samba NMB Daemon
   Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-10-12 19:41:46 SAST; 4s ago

smb.conf looks like this

# cat /etc/samba/smb.conf
# The following configuration re-enables the deprecated, insecure SMB1 protocol 
#
# ';' also denotes a comment (typically used for configuration parameters)
#

# Disable insecure protocols by default (SMB2 = Win 7, SMB3 = Win 10)
client ipc min protocol = NT1
client ipc max protocol = SMB3
client min protocol = NT1
client max protocol = SMB3
server min protocol = SMB2
server max protocol = SMB3

kyrios yep i had a look at the section Enabling legacy SMB1/CIFS protocol support

    tried the following

    $ smbclient -U user -L 192.168.1.102

    Unable to initialize messaging context
Enter WORKGROUP\user's password: 

Sharename       Type      Comment
---------       ----      -------
print$          Disk      Printer Drivers
kodi            Disk      
IPC$            IPC       IPC Service (Samba 4.9.11-Debian)
Reconnecting with SMB1 for workgroup listing.
smbXcli_negprot_smb1_done: No compatible protocol selected by server.
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
Unable to connect with SMB1 -- no workgroup available

    i actually just had a look at the samba server (running on a debian machine).

    it has in /etc/samba/smb.conf

      workgroup = WORKGROUP
   min protocol = SMB2
   max protocol = SMB3

      milomak Why are you trying to connect with SMB1 when the server requires at least SMB2?

          the solution lies here

          on the server remove min and max protocol

          just have

          protocol = SMB3

          DataDrake before i posted here while i was trying to figure this all out, smbclient indicated that SMB1 was being used. but as you can see from the post above the issue is now solved.

            Also when Solus will adopt the next major version of samba (4.11+), SMB1 will be completely withdrawn as it is completely obsolete and insecure.