unable to connect to samba shares

while following the guide from the first video I can into an issue with not being able to connect to the servers samba shares from any device. They would be listed as available from the server. Found that I needed to update the global section of my smb.conf file to the following before I was able to connect from my MAC.

[global]
server string = Servarr
workgroup = WORKGROUP
client min protocol = SMB3
client max protocol = SMB3
client smb encrypt = required
client signing = required
server min protocol = SMB3
server max protocol = SMB3
ntlm auth = ntlmv2-only
security = user
map to guest = Bad User
name resolve order = bcast host
bind interfaces only = yes
#hosts allow = 10.0.0.0/24
#hosts deny = 0.0.0.0/0

[BenRamins]

I'm gonna piggy back on the notes above for anyone who may come across this in the future:

if you're on windows, here's how's you'd want to see what shares the container is advertising:
(replace with the IP of the container)
net view \\10.0.0.100

now, if you get System error 53 - you should try the notes above from the previous user, then try again.

If you're like me, you MIGHT now be getting System error 5 which means access is denied

you may want to double check you created an smb user. I didn't - thought I'd wing it with root, but smb didn't like that, so once I created a dedicated smb user, it worked.

but wait, there's more: if the machine/device you're trying to access the shares from is on a different L2 subnet than the container, the shares will not appear automatically under "Network" or "Network locations". You have to go to File Explorer, paste the following:
(replace with the IP of the container)
\\10..0.0.100\
if prompted for credentials, enter the smb user credentials - and you should now see the folders
once you see the folders (in TechHut's example, "data" and "docker") and if you want to persist them in your file explorer, right click a folder and then select "Map network drive", you will then be prompted to assign a letter to the drive and whether you want auto signin, and it will then persist on your machine even if it's on a different L2 subnet.