PiCorePlayer Samba Password-Mapping network Drive

[jfo]

I'm setting up a piCorePlayer server with LMS for a friend. After some initial problems, his Windows 11 PC has discovered the pi on his network but I can't get past the Network Credentials sign in when trying to map it as a network drive. I assume I should use tc as user name and piCore, the password I entered in the LMS-Samba setup section in picoreplayer? It won't accept these. Can I just re-enter and re-save the password in the Samba setup or is another method needed to check or change the Samba password?
I also tried the MS account credentials but no luck. Any assistance is appreciated.

[jophill]

I'm setting up a piCorePlayer server with LMS for a friend. After some initial problems, his Windows 11 PC has discovered the pi on his network but I can't get past the Network Credentials sign in when trying to map it as a network drive. I assume I should use tc as user name and piCore, the password I entered in the LMS-Samba setup section in picoreplayer? It won't accept these. Can I just re-enter and re-save the password in the Samba setup or is another method needed to check or change the Samba password? ...

IIUC, Samba maintains its own credentials, independent of the host. So, I think picoreplayer's standard host credentials can't be expected to work by default, even though Samba does seem to have been set up to know about a user called "tc".

I just enter a password for user "tc" (not the same password as the host) on the Samba part of the LMS tab. That works for me.

[strebor56]

Did you follow this: https://docs.picoreplayer.org/how-to/add_usb_hdd/

Bonne chance...S

[jfo]

IIUC, Samba maintains its own credentials, independent of the host. So, I think picoreplayer's standard host credentials can't be expected to work by default, even though Samba does seem to have been set up to know about a user called "tc".

I just enter a password for user "tc" (not the same password as the host) on the Samba part of the LMS tab. That works for me.

I have used the same password on other installations successfully. I'm concerned I may have made an entry error when doing the initial setup on this one. It appears the samba password is encrypted and can't be viewed.

Perhaps one of the piCore team can jump in. Can I reset the password by removing Samba on the LMS Setup page in piCorePlayer and then reinstalling it with a new password?

[jfo]

Did you follow this: https://docs.picoreplayer.org/how-to/add_usb_hdd/

Bonne chance...S

Yes, I carefully followed the setup instructions. I have done four servers now and have never encountered this issue.

[d6jg]

There was a Windows update a while ago that required you to enter the username including the workgroup name like this

WORKGROUP\user

Check what you have set the Samba workgroup to be

[jfo]

There was a Windows update a while ago that required you to enter the username including the workgroup name like this

WORKGROUP\user

Check what you have set the Samba workgroup to be

I haven't seen a requirement to include the workgroup name in Win 10 with latest updates, when asked for network credentials.....just the user and password. Have you seen this on Win 11? The server I'm still having trouble with is on a friends Win 11 machine. The samba workgroup is WORKGROUP, matching the PC.

Can anyone from the pCP team tell me if the Samba password can be reset by removing Samba from pCP and re-adding along with a new password?

[paul-]

Not sure what you are asking, you can set the password directly from the web interface.

[jfo]

Not sure what you are asking, you can set the password directly from the web interface.

When mapping a network drive on Win10, credentials were required and I have successfully used the Samba user and password entered in the webUI. On a different PC with a new installation, the credentials were not accepted and I suspected I was using the wrong password. I had set up this server awhile ago but had not installed it yet, so may have assumed the wrong password. I wanted to rule out an incorrect password but could not find a way to confirm or reset. So, my question is...can you just overwrite/reset the Samba password by re-entering/saving in the web UI?
edit: I tried this but it made no difference, so I still don't know if the password was indeed reset, or if there is another issue with permissions, etc
Thanks Paul

[paul-]

Yes, the webui resets the password.

[Viragored]

Did anyone find a proper solution?

I've got the same problem. I've just rebuilt my Pi 3B with LMS and external powered hard drive mounted at /mnt/LMSfiles. All done over the pCP GUI from my Windows 10 PC.
I've set up Samba shares for the music files and the LMS server data, exactly matching what I had before the previous SD card in the Pi died from a power blip. But...

Windows Explorer is saying "Connection refused" when I enter the Id (tc) and password that I used on the Samba setup page. And trying to map the share as a network drive gets the same error. I've been round and round the same loop numerous times, resetting the Samba password, using a plain text source to copy/paste the password to ensure no typing errors creep in, so I need to find what the actual problem is - it's not simply id and password. Permissions somewhere, maybe, or Samba version changes?

At the moment I've got four Pis running on my home network, Samba works properly on the other three, and the workgroup name is correct. (Filezilla can access all the files successfully via sftp.)

In case it's useful, the file permissions for /usr/local/etc/samba/smb.conf are -rw-r--r-- (644), it's owned by root, and the contents are:
[global]
netbios name = JukeBox
workgroup = MSHOME
log file = /var/log/%m.log
max log size = 1000
local master = no
security = user
map to guest = bad user
dns proxy = no
load printers = no
[LMSfiles]
path = /mnt/LMSfiles
create mask = 0777
browseable = yes
writeable = yes
[LMScache]
path = /mnt/part3/slimserver
create mask = 0777
browseable = yes
writeable = yes

EDIT: I've just looked at the owner and permissions for my disk mount point /mnt/LMSfiles. Owner is root, and permissions are drwxrwxrwx (777)

[Paul Webster]

Are the 3 working RPi systems all running pCP as well?

[Viragored]

Are the 3 working RPi systems all running pCP as well?

No, none of them do - one's a Pi 4 mostly running Kodi for playing videos, another Pi 4 runs as a general hack in the workshop, a Pi 3B acts as a network file server with some other tasks. But they do all have Samba shares on them, and access Samba shares on the Windows 10 PC as well as each other.

[Paul Webster]

Anything in the samba logs?
I have not checked to see where they are in pCP but try /var/log or /var/logs

[Viragored]

Anything in the samba logs?
I have not checked to see where they are in pCP but try /var/log or /var/logs

New territory for me! A file at /var/log/smbd.log has this in it:

[2022/11/21 17:49:35.684068, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2022/11/21 17:49:35.696735, 0] ../../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2022/11/21 17:49:35.697106, 0] ../../source3/smbd/server.c:1074(smbd_open_one_socket)
smbd_open_one_socket: open_socket_in: Address family not supported by protocol
[2022/11/21 17:49:35.700305, 0] ../../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2022/11/21 17:49:35.700585, 0] ../../source3/smbd/server.c:1074(smbd_open_one_socket)
smbd_open_one_socket: open_socket_in: Address family not supported by protocol

At that time, I think (but am not sure) I re-started the Pi after having the SD card out to make a backup. If that's right these messages come from Samba starting and not from incoming network requests.