dperson / samba

Samba docker container
GNU Affero General Public License v3.0
1.5k stars 509 forks source link

Problems with Username/Password on a share #439

Closed masterlog80 closed 1 year ago

masterlog80 commented 1 year ago

Hello guys, I am trying to setup a docker container to mount a folder and sharing on Windows. However, despite I can create a share that everyone can access, I am unable to create a working set of Username/Password for it. To better clarify, I have used this example YAML, and I have raised the logs level by adding -g "log level = 3". https://github.com/dperson/samba/blob/master/docker-compose.yml The access to tje share Mount is fine (no User/Pass request), while I can't access to Bobs Volume getting an Error on Windows: per my understanding the User should be bob with password bobspasswd, but it's not working. Below is what I see on the container's logs:

2023-05-27T12:08:23.883007727Z Allowed connection from 192.168.*.* (192.168.*.*)
2023-05-27T12:08:23.883669212Z idmap range not specified for domain '*'
2023-05-27T12:08:23.883867517Z Failed to fetch domain sid for MYGROUP
2023-05-27T12:08:23.884554142Z Forced user smbuser
2023-05-27T12:08:23.884826805Z Forced group smb
2023-05-27T12:08:23.884876642Z make_connection_snum: Connect path is '/tmp' for service [IPC$]
2023-05-27T12:08:23.884888266Z Initialising default vfs hooks
2023-05-27T12:08:23.884900532Z Initialising custom vfs hooks from [/[Default VFS]/]
2023-05-27T12:08:23.884912944Z Initialising custom vfs hooks from [streams_xattr]
2023-05-27T12:08:23.884949596Z Initialising custom vfs hooks from [recycle]
2023-05-27T12:08:23.884962356Z Initialising custom vfs hooks from [fruit]
2023-05-27T12:08:23.884974806Z Initialising custom vfs hooks from [catia]
2023-05-27T12:08:23.884985849Z fruit_connect: Enabling durable handles for Time Machine support on [IPC$]
2023-05-27T12:08:23.885292934Z error reading meta xattr: Not supported
2023-05-27T12:08:23.885311713Z error reading meta xattr: Not supported
2023-05-27T12:08:23.885379690Z pc-home (ipv4:192.168.10.10:64744) connect to service IPC$ initially as user smbuser (uid=100, gid=101) (pid 88)
2023-05-27T12:08:23.886958532Z error reading meta xattr: Not supported
2023-05-27T12:08:23.886978361Z error reading meta xattr: Not supported
2023-05-27T12:08:23.886991164Z get_referred_path: |Bobs Volume| in dfs path \192.168.*.*\Bobs Volume is not a dfs root.
2023-05-27T12:08:23.887002806Z smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_NOT_FOUND] || at ../../source3/smbd/smb2_ioctl.c:312
2023-05-27T12:08:23.887703153Z Allowed connection from 192.168.*.* (192.168.*.*)
2023-05-27T12:08:23.887720586Z create_connection_session_info: guest user (from session setup) not permitted to access this share (Bobs Volume)
2023-05-27T12:08:23.887754651Z create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
2023-05-27T12:08:23.887767799Z smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_ACCESS_DENIED] || at ../../source3/smbd/smb2_tcon.c:142
2023-05-27T12:08:23.888559558Z Allowed connection from 192.168.*.* (192.168.*.*)
2023-05-27T12:08:23.888576728Z create_connection_session_info: guest user (from session setup) not permitted to access this share (Bobs Volume)
2023-05-27T12:08:23.888588389Z create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
2023-05-27T12:08:23.888600942Z smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_ACCESS_DENIED] || at ../../source3/smbd/smb2_tcon.c:142
2023-05-27T12:08:37.819426573Z pc-home (ipv4:192.168.10.10:64744) closed connection to service IPC$
2023-05-27T12:08:38.844558178Z Closing idle connection
2023-05-27T12:08:38.844684949Z got a SHUTDOWN message
2023-05-27T12:08:38.848382578Z Server exit (normal exit)

I don't really understand what is ongoing there. Is there someone able to mount a folder to the container and then share it with a Username/Password on Windows devices? If yes, I'd appreciate if you can provide the docker-compose file!

Thanks

masterlog80 commented 1 year ago

Mhhh... after rebooting Windows and reinstalling the SMB part the issue has solved