Yeah, now that you say that, it makes sense - I came across a comment on the same thread that finally cleared it up where someone mentioned that the factory-integrated Plex server software handles the incoming SMB connections.
Still sucks. I just disabled the incoming SMB connection feature. I’ll turn it on when I need to use it. This way nothing on my network is vulnerable to any security risks that SMB1 is vulnerable to.
LOL. Don’t think I even knew what I was saying, but I tried. I spent 6 hours troubleshooting the Nvidia Shield’s recent SMB update. Just wanted the right command for LE CLI to list current SMB connections with more detail than the GUI.
I didn’t know it, but checking that wouldn’t have helped anyway. Turns out Nvidia released a “partial” update - SMB2/3 (outgoing connections only) - for their Android TV 8.0 implementation.
I could finally connect (outgoing only) to LE via SMB 2/3.
I just wanted to connect to the Shield from a computer for small file transfers via SMB 2/3 also.
I didn’t even consider for a second that Nvidia would be stupid enough to release a single-direction (outgoing) SMB update in 2019. Idiots.
LE to Shield arrows backwards above. Oops. I was making the Shield -----> LE connection without an issue.
So I thought it was just macOS failing to connect...until I tried Windows 10 Pro (which has SMB1 module disabled by default now), and it wouldn't connect either.
So I'm playing around with a 3rd party file explorer app on the Shield (X-Plore) and I find a tiny note (SMB1). So Android, as an OS, couldn't tell me that it was failing to allow inbound SMB 2/3 connections. It had to be a 3rd party app. That thing has been nothing but a networking nightmare for 2 years now. Until LibreELEC 9 Alpha, it was the only device I owned that could spit out Atmos/DTS:X. One of the Linux kernel updates Milhouse did along the way finally allowed proper audio.
Still unclear as to whether the Shield update not allowing incoming SMB2/3 connections is intentional.
BTW, it would still be nice to have a command to display detailed information on LE's current SMB connections.
Thx
I should also mention that I manually added a previously non-existing file - /etc/nsmb.conf - in macOS to also say min 2 / max 3
#nsmb.conf
[default]
protocol_vers_map=6Apple updated the man docs for a number of items in Mojave, and they are no longer using this style:
smb_neg=smb3_onlyFrom man doc:
protocol_vers_map Bitmap of SMB Versions that are enabled
"Bitmap of SMB Versions that are enabled" can be one of:
7 == 0111
SMB 1/2/3 should be enabled
6 == 0110
SMB 2/3 should be enabled
4 == 0100
SMB 3 should be enabled
Hi,
TL;DR? See subject line - may be all I need. / If you read below and have any additional insight....I would be super grateful.
If this should be in support, mods feel free to move - I wasn't sure...
LE CLI command via SSH may help me figure out what the heck my 2nd video device is doing (re: SMB version) after new SMB update, but I don't know the LE command and I'm not having luck trying commands from searches / other distro forums:
LE 8.95.2 on Intel NUC, under LibreELEC Settings ---> Connections, I can see 2nd device (Nvidia Shield TV / Android 8.0) but the info is limited to interface, state, IP - the basics.
After Nvidia finally released an update a couple of days ago with support for SMBv3, I checked SMB connections, and at least I can tell it no longer requires SMBv1. (See 3 & 4 below)
On macOS, I can't test this - I can no longer browse or do anything with the Shield. (Aware of SMBv2 browsing limitation, don't know if that's entirely the issue.)
1) macOS ---/---> Shield (fail)
[after Nvidia's "SMBv3" update]
2) macOS -------> LE (success)
["smbutil" indicates SMB v3.02 connection to LE.]
___________________________________
3) LE (min 2 max 3) ---------> Shield (success)
4) LE (min 3 max 3) ----/----> Shield (fail)
5) Shield ---------> LE (success)
I just want to find out what the Shield is allowing since LE connects to it, but macOS doesn't. (And get macOS connected againNo SMB settings anywhere in the Shield settings, after digging through menus 20 times. I'm guessing, as has been noted with others before, that Nvidia may have thrown in their own "flavor" of SMB just like macOS and some Linux distros.
If you got this far, thank you...
Alex
Oh, really? I should have specified but I was in fact referring to the generic build. I thought it would have caught the kernel in the bootloader’s scan, but maybe not in the kernel’s native locale.
I am manually reinstalling LibreELEC, because of course the installer isn't happy with my FAT EFI partition. I'm just getting into the trenches on this stuff, but I believe that the standard LibreELEC install is legacy boot. I just wiped my Intel NUC and changed the Visual BIOS settings to UEFI.
I have Ubuntu 18.04 also, and my bootloader has two entries for it - one for the efi file and one for the kernel.
I read somewhere that I may need to place a copy of the kernel on the EFI partition, but that it still needs to know where to point for the actual installation...(FYI, using a large drive - EFI is /dev/sda1, LE system /dev/sda2, LE storage /dev/sda3, empty ext4 /dev/sda4, Ubuntu /dev/sda5)
It will only boot to Ubuntu, with the SYSTEM and KERNEL files from the 8.2.5 tarball in the LE system partition.
I’ve actually spent, conservatively speaking, 20 or more hours trying to get all this set up right - mostly for learning purposes.
I installed LE as close to the front of the disk as possible because I know it likes to own the disk, but my media is external and LE doesn't need 1TB.
Any ideas?
Would adding EFI stub loader support to the Linux kernel be something that you guys can do? It eliminates the need to create *.efi files. My bootloader scans and finds most distros via the kernel with no issue, but I can't get it to work with LibreELEC.
Haha, that would have been an appropriate title. Honestly I'm having more trouble than most because I have almost every major environment using Kodi. (Some in the same room - I just choose which OS/device I feel like using.)
I have Kodi on all of these:
*Nvidia Shield (Android TV)
*Apple TV 4K / tvOS (Yes, I basically "sideload" Kodi test builds, via X-code on my Mac. And I'm sharing someone's developer account, so it doesn't expire)
*macOS
*Windows 10 Pro (dual boot on the Mac)
*LibreELEC (Linux of course) on my Intel NUC.
*And at one time I had it on my iPhone (iOS) for 7 days, but I didn't want to pay the developer fee.
*I had it on my Raspberry Pi at one point also.
Seven different OS environments! (Only 5 currently.)
But the ones I actually use for Kodi are LibreELEC & the Android TV. The Apple TV has a paid app called Infuse, and it is a much better experience in tvOS than Kodi.
So yeah - I tinker too much.
This thread alone is a learning experience for me.
I posted on the forum with issues when 8.2 was released, and I'm guilty of not seeing the wall of text on day 1. (I installed the update within LibreELEC - that had quite a bit to do with it.) But after receiving a forum response, I read that wall of text. 
It's not really that much.
I've always been someone who reads release notes, though - except that time, of course. Even if I only understand 1/3 of the bullet points. I've learned things just from context reading release notes.
After the read, I resolved some issues that I had by teaching myself (I know - it's simple.) the relevant parameters to edit a copy of the samba.conf.sample file in /storage/.conf/.
Made some changes to the home items and made my version the live version. Easy.
Backed the edited version up too.
By the way, I can understand why (especially mainstream) Linux distros would retain legacy compatibility - Ubuntu wants to make moving from Windows or macOS as pain-free as they can, I'm sure.
What really bugs me is WHY Apple insists on making this ridiculous, unpredictable system (stack?). I'm serious - I'd like to know why. They TRY to give the impression that their OS is the easy-to-use alternative to Windows....
Christ - some standardization amongst the OS vendors would make life a lot frickin easier for devs and end users alike. That's just wild chewitt.
CvH - that, my friend, is the ultimate goal. I was just hired 2 days ago after being unemployed for over a month. And it's the highest paying job I've ever had (though not by a huge margin.)
Anyway - I have a shiny Synology 4-bay unit picked out (DS418) AND at least so far I have one 8TB WD Red HDD. A few months back I got a WD Easystore external drive when Best Buy had them for $150, and followed a comprehensive serial number list and guide from SlickDeals and Reddit DataHoarders. The result - I ended up with a WD80EFAX w/256MB cache - which you can't even buy anymore. What seems to be it's successor with a 128MB cache sells as an internal drive for $249 at NewEgg.
Anyway - $750 in (3) more hard drives since I'll be shucking my external, and $369 for the NAS. I can finally free myself from the chains of SMB. Yeahhh!
Sorry for the long post I'm just excited!
Hello,
I regularly add images to the colored studio logo Textures.xbt file. I use the Kodi Texture Tool. When I finish up and copy the modified file back to Its location in the add-on's resources folder, LibreELEC then refuses to read it at all. Of course I make sure there is only one studio entry in the Nfo file, otherwise it doesn't help at all. Anyway, LibreELEC (AFTER file mod) only displays the text from Nfo file Studio line. No image.
If I copy the EXACT same updated Textures.xbt file into Kodi on my Shield / Android TV or macOS installations, its flawless.
Any ideas? 
Interesting - I’ve altered files (every time there’s an update to the skin, or I reinstall altogether, I have to redo some customizations) within that folder more times than I can remember, and it’s never failed. I usually use my Mac to connect to the share in the GUI, but when that failed, I connected via SSH, and it said "read only file system."
I'm having some memory loss here, but I think I rebooted LibreELEC and accessed it via Windws to solve the problem.
By the way - since you guys seem to know about skins/addons - is there any particular way that an add-on must be zipped for Kodi to install it properly?
I use Kodi on my Apple TV 4K as well, but I can't access the file system. This should have been an easy workaround: I unzipped the skin, added 4 small images to a folder already containing hundreds, and altered references to those images - changing about a half line of existing inconsequential code on 7-8 existing XML files. Then, I zipped it back up, and it wouldn't install to Kodi in any OS. The installation simply fails.
I'm having the same problem. IN /storage/.kodi/addons.......
Yes I did have it set to allow for 1-3 previously. Now it's just set to allow 2-3. You're right - makes sense to avoid defaults.
Some more thinking also got me wondering if Little Snitch connection monitoring software (recent acquisition - I kinda forgot about it) possibly blocked the incoming request. My Intel NUC w/LibreELEC is in another room, so I may have missed a prompt asking me if I was OK with the incoming request.
Thanks for your insight!
I wasn't aware that I had the ability to manually set an alternate parameter specifically for SMB in user.conf - thanks for the heads up. It's clear that macOS won't access LibreELEC set to min/max 3/3 without any manual intervention. I've heard over and over again that macOS has had ongoing problems or strange ways of having it implemented, so that doesn't surprise me.
I'll play with user.conf and see if I can figure out what macOS is actually able to deal with. But since you confirmed that SMB 2 is generally safe, now I know I'm good otherwise to leave it at 2/3. (Makes sense that this setting became the default in 8.2)
Strangely, on my tvOS (Apple TV 4K) Kodi installation, I can access my Mac where I store my music, but I can't access LibreELEC, where I have my videos stored, ever since I bumped up to SMB2 minimum. (this may also be related to an alias issue) I do have another tvOS video player (Firecore Infuse) that just added SMB3 support in their last update, so it's not like the OS is somehow making it impossible to go above SMB1. But I read somewhere that Memphiz is having trouble spending a lot of time on development all by himself, understandably.
Thanks guys.
Chewitt - that makes total sense. Having Kodi installed on other machines running various operating systems - I wasn't thinking about the fact that the OS is of course acting as the server here and Kodi the client.
Milhouse - You have a great point. I will set my client settings to the same (SMB2/SMB3) as the server settings manually.
With the newer SMB version(s) being backwards compatible [or so I'm told] - is it safe to say that SMB2 maintains this compatibility while not being subject to the exploits you developers are concerned about with SMB1?
I tried just setting the min/max to SMB3/SMB3, knowing my Nvidia Shield would lose access, but my Mac running High Sierra also lost access - that I wasn't expecting, so I just went back to SMB2/SMB3.
With LibreELEC--->Services--->SMB min/max settings in place, will they simply override Services--->SMB client settings that you find in all versions of Kodi?
I've usually kept them in sync manually, but now I just have the Kodi SMB settings set to "none" for min/max. Am I right to assume that the LibreELEC settings are king?
Wow I was really stuck inside the box with regard to thinking on this one. macOS likes you to create "Sharing Only" accounts that sort of exist in the background, but you're totally right - I was easily able to do that with one named kodi, password kodi... nice and simple.
The strange thing is, now it works, but I never entered that username and password in LibreELEC at any point. I selected the option in LibreELEC settings under "Services" to "Use Samba Password Authentication," for a sec, but I noticed that the defaults were username libreelec, and pw libreelec. I was going to try putting in kodi, kodi (as I had created on my Mac) but it worked without even bothering. So strange. I've been trying to get it to work for months and it finally just works....
Thanks for the suggestion.