I’m fairly new to Linux, with more routine in Windows, but Windows doesn’t seem to be able to properly address the large 4TB drives I’m using for storage, so I decided to try and set up a Linux server and put my files there. I’m finding it very difficult to make the Windows computers in my home network see the Linux file server running SAMBA. Given how new I am to Linux, my problem is there’s an overwhelming amount of Internet articles on SAMBA, but the information given is partly conflicting (coming from different versions of SAMBA and likely anything from 0 - 20 years old). Also, I don’t know what error sources there might be; for instance I hadn’t thought about Windows firewall being a problem (and do not know if it can be).
**
So, for now I am hoping somebody can guide me to a guide or how-to which explains how to set up SAMBA as a file server to host for Windows machines. I’m looking for a general explanation of the entries used in the smb.conf file (some are self-explanatory, others are not), and also for better understanding of when or if I need to start the three Samba daemons manually after each change I make in the smb.conf file.**
So far, my impression is I ought to make the linux server the “starter” or controller of the Windows home group (earlier, there was an existing Windows home group, but the Windows machines only saw each other and not the Linux server “joining” it), and
then when that group is up and running, let the Windows machines join it.
I have copies of smb.conf files that seem to work setting up the drives/partitions I want to share with the Windows machines. Basically, I want all Windows machines in the network to have full “guest” read/white access to the 5 4TB HD’s which will be set up on the linux server,
but presently there are only 2 HD’s on the Linux server being shared.
I appreciate any help with gratitude. I will post a copy of the smb.conf file I’m using once I’ve completed my newest attempt to make SAMBA work.
More information:
The Linux server has IP 192.168.1.2 in the internal network, and the Windows machine 192.168.1.3. When I ping from the linux server to the Windows machine, I get the answer that the package is received in 0,3 milliseconds. When I ping from the Windows machine
to the Linux server, I get the message that the packages are sent and received, but that 192.168.1.3 (the windows machine I am pinging from) gets the message “destination host unreachable”.
I have configured the Linux firewall so allow all access from the internal network, and both computers are in my private network behind the same router. So I’m somewhat baffled by the message “destination host unreachable”, given that the windows ping reports that the packages are send and received by the Linux machine.
Here is a printout of the smb.conf file. It was tested with testparm, which reported no problems/errors.
The idea behind this setup is that SAMBA functions as workgroup server as well as file server for the Windows client computers.
smb.conf is the main Samba configuration file. You find a full commented
version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
samba-doc package is installed.
[global]
netbios name = Linuxfilserver
workgroup = MK-NETVAERK
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
logon path = \%L\profiles.msprofile
logon home = \%L%U.9xprofile
logon drive = P:
# usershare allow guests = Yes
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = No
domain master = No
security = user
wins support = Yes
ldap admin dn =
# The following three lines ensure that the Samba
# server will maintain the role of master browser.
# Make sure no other Samba server has its OS level
# set higher than it is here.
local master = yes
preferred master = yes
os level = 65
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = yes
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
guest ok = Yes
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775
Share disabled by YaST
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
write list = root
Shares HD1 main data partition located at /home
[HD1]
path = /home
browsable = yes
writable = yes
guest ok = yes
read only = no
create mask = 0755
Shares HD2 main data partition located at /srv/HD2
[HD2]
path = /srv/HD2
browsable = yes
writable = yes
guest ok = yes
read only = no
create mask = 0755
Shares HD3 main data partition located at /srv/HD3. Rignt now /srv/HD3 is just
an empty directory, but later a 4TH HD will be mounted at srv/HD3
[HD3]
path = /srv/HD3
browsable = yes
writable = yes
guest ok = yes
read only = no
create mask = 0755
Shares HD4 main data partition located at /srv/HD4. Rignt now /srv/HD4 is just
an empty directory, but later a 4TH HD will be mounted at srv/HD4
[HD4]
path = /srv/HD4
browsable = yes
writable = yes
guest ok = yes
read only = no
create mask = 0755
Shares HD5 main data partition located at /srv/HD5. Rignt now /srv/HD5 is just
an empty directory, but later a 4TH HD will be mounted at srv/HD5
[HD5]
path = /srv/HD5
browsable = yes
writable = yes
guest ok = yes
read only = no
create mask = 0755
Shares HD6 main data partition located at /srv/HD6. Rignt now /srv/HD6 is just
an empty directory, but later a 4TH HD will be mounted at srv/HD6
[HD6]
path = /srv/HD6
browsable = yes
writable = yes
guest ok = yes
read only = no
create mask = 0755
Well, it actually works now. The above configuration is valid/usable for a SAMBA/Windows server. The only thing I needed to do extra was to use:
chown nobody:nogroup HD2 (and the same for the other shared partitions/directories) to make sure those have no owner, i.e. all guests can read and write in them.
chmod u+rwx,g+rx.x+rx /HD2 (and the same for the other shared partitions/directories) to give all guests read, write and execution access.
Now I can access all the shared partitions from Windows 10 and read, write, delete, create directories and delete them etc.