New answers tagged samba
0
No, the 'guest' user with 'guest ok = yes' set on a share is generally the user 'nobody' which doesn't have a password. What you could do is create a user with a password, remove 'map to guest = bad user' from global and 'guest ok = yes' from the share, add 'valid user = your_new_user' to the share and use the username and password when connecting to the ...
0
Okay, here is the minimum you need for a guest only share, that doesn't use SMBv1:
[global]
security = USER
map to guest = Bad User
client min protocol = SMB2
server min protocol = SMB2
[share]
path = /smbshare
read only = No
guest ok = yes
guest only = yes
When you have got that working and then want authenticated users, ...
1
I think I figured out the problem: You mention you want no security, so I suppose you didn't add any user and ran smbpasswd. User ecb may be the user you login to your Debian system.
Yet on your config you have security = user, which means user authentication.
So for no authentication you only need:
[global]
map to guest = Bad User
[Share]
...
5
Colons aren’t valid characters on SMB/CIFS shares — Windows uses them for drive letters. The failing directory name contains one, which is why mkdir fails.
0
Why the permissions are set as they are?
When a Unix-style program creates a new file, it will specify initial permissions for it. These initial permissions specified are typically 0666 or rw-rw-rw- for regular files, and 0777 or rwxrwxrwx for directories or executable files. This is something coded right into each program and not easily changeable.
But ...
0
OK, have you created users with 'smbpasswd -a username' (needs to be run as root) ?
If you haven't, then your guest account 'myuser' will not work. This means that no one will be able to access your share.
Authentication (based on your smb.conf) works like this:
A user connects to Samba and if the user is known and supplies the correct password, they are ...
0
Finally found it. The samba-ad-dc service was never started.
Details on fixing that are at https://wiki.samba.org/index.php/Managing_the_Samba_AD_DC_Service_Using_Systemd
No idea why the first page never referenced the second. Still some issues, but that at least got me past this problem.
1
Stop using sssd.
From Samba >= 4.8.0, Shares and sssd are incompatible. If you want shares, then you must use winbind.
1
It sounds like your Samba share is on the root partition. If you expect this to be the largest section, you can:
Copy the entire contents of the Samba share to the 2TB drive.
Delete the contents of the old Samba share, but keep the folder. E.g. If your share is in /opt/samba, delete everything inside /opt/samba but keep the folder.
Mount the 2TB drive at /...
Top 50 recent answers are included
