Linux samba server for MS clients

[rholme]

From the Linux side - install samba (most of the commands here require sudo inf front)
dnf install samba
or if you like
dnf install samba samba-common samba-common-tools samba-libs samba-python
Now to make it all work you need to configure /etc/samba/smb.conf
a) change the workgroup line to something you want
I found other recommended changes from the net were already the defaults
b) decide on who is going to access samba and how
- for the purposes of this write-up, I will use "user1" as a private user
"group1" as an artificial Linux user with shared samba access for a group of samba users
i.e. there will be a user1 and group1 Linux user (group1 does not have to be able to login)
SO - create the two samba users and give them passwords (what you need to login using samba)
SO - create the two samba users and give them passwords (what you need to login using samba)
in samba.conf (I made a sub-directory in each Linux account to leave other things private)
N.B. - user1 will be in the group smbusers so has access to both areas
Changes to smb.conf file
[group1]
path = /home/group1/exports
valid users = @smbusers
browseable = yes
read only = no
create mask = 0750

[user1]
path = /home/user1/exports
valid users = user1
browseable = yes
read only = no
create mask = 0750

smbpasswd -a user1
smbpasswd -a group1
to change the passwords, simply omit the "-a" later
c) make an entry in the /etc/group file (I used vi, but there are better ways)
- I made the group name smbgroup and the groupid 999 (change as you like)
smbgroup:x:999:user1,group1
d) now to get the whole thing cooking - here are the Fedora root commands (sudo if you like)
systemctl enable smb nmb
firewall-cmd --add-service=samba --permanent
firewall-cmd --reload
systemctl start smb nmb
setsebool -P samba_enable_home_dirs on

--- if you need to change the config file, restart with the below
systemctl restart smb

https://docs.fedoraproject.org/en-US...ers/index.html


From the MS side, the user needs to do five things to mount Samba areas.
a) turn on network discovery (after this you should be able to see the computer by name)
b) make sure you have the samba client service configured
c) make sure you have configured your MS workgroup to match the server configuration workgroup
d) map the samba network drive --- permanently is easier (unless you like to do each time)
e) mapping the server areas - using the above exports (user1 and group1) here are the two alternative ways to do
- one using the server name (if that does not work, use the IP)
\\sambaserver\user1
OR if you cannot “see” the server's – use the fixed IP address (I used the other export in my example)
\\192.168.2.3\group1

You will be prompted for your Samba userid and password.
The Samba userid will be the same as the Linux userid, but the passwords could be the same or different.

https://www.hiroom2.com/2016/06/26/f...th-windows-10/