So I should edit QNAP's smb.conf and add the settings. Or should I edit LibreELEC smb.conf and add these settings?
QNAP .. because you are setting "client" min protocol and it's the client.
Posts by chewitt
-
-
Security for local private network isnt big issue, SMB1 is used more as 20years...
People who experienced the WannaCry ransomware attack might disagree with your bad advice.
zx-9r Samba versions from 4.1 > 4.6 will always attempt to connect at SMB1 unless smb.conf forces SMB2 via "client min protocol" and I'd guess the Samba version in the QNAP falls in that range. If LE samba is set for SMB1-3 it connects at SMB1 and things work. If LE is set for SMB2-3 the client still attempts to connect at SMB1 and things fail. From Samba 4.7 onwards the connection default is SMB3_11 and the client auto-negotiates lower versions if required.
-
-
Budget requires some kind of Amlogic box, but LE/Kodi has no browser and most devices will be limited to 720p for Netflix etc. as they must be software decoded. The same box running Android will have a browser and probably supports hardware decoded 1080p netflix.
-
Perhaps reset Kodi audio settings to defaults. I use a WP2 as the family "daily driver" and have never seen anything like that.
-
On Android Kodi includes Samba (smbclient) as part of the image and it is an older version that does not support SMB2. The Samba version should be bumped to a newer version that supports SMB2/3 for Kodi Leia.
smbstatus is not included in LE
-
The OS will auto-mount the drive unless there is an issue with the filesystem. The usual issue we see reported is "unsafe eject" from Windows which leaves the filesystem in an unclean state. If not, it might be worthwhile running chkdsk.exe over the drive.
-
The "failed to start Xorg" message indicates there are no Xorg graphics drivers that support that card in the OS image. It dates from 2009/10 which is probably just beyond the current drivers we use; AMD support for older cards isn't so great. The LE boot splash that you see is just the boot splash.
-
Please post a debug log that proves the box is clean then, as requested.
-
Yup.. that pretty much describes the current mess of the Kodi-on-Linux hardware scene. Amlogic S905D devices would probably be "least worst" at the moment, but there is no "best" box to recommend.
-
The /storage/.config folder supports user provided config in a specific list of folders and pulse-daemon.conf.d is not one of them. You'd have to recompile the OS image with changes to make that work.
-
I have here None minimum and None maximum protocol version
but all this is in section Client , then i mean server protocol is untuched by this....
"Go into LE settings" where server things are configured, not Kodi settings where client things are configured.
-
LE 8.2 has newer drivers than OE, but with Intel newer doesn't necessarily mean better. Have a play with a current Milhouse release to see if things resolve under a newer (again) kernel and drivers.
-
"ImportError: No module named pkg_resources"
missing python module of some description
-
It is probably something hacked-up from one of the community builds. It is nothing to do with us, and as there is no attempt to provide sources for the image I would currently assume they are GPL violators as well.
-
Kodi on Android currently supports only SMB1. Go into LE settings. Under services set the minimum SMB version to SMBv1. That should be the only change required. It would alsobe recommended to use a username/password for access.
-
No hablo español, lo siento.
-
It's hard to comment. Apart from poor range we're not aware of any issues with the RPi3 onboard wifi .. and without some error messages to guide investigation there isn't much to go on.
