Hi,
I’ve been having issues with SMB shares on OSMC on my Pi. I’ve done a bit of googling and it seems a common issue and I found a thread whereby I can set up fstab based Samba share mounts. I followed the tutorial and successfully set up a mount
//192.168.0.100/Films /mnt/Films cifs x-systemd.automount,noauto,rw,iocharset=utf8,username=wiggies,password=password,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770,vers=2.0 0 0
but when I cd /mnt/Films to test it I get -bash: cd: /mnt/Films: No such device. Although if I cd /mnt and then ls it list a Films mount.
I bit more googling finds to an article about installing smbclient and running the following command smbclient -L 192.168.0.100 -U wiggies this then requests a password and then gives me this error Connection to 192.168.0.100 failed (Error NT_STATUS_IO_TIMEOUT).
192.168.0.100 being the fixed IP of my windows 10 desktop
wiggies being the user account of my windows 10 desktop
password being the password I use to log onto my windows 10 desktop
Now I’m completely stuck and no amount of googling has helped. It would be greatly appreciated if anyone can help me proceed with this.
Sorry if the above information is lacking the important detail. This is all very new for me.
Thanks
Have you tried other SMB versions than 2.0? Try 1.0 and 3.0.
Thanks for your reply. I had tried 3.0 before the 2.0 but didn’t try 1.0 as I’d read something about it being bad for security?!? Anyhow, have tried 1.0 but that hasn’t made any difference.
Does the failure of smbclient to connect mean it’s a setting on my PC rather than the SSH activities?
The smbclient failure does make me think it may be a problem on your Windows 10 system, so I’d suggest checking the settings there.
Version 1.0 is less secure, but probably OK if you are on a home network with no access from the outside world allowed.
Tried all sorts on my PC to no avail :-/
Thanks for your time.
Were you able to connect using Kodi shares instead of fstab? Do you have any other devices to test from?
Are you sure that the IP on the W10 system didn’t change? What do you get if from the Pi you try:
$ ping 192.168.0.100
Also try smbclient with debugging enabled:
$ smbclient -d 10 -L 192.168.0.100 -U wiggies
I used to be connected using the smb share on Kodi but that stopped working and I couldn’t fix it, hence looking at alternatives and finding info on fstab.
Just setting up a Win 10 laptop to see if I can do the regular share from Kodi to it.
The PC static IP address was the first the first thing I checked.
Pinging my PC from the SSH on the Pi works…
64 bytes from 192.168.0.100: seq=0 ttl=128 time=4.809 ms
64 bytes from 192.168.0.100: seq=1 ttl=128 time=4.649 ms
64 bytes from 192.168.0.100: seq=2 ttl=128 time=2.764 ms
Running the smbclient with debugging returns the following before I enter my password…
osmc@osmc:~$ smbclient -d 10 -L 192.168.0.100 -U wiggies
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
scavenger: 10
dns: 10
ldb: 10
tevent: 10
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
scavenger: 10
dns: 10
ldb: 10
tevent: 10
Processing section “[global]”
doing parameter config file = /etc/samba/smb-local.conf
doing parameter workgroup = WORKGROUP
doing parameter security = user
doing parameter follow symlinks = yes
doing parameter wide links = no
doing parameter unix extensions = no
doing parameter lock directory = /var/cache/samba
doing parameter load printers = no
doing parameter printing = bsd
doing parameter printcap name = /dev/null
doing parameter disable spoolss = yes
doing parameter log level = 1
doing parameter map to guest = bad user
doing parameter read raw = Yes
doing parameter write raw = Yes
doing parameter strict locking = no
doing parameter min receivefile size = 16384
doing parameter use sendfile = true
doing parameter aio read size = 2048
doing parameter aio write size = 2048
doing parameter socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=131072 SO_SNDBUF=131072
pm_process() returned Yes
lp_servicenumber: couldn’t find homes
added interface eth0 ip=192.168.0.71 bcast=192.168.0.255 netmask=255.255.255.0
Netbios name list:-
my_netbios_names[0]=“OSMC”
Client started (version 4.5.12-Debian).
After password I get…
Connecting to 192.168.0.100 at port 445
Connecting to 192.168.0.100 at port 139
Connection to 192.168.0.100 failed (Error NT_STATUS_IO_TIMEOUT)
Setting up the Win 10 Laptop worked flawlessly straight away. So it does look like some rogue setting on my desktop.
So I understand you connection from OSMC to WIn 10 on your laptop works fine?
Just for the records to connect to Win10 with smbclient we need to add SMB3 so full comment would be smbclient -m SMB3 -d 10 -L 192.168.0.100 -U wiggies
Thanks for your reply. Yes the connection from OSMC to the Win 10 laptop does work fine.
smbclient with SMB 3 as requested…
osmc@osmc:~$ smbclient -m SMB3 -d 10 -L 192.168.0.100 -U wiggies
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
scavenger: 10
dns: 10
ldb: 10
tevent: 10
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
scavenger: 10
dns: 10
ldb: 10
tevent: 10
Processing section “[global]”
doing parameter config file = /etc/samba/smb-local.conf
doing parameter workgroup = WORKGROUP
doing parameter security = user
doing parameter follow symlinks = yes
doing parameter wide links = no
doing parameter unix extensions = no
doing parameter lock directory = /var/cache/samba
doing parameter load printers = no
doing parameter printing = bsd
doing parameter printcap name = /dev/null
doing parameter disable spoolss = yes
doing parameter log level = 1
doing parameter map to guest = bad user
doing parameter read raw = Yes
doing parameter write raw = Yes
doing parameter strict locking = no
doing parameter min receivefile size = 16384
doing parameter use sendfile = true
doing parameter aio read size = 2048
doing parameter aio write size = 2048
doing parameter socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=131072 SO_SNDBUF=131072
pm_process() returned Yes
lp_servicenumber: couldn’t find homes
added interface eth0 ip=192.168.0.71 bcast=192.168.0.255 netmask=255.255.255.0
Netbios name list:-
my_netbios_names[0]=“OSMC”
Client started (version 4.5.12-Debian).
Thanks for all your help. I took the hit and reset my Windows 10 as everything was now pointing at some miscellaneous setting in there that had borked everything. The regular Kodi shares are working again.
I’m running into the same issues that cerbera1971 was having. I did a debug like was recommended and came back with the following info. Would prefer to reset Windows 10 only as a last resort.
osmc@osmc:~$ smbclient -m SMB3 -d 10 -L 192.168.1.110 -U Brian
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
scavenger: 10
dns: 10
ldb: 10
tevent: 10
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
scavenger: 10
dns: 10
ldb: 10
tevent: 10
Processing section “[global]”
doing parameter workgroup = WORKGROUP
doing parameter dns proxy = no
doing parameter log file = /var/log/samba/log.%m
doing parameter max log size = 1000
doing parameter syslog = 0
WARNING: The “syslog” option is deprecated
doing parameter panic action = /usr/share/samba/panic-action %d
doing parameter server role = standalone server
doing parameter passdb backend = tdbsam
doing parameter obey pam restrictions = yes
doing parameter unix password sync = yes
doing parameter passwd program = /usr/bin/passwd %u
doing parameter passwd chat = Enter\snew\s\spassword:* %n\n Retype\snew\s\spassword:* %n\n password\supdated\ssuccessfully .
doing parameter pam password change = yes
doing parameter map to guest = bad user
doing parameter usershare allow guests = yes
pm_process() returned Yes
lp_servicenumber: couldn’t find homes
added interface eth0 ip=192.168.1.21 bcast=192.168.1.255 netmask=255.255.255.0
Netbios name list:-
my_netbios_names[0]=“OSMC”
Client started (version 4.5.12-Debian).
Enter Brian’s password:
Connecting to 192.168.1.110 at port 445
Connecting to 192.168.1.110 at port 139
Connection to 192.168.1.110 failed (Error NT_STATUS_IO_TIMEOUT)