Cannot access shares - Mint to Mint machines

[theedudenator]

I had this working, but had to reinstall some software and add harddrives.

Now I can see the shares on both machines.
But if I try to access the shares I get.

Unable to Mount Windows share: Permission denied

Any suggestions on where to start? Both machines are running the latest mint

[theedudenator]

testparm -sv | grep "encrypt passwords"

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE

encrypt passwords = Yes

[altair4]

Please post the output of the following commands:

Code: Select all

testparm -s

Code: Select all

net usershare info --long

An "unable to mount ..." error is usually a Linux permissions error either at the shared folder or somewhere along the path not a samba error.

[theedudenator]

net usershare info --long
info_fn: file /var/lib/samba/usershares/save-bsmt is not a well formed usershare file.
info_fn: Error was Path is not a directory.
info_fn: file /var/lib/samba/usershares/downloads-bsmt is not a well formed usershare file.
info_fn: Error was Path is not a directory.
info_fn: file /var/lib/samba/usershares/music-bsmt is not a well formed usershare file.
info_fn: Error was Path is not a directory.
info_fn: file /var/lib/samba/usershares/photos-bsmt is not a well formed usershare file.
info_fn: Error was Path is not a directory.
info_fn: file /var/lib/samba/usershares/homemovies is not a well formed usershare file.
info_fn: Error was Path is not a directory.
info_fn: file /var/lib/samba/usershares/profiles-bsmt is not a well formed usershare file.
info_fn: Error was Path is not a directory.
info_fn: file /var/lib/samba/usershares/movies-bsmt is not a well formed usershare file.
info_fn: Error was Path is not a directory.
[raid-bsmt]
path=/media/pete/raid
comment=
usershare_acl=Everyone:F,
guest_ok=y

[Downloads]
path=/home/pete/Downloads
comment=
usershare_acl=Everyone:F,
guest_ok=y

[theedudenator]

If I go to networking on the "main" machine and try to access the share on the "main" machine I get the same error.

If I select properties on the share drive it says.

The permissions of "smb" could not be determined

[altair4]

***** You didn't post the output of this command:

Code: Select all

testparm -s

But there is a problem with at least this share:

[raid-bsmt]
path=/media/pete/raid
comment=
usershare_acl=Everyone:F,
guest_ok=y

You allow guest access to something under /media/pete. Only one user will be able to get past the "pete" directory and that's "pete". Make the guest user appear to be "pete" for these shares:

Edit /etc/samba/smb.conf and add the following line - right under the workgroup line:

Code: Select all

force user = pete

Save the file then restart samba:

Code: Select all

sudo service smbd restart

Wait a few minutes then try to access the share again.

[theedudenator]

is there a better place to mount my disk that I want for network access?

[theedudenator]

testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
server string = %h server (Samba, Linux Mint)
server role = standalone server
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
usershare allow guests = Yes
panic action = /usr/share/samba/panic-action %d
idmap config * : backend = tdb
force user = pete

[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
printable = Yes
print ok = Yes
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers

[altair4]

is there a better place to mount my disk that I want for network access?

Since /media/$USER is where most external USB type devices are mounted one usually doesn't have a choice. But if you are mounting things yourself just go up the tree to /media/raid for example.

From a practical sense you will probably need to use "force user" anyway since when the client adds something to a shared folder as guest "pete" will have read access but not write.

[exsencon]

Well, a few days ago I decided to try Mint 17.1 and I must say I am rather pleased with it coming from Ubuntu since 7.04 I think.
With Ubuntu 14.10 I ran into a lot of problems and that's the reason of my switch.
Anyway, allthough I managed to get my printer working wireless from my Laptop to my Desktop (printer is USB-connected there) with samba, there still is a samba-file problem.
My systems: Dell 520 Dimension 2HDD, one with WinXP,the other one with a lot of Linuxes,3GB RAM
Dell 1501 Inspiron Laptop with 120GBHDD,2GBRAM with WINXP and Mint 17.1 in dualboot
Installation of Mint went without any problems really,to get the wireless I just had to do:
sudo apt-get install firmware-b43-installer after putting in my pw.

Now,so far ,so good.
Now we come to samba,just trying to have my Laptop shares on my Winxp Desktop and vice-versa. Well, as usual there is always a problem with samba. I gave up a long time ago asking what the problem really is,I probably will never know.
OK, now with Mint it is like this:
Laptop Mint and Desktop WinXP both have as workgroup WORKGROUP, so it shouldn't be that big a problem,but well,it is.
When I try my Mint Laptop with Network I get that ****little menu saying passwd for workgroup domain and it goes just on and on.
When I try my WnXP desktop it simply says I have no permission to use this network resource while at least in theory I should have all the permissions.
Anyway, here is my testparm -s:

Code: Select all

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Processing section "[print$]"
Processing section "[share]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
	server string = %h server (Samba, Linux Mint)
	server role = standalone server
	map to guest = Bad User
	obey pam restrictions = Yes
	pam password change = Yes
	passwd program = /usr/bin/passwd %u
	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
	unix password sync = Yes
	syslog = 0
	log file = /var/log/samba/log.%m
	max log size = 1000
	dns proxy = No
	usershare allow guests = Yes
	panic action = /usr/share/samba/panic-action %d
	idmap config * : backend = tdb
	read only = No

[printers]
	comment = All Printers
	path = /var/spool/samba
	read only = Yes
	create mask = 0700
	printable = Yes
	print ok = Yes
	browseable = No

[print$]
	comment = Printer Drivers
	path = /var/lib/samba/printers
	read only = Yes

[share]
	comment = Home
	path = /home/zeger/Desktop/904 shared

And my net usershare info --long

[904 shared]
path=/home/zeger/Desktop/904 shared
comment=
usershare_acl=Everyone:F,
guest_ok=y

I don't see any errors there allthough I find my net usershare a bit short.
Simple question: Can anybody help me out?
I know samba is kind of tricky having run 14-15 linuxes so far, always had problems but most of the time found a solution,if it's not a file problem it's a permission problem.
Now to be complete and I know this is a long post I just want to add this simple thing:
When I go simply File-connect to server I just put smb://my IPaddress then put workgroup-username and password and up it goes-no problem wether I put in my Desktop or my Laptop IPaddress.
Finally my smb.conf:

Code: Select all

[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, Linux Mint)

# 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

security = user

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


read only = 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.
# 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

[share]
comment = Home
path = /home/zeger/Desktop/904 shared
browseable = yes

# 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

So,now what?

[altair4]

You should have started your own topic. Samba in an all Linux network is a lot easier and the subject of this topic.

On the Mint samba server you essentially have one share and because you have another parameter in the wrong place it looks like this:

[share]
comment = Home
path = /home/zeger/Desktop/904 shared
browseable = yes
read only = no

So what you have is a share that allows write access to all samba clients that can provide the correct credentials to the server.

My guess is you didn't tell samba who those users are and what credentials to use. So let's say you want to access this share as the user "zeger". You have to add that user to the samba password database:

Code: Select all

sudo smbpasswd -a zeger

It will first ask for sudo's password then it will ask you what password to use for samba.

You may have some interference with any shares you created from Nemo since all you posted was this:

I don't see any errors there allthough I find my net usershare a bit short.

Need to see the entire output to see if something is misconfigured or duplicated.

As for this:

When I go simply File-connect to server I just put smb://my IPaddress then put workgroup-username and password and up it goes-no problem wether I put in my Desktop or my Laptop IPaddress.

I would suggest you go through the Samba Checklist

[exsencon]

First of all sorry for "missposting" my post.
Followed the samba checklist all the way and after reboot it works as a charm!
Thanks a lot.
See about the printer now,though it is working with samba, I still would have it working wireless just with the the drivers and an lpd file,but that will be another post.
Thanks again.