[RPi4] Windows 11 Explorer can't access LibreELEC hard drive

  • Hi all. New to forum.

    Attached 2TB hard drive "New Volume" to network attached, Raspberry Pi usb port. I can ping. Can play media from local Windows 11, Kodi app. I can SSH to Raspberry Pi.

    I would like to see attached drive in Windows explorer in order to move files to drive. Right now it's listed under network but "Windows can't access \\Libreelec".

    I can only ssh as root as default Pi, Raspberry log in is denied as wrong (forgot) password. I can see contents of sd card when connected to pc in explorer.

    I have read numerious threads on different scenarios but no luck. Any help would be appreciated. Sorry if this topic has been covered.

  • The default password is defined in LibreELEC settings and is libreelec/libreelec not root/libreelec. Modern Windows OS versions will need to use authentication so you need to have auth on.

  • Thank you..

    Verified all services settings correct in Samba. Am I correct to believe that is all I need on the Raspberry side? Or is there some settings on the sd card I need to make? I can ping the RP4. Can play media from local Windows 11, Kodi app usb new volume.

    I have a DS214play that shows up in explorer with no issues. So does that mean authentication is set?

    I have a feeling it's just one setting that's throwing me off.

    Thanks for your help sir...

  • You should only need to enable Samba with min SMBv2, max SMBv3 (the default) and with auto-sharing of USB drives turned on (the default). Modern Windows require SMB authentication so that needs to be on (not enabled by default).

    If "Can play media from local Windows 11, Kodi app usb new volume." means the Kodi SMB client on a Windows Kodi install can play media from the LE Samba shares? .. the shares are working. The Kodi SMB client is different from the OS client (explorer, etc.).

    Have you tried accessing via \\192.168.2.1 (or whatever the IP is) instead of \\LIBREELEC?

    Option B .. use an SFTP client and transfer files over SSH instead.