smbclient is good:
osmc@vero:~$ smbclient //192.168.1.40/movies-d --user=vero -m SMB3
smb: \> get test.file /dev/null
getting file \test.file of size 121505600 as /dev/null (15001.0 KiloBytes/sec) (average 14891.8 KiloBytes/sec)
Internal smb in kodi, transfer took 13 secs=9,3MB/sec. Seems decent.
However I tried to play a movie and whenever i tried to play, OSMC would give me sad smiley. So couldn’t test that. Wonder if something is missing in this release?
I wonder if your system isn’t fully up to date.
Can you post a log after sad smiley? Enable debug logging as well
Sam
Hey
Enabled debug logging, rebooted, and started a movie.
log is here: http://paste.osmc.tv/bemeyeveho
Log is anonymised, but shouldn’t matter.
I can try do a clean install again.
If you do that, you can make a backup via My OSMC.
It might end up resolving the issue.
Sam
Something is out of sync:
ii vero364-image-3.14.29-54-osmc 54
ii vero3-mediacenter-osmc 17.6.0-5
so we’re on Kodi 17.6, though my V4K is showing a different version (51)
But your sources.list is still showing Debian jessie:
deb http://ftp.debian.org/debian jessie main contrib non-free
deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb http://apt.osmc.tv jessie mainYep, that’s why I suggested a reinstall.
He has some kind of frankenbuild.
Changing sources to stretch across the board might help, but I’m not sure how invested he is in his current setup
Hi, sorry for late response, but I have been out of town.
I did i clean install, and I updated after added the line “deb http://apt.osmc.tv stretch-devel main”.
The performance is the same-ish when using the fstab smb mount:
osmc@vero:~$ dd if=/mnt/movies-d/test.file of=/dev/null bs=1M count=3072
115+1 records in
115+1 records out
121505600 bytes (122 MB, 116 MiB) copied, 60.2424 s, 2.0 MB/s
Iperf was 195Mbits/sec
I tried starting a movie, after enabling debug logging, and i uploaded a log here: http://paste.osmc.tv/anikoveguq
In this totally clean setup, the wifi does not automaticly connect after reboot, I have to go disable, and enable wifi, before it connects. Not really relevant to my speeds, but wanted to mention it anyways 
That’s not normal at all. What does My OSMC show when this happens?
It just shows wifi enabled, but not connected. There is no networks to see in the right side either. Fixes when i disable and enable it again
Do you have good signal?
I’d try:
connmanctl enable wifi
which should keep WiFi persistently enabled and functional.
Sam
Here’s what the log shows:
Jan 21 13:37:27 vero wpa_supplicant[462]: wlan0: Trying to associate with b0:6e:bf:dc:85:0c (SSID='bst5G' freq=5180 MHz)
Jan 21 13:37:27 vero connmand[377]: ipconfig state 2 ipconfig method 1
Jan 21 13:37:27 vero kernel: Connecting with b0:6e:bf:dc:85:0c ssid "bst5G", len (5) channel=36
Jan 21 13:37:27 vero kernel: dhd_dbg_start_pkt_monitor, 1724
Jan 21 13:37:27 vero wpa_supplicant[462]: wlan0: Associated with b0:6e:bf:dc:85:0c
Jan 21 13:37:27 vero kernel: wl_iw_event: Link UP with BSSID=b0:6e:bf:dc:85:0c
Jan 21 13:37:27 vero kernel: wl_bss_connect_done succeeded with b0:6e:bf:dc:85:0c
Jan 21 13:37:27 vero wpa_supplicant[462]: wlan0: WPA: Key negotiation completed with b0:6e:bf:dc:85:0c [PTK=CCMP GTK=CCMP]
Jan 21 13:37:27 vero wpa_supplicant[462]: wlan0: CTRL-EVENT-CONNECTED - Connection to b0:6e:bf:dc:85:0c completed [id=0 id_str=]
Jan 21 13:37:27 vero connmand[377]: wlan0 {RX} 2 packets 276 bytes
Jan 21 13:37:27 vero connmand[377]: wlan0 {TX} 5 packets 506 bytes
Jan 21 13:37:27 vero connmand[377]: wlan0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Jan 21 13:37:27 vero wpa_supplicant[462]: bgscan simple: Failed to enable signal strength monitoring
Jan 21 13:37:27 vero connmand[377]: wlan0 {newlink} index 3 address CC:B8:A8:12:77:34 mtu 1500
Jan 21 13:37:27 vero connmand[377]: wlan0 {newlink} index 3 operstate 6 <UP>
Jan 21 13:37:28 vero connmand[377]: ipconfig state 3 ipconfig method 1
Jan 21 13:37:28 vero avahi-daemon[347]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.158.
Jan 21 13:37:28 vero avahi-daemon[347]: New relevant interface wlan0.IPv4 for mDNS.
Jan 21 13:37:28 vero avahi-daemon[347]: Registering new address record for 192.168.1.158 on wlan0.IPv4.
Jan 21 13:37:28 vero kernel: wl_bss_connect_done succeeded with b0:6e:bf:dc:85:0c vndr_oui: 00-90-4C 00-10-18
Jan 21 13:37:28 vero connmand[377]: wlan0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
Jan 21 13:37:28 vero connmand[377]: wlan0 {del} route ff00:: gw :: scope 0 <UNIVERSE>
Jan 21 13:37:28 vero connmand[377]: wlan0 {add} address 192.168.1.158/24 label wlan0 family 2
Jan 21 13:37:28 vero connmand[377]: wlan0 {add} route 192.168.1.0 gw 0.0.0.0 scope 253 <LINK>
Jan 21 13:37:28 vero connmand[377]: wlan0 {add} route 192.168.1.1 gw 0.0.0.0 scope 253 <LINK>
Jan 21 13:37:28 vero connmand[377]: wlan0 {add} route 0.0.0.0 gw 192.168.1.1 scope 0 <UNIVERSE>
Jan 21 13:37:28 vero connmand[377]: wlan0 {add} route 159.253.212.250 gw 192.168.1.1 scope 0 <UNIVERSE>
Jan 21 13:37:28 vero connmand[377]: wlan0 {del} route 159.253.212.250 gw 192.168.1.1 scope 0 <UNIVERSE>
Jan 21 13:37:49 vero systemd[1]: Time has been changed
Jan 21 13:37:49 vero systemd[1]: apt-daily-upgrade.timer: Adding 33min 4.717266s random time.
Jan 21 13:37:49 vero http-time[401]: Updated time from Sun Jan 21 12:37:29 UTC 2018 to Sun Jan 21 12:37:49 UTC 2018 using HTTP query to www.google.com
So it looks like it connected without error on wlan0. The ifconfig shows:
====================== ifconfig =================== pi3lDrO1
eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC> mtu 1500
ether c4:4e:ac:10:b9:50 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2 bytes 680 (680.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 40
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 4096
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
inet 192.168.1.158 netmask 255.255.255.0 broadcast 192.168.1.255
ether cc:b8:a8:12:77:34 txqueuelen 1000 (Ethernet)
RX packets 732034 bytes 419440722 (400.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 340776 bytes 19254624 (18.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
so the IP address hasn’t changed and eth0 isn’t connected.