Linux 9 Samba Help

[DerpDiamonds]

So I am trying to setup a samba server where I can regularly send my windows backups to this server. But windows can recognise the server, but won't access the files within it.

 

I have been at this for a couple days and do not know the problem. If you need any logs or files I will send them. Please help!

 

Thanks!

[jj9987]

What do you mean by "won't access the files within it"?

Can you see the shares? Have you given correct permissions? Are you using a guest user or some other one?

[DerpDiamonds]

I am using the account when I setup the machine, and by "won't access the files within it" I mean that I cannot view the folders.

 

Do you want the samba config?

[Jarsky]

17 minutes ago, DerpDiamonds said:

Do you want the samba config?

 

 

Yeah can you post the smb.conf 

[DerpDiamonds]

Just out at the moment, will do when I get back.

[Jarsky]

I probably wont be around then, but you should have an entry that looks something like...

 

[media]
    path = /mnt/media
    read only = no
    writeable = yes
    browseable = yes
    valid users = DerpDiamonds, myuser2, myuser3
    create mask = 0644
    directory mask = 0755
    force user = DerpDiamonds

 

[media] = share name, so that will be \\myserver\<share name>

path = obviously the path of the share 

valid users = the usernames of all the users you want to give access to the share

force user = if you set this, it means any file written to the share will be written as this username

 

of course your share should have the appropriate permissions at the file system level as well. 

you can check the ownership using the "ls -l <pathname>" command...e.g ls -l /mnt/media

if you have multiple users, you should create a group, add all your users to that group, and chown the directory to the group. 

[DerpDiamonds]

1 hour ago, Jarsky said:

I probably wont be around then, but you should have an entry that looks something like...

 

[media]
    path = /mnt/media
    read only = no
    writeable = yes
    browseable = yes
    valid users = DerpDiamonds, myuser2, myuser3
    create mask = 0644
    directory mask = 0755
    force user = DerpDiamonds

 

[media] = share name, so that will be \\myserver\<share name>

path = obviously the path of the share 

valid users = the usernames of all the users you want to give access to the share

force user = if you set this, it means any file written to the share will be written as this username

 

of course your share should have the appropriate permissions at the file system level as well. 

you can check the ownership using the "ls -l <pathname>" command...e.g ls -l /mnt/media

if you have multiple users, you should create a group, add all your users to that group, and chown the directory to the group. 

What permissions do I need?

[Jarsky]

17 minutes ago, DerpDiamonds said:

What permissions do I need?

 

That all depends on how you're configuring it.

If you're configuring it for a single user account then just chmod the directory to 755 and the example samba config above. 

 

If you don't know what that means you should look up Unix/Linux Permissions. 

Permission is broken into 3 categories of users - Owner - Group - World (other users).

You give those users read, write, execute or any combination of the 3, by assigning a decimal value. 

 

755 is representative of rwxr-xr-x . that means Owner = Read/Write/Exec  Group = Read/Exec  Others = Read/Exec 

 

If you want multiple different users, then you'll want to get more complicated and chown the directory to the group, chmod the permission to 775 and might want to override the permissions in samba rather than applying a mask as well. 

 

 

[Aspect11]

So I added in my share:

[backup]
   path = /home/jack/Documents/JackBackup
   read only = no
   writeable = yes
   browseable = yes
   valid users = jack
   create mask = 0644
   directory mask = 0755
   force user = jack

But when I go to ma a network folder on windows typing in:

\\192.168.1.134\backup

It just comes up with 'Windows cannot access \\192.168.1.134\backup'. What do I do?

 

The updated smb.conf:

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set 
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = no

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

[backup]
   path = /home/jack/Documents/JackBackup
   read only = no
   writeable = yes
   browseable = yes
   valid users = jack
   create mask = 0644
   directory mask = 0755
   force user = jack

 

[Jarsky]

2 minutes ago, DerpDiamonds1 said:

So I added in my share:

[backup]
   path = /home/jack/Documents/JackBackup
   read only = no
   writeable = yes
   browseable = yes
   valid users = jack
   create mask = 0644
   directory mask = 0755
   force user = jack

But when I go to ma a network folder on windows typing in:

\\192.168.1.134\backup

It just comes up with 'Windows cannot access \\192.168.1.134\backup'. What do I do?

 

The updated smb.conf:

 

 

Since you only have one user - you can remove that line "force user"

If you browse too \\192.168.1.134 then can you see the "backup" alias?

P.S have you restarted samba after making the change to smb.conf? (service samba restart)

Does your linux server have a firewall running? If its Debian 9 - run 'sudo ufw status'  Samba requires ports UDP 137/138 & TCP 139/445 to be open

[Aspect11]

1 minute ago, Jarsky said:

 

Since you only have one user - you can remove that line "force user"

If you browse too \\192.168.1.134 then can you see the "backup" alias?

P.S have you restarted samba after making the change to smb.conf? (service samba restart)

Does your linux server have a firewall running? If its Debian 9 - run 'sudo ufw status'  Samba requires ports UDP 137/138 & TCP 139/445 to be open

So I have removed force user, I ran 'sudo ufw status' and it said "sudo: ufw: command not found". Also I have restarted and I cannot view \\192.168.1.134 because it is not appearing in the network section of windows. Any other questions or is it broken?

[Jarsky]

3 minutes ago, DerpDiamonds1 said:

So I have removed force user, I ran 'sudo ufw status' and it said "sudo: ufw: command not found". Also I have restarted and I cannot view \\192.168.1.134 because it is not appearing in the network section of windows. Any other questions or is it broken?

 

try running 'service iptables status' then...(i thought debian9 used ufw)

it sounds like firewall is blocking it

[Aspect11]

3 minutes ago, Jarsky said:

 

try running 'service iptables status' then...(i thought debian9 used ufw)

it sounds like firewall is blocking it

It says "Unit iptables.service could not be found." Do I need to install it or something?

[Jarsky]

No we just want to make sure its not being blocked by firewall. 

Your Windows computer is in the workgroup "WORKGROUP" right? 

 

[Aspect11]

6 minutes ago, Jarsky said:

No we just want to make sure its not being blocked by firewall. 

Your Windows computer is in the workgroup "WORKGROUP" right? 

 

I think so yeah.

[Aspect11]

I just sorted it, turns out that the location I was changing was the wrong one. So I just reverted the changes and fixed it. Thanks for all you help!