Choose style:

Author Topic: Samba: The Dance That's Killing Me...or...Yet Another Windows Access Issue  (Read 238 times)

0 Members and 1 Guest are viewing this topic.

Offline radiobob

  • nOOb
  • *
  • Posts: 4
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): Peppermint Ten
I really am enjoying using Peppermint.  Now, I'm not a full-on noob, but I'm hardly proficient and I'm having problems that make me want to rip my (remaining) hair out.

I took an old Vista PC someone gave me (Intel Core2 4400 2GB RAM) and installed Peppermint 10 with an eye toward using it download and store syndicated shows for my radio station; all other PCs on the intended network are Win 10 or Win 7.

Having read Samba tutorials until I have intense strabismus, watched YouTube videos, read forum posts, tried the famous Tony Bronze fix (https://forum.peppermintos.com/index.php/topic,7086.0.html), I'm still unable to get my test bed Win 10 machine to consistently read from the Peppermint PC, OR to be able to write to the latter at all.

I've set the share name so it's different from its associated directory name, I've turned the firewall on and off, I've edited and re-edited and re-edited the samba/smb.conf file--both via terminal and the Samba GUI (a bad idea since the GUI apparently keeps commenting out things)--and chmod 777'd (is that a verb?) the heck out of the shares, and got as far as being able to browse and open files from the Win 10 box, but not to write.

To make matters even more (if that's possible) frustrating, now I can no longer even browse from the Windows PC!

Once I get this licked, then I get to make myself even crazier playing with wget and crontab.  In the meantime, I welcome help, suggestions, thoughts, recipes, etc.  Thanks!


UPDATE FROM ORIGINAL POST
I have an AtomicPi single board computer, also running Peppermint; I am having NO problems sharing/reading/writing files from the Win 10 PC!  I even tried a copy 'n' paste of the A-Pi's smb.conf on the former Vista machine; no joy...
----
Following is edited for brevity:

Code: [Select]
#======================= Global Settings =======================

[global]

## Browsing/Identification ###

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

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

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

# 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 ####

>snip

#### 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 ###########

>snip
############ 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
username map = /etc/samba/smbusers
security = user
; encrypt passwords = yes
guest ok = yes
guest account = videodrome

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

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
[homes]
comment = Home Directories
        browseable = yes

# 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 = 0777

# 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 = 0777

>snip

[Syndication]
comment = Syndicated Shows
path = /media/pepper/Radio
writeable = yes
browseable = yes


« Last Edit: December 13, 2019, 03:04:48 pm by PCNetSpec »

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26468
  • Karma: 2871
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Samba: The Dance That's Killing Me...or...Yet Another Windows Access Issue
« Reply #1 on: December 13, 2019, 03:05:31 pm »
So I take it you've enabled SMB v1 in both Peppermint and Win10 ?


Instructions for enabling SMB v1 in Peppermint 9 can be found here:
https://forum.peppermintos.com/index.php/topic,7086.msg72516.html#msg72516

Instructions for making sure SMB v1 is installed in Windows 10:-
  • Search in the start menu for ‘Turn Windows features on or off’ and start it.
  • In the resulting dialog window search for ‘SMB1.0/CIFS File Sharing Support’ in the list of options offered, and tick the box next to it.
  • Click OK and Windows will download/install it .. You should then be prompted to reboot the PC, but if not reboot anyway.
(it's important that you REBOOT Windows because it does that very 'Windowy' thing where it's installed as part of the shutdown and bootup process)
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline radiobob

  • nOOb
  • *
  • Posts: 4
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): Peppermint Ten
Re: Samba: The Dance That's Killing Me...or...Yet Another Windows Access Issue
« Reply #2 on: December 13, 2019, 06:49:06 pm »
No luck!  In fact, now the Atomic Pi will no longer let me access its files from the Windows 10 box.  One step forward, three back...
« Last Edit: December 13, 2019, 06:54:03 pm by radiobob »

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26468
  • Karma: 2871
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Samba: The Dance That's Killing Me...or...Yet Another Windows Access Issue
« Reply #3 on: December 14, 2019, 06:40:59 am »
First let's backup smb.conf
Code: [Select]
sudo cp -v /etc/samba/smb.conf /etc/samba/smb.conf.backup

Now let's try editing smb.conf (the following assumes you Windows workgroups is WORKGROUP):
Code: [Select]
gksudo xed /etc/samba/smb.conf
and try making it read:-
Code: [Select]
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]

# Allow smb version 1
name resolve order = bcast host
client max protocol = NT1

## Browsing/Identification ###

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

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# 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 =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[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 = yes

# 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.
# Un-comment the following parameter to make 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

[Syndication]
path = /media/pepper/Radio
writeable = yes
; browseable = yes
guest ok = yes
Then give /media/pepper/Radio 777 permissions
Code: [Select]
sudo chmod -R 777 /media/pepper/Radio
« Last Edit: December 14, 2019, 06:43:19 am by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline radiobob

  • nOOb
  • *
  • Posts: 4
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): Peppermint Ten
Re: Samba: The Dance That's Killing Me...or...Yet Another Windows Access Issue
« Reply #4 on: December 14, 2019, 02:20:53 pm »
Tried all of the above--setting the smb.conf letter-for-letter to your blueprint,, but still no go.  Found some workarounds involving forcing a user that I can't begin to explain (but that work), so I'm going to call this "closed", if not officially "solved".
You have my deep appreciation!

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26468
  • Karma: 2871
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Samba: The Dance That's Killing Me...or...Yet Another Windows Access Issue
« Reply #5 on: December 14, 2019, 02:42:36 pm »
Can you link to the solution/workaround .. so we can see what you did and possibly figure out where the problem was ?
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline radiobob

  • nOOb
  • *
  • Posts: 4
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): Peppermint Ten
Re: Samba: The Dance That's Killing Me...or...Yet Another Windows Access Issue
« Reply #6 on: December 14, 2019, 05:45:29 pm »
This is a synthesis of bits and pieces gleaned from several sources.  I don't know enough to know whether or not this is a "best practice", but it seems to work.

1.  I set the smb.conf like this:
[usb]
guest ok = Yes
path = /media/atomicpi/62FD-20C1
read only = No
force user = atomicpi

2.  I removed an existing Windows username:
sudo pdbedit -L
sudo smbpasswd -x winusername #[in this case, "videodrome"]

3.  Restarted both the Atomic Pi and the Windows 10 machine.  At first I couldn't gain access to the USB drive.  I tried this:
\\atomicpi-MF-001.local

Initially I could not read or write to the USB, then I could!  I've swapped out several USB drives since, changing the relevant parts of the smb.conf file.

While I generally understand what's going on, I do not know the nomenclature and syntax well enough, much less the relevant commands, so I have to rely on others (for now) to guide me.  It is particularly frustrating when I follow procedures others have used or generally accepted practices, and errors nonetheless occur and/or things flat out don't work.  For example, when I ran testparm after adding the lines you suggested at the top of the smb.conf, I got a bunch of errors (sorry, I can no longer reproduce them without going backwards).  Anyway, frustration after following a proven step-by-step template, only to have it not work, seems to be status quo for tech stuff, doesn't it?

Again, thanks!