Windows 10 stopped seeing CoreELEC on network

Open the file with nano to edit it

nano /run/samba/smb.conf

Use arrow keys to locate the cursor.

See bottom bar for instructions on saving changes.

That did it, thanks, it saved my “local master = no”. Now to test it.

Here is what my lanscan shows, and my Tronsmart is the master. I will power it down, and see what becomes the new master. My Synology used to become the master and it did not affect the Windows explorer from finding the networked devices.

Also, here is what my Windows explorer looks like when my CoreELEC device is NOT the master.

Powered off my Tronsmart Windows 10 microPC (it runs 24/7), which was the network MASTER. Now, I only have my desktop computer (which I am using now) to show up under Windows explorer (that is my issue). None of my other networked devices show up at all. The shortcuts to the devices still work. Also, the Lanscanner app is still looking for the Tronsmart master, so it shows nothing. I will leave the Tronsmart powered off until later tonight, and see it anything changes.

Windows%20explorer

Guys, I found this older post and did as it says and bingo, smb shares opened right up - https://www.schkerke.com/wps/2015/06/windows-10-unable-to-connect-to-samba-shares/
FYI I did do some of the actions in the post ie editing the smb.conf, but nothing worked till I followed the post in the link.

1 Like

Great find. I didn’t know, that Microsoft changed the behavior of connections to non-secured samba shares.
Glad you solved it with this solution.

Very frustrating and a lot of stuff tried. Nice simple solution. Thanks again for your help.

I did what the link showed, but still did not work. I created the new Dword and rebooted, but still nothing shows in my Windows explorer, except the computer I am on now. GRRRRRRRRRRRRR

Sorry it didn’t work. After all I have done to try to fix this I was surprised when it worked. Dumb question maybe, but did you go back into regedit and make sure the dword file got saved? On the kodi box the only other thing I did was to change min to smb2 and max to 3.

Yes,

I should switch to Linux, it does NOT have these issues…

It didn’t work for me, brother.