<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Right now, im just trying to get my
Linux box to ACCESS a "share" on my WD N750 Router. I have 2
SSD's attached to the USB ports on it. Win systems see them no
problem.<br>
<br>
Smbk4 is asking for passwords. i put in the username and password
I use for MY root access.... it ignores it.<br>
This while in the Smb4K app.<br>
<br>
<br>
Adding a account? the device has no account.... it is setup as a
public share.<br>
<br>
<br>
Again, let me remind everyone. I AM CLUELESS.... Please do not
make assumptions that I know something that to all of you is
fundamental regarding this..... if I did, I probably wouldn't
need help.<br>
<br>
<br>
SO FAR: I THINK what you folks are saying is that I have to
authenticate in MY machine. The concept here eludes me.<br>
<br>
<br>
<big>Is this how it works:<br>
<br>
Machine A (Linux box)<br>
Machine B Router serving SSD shares<br>
<br>
Smb4K Sees shares<br>
Samba requires authentication LOCAL in MY machine to access
Samba "Universe"</big><br>
--------------------------<br>
<br>
<br>
On 08/20/2013 10:48 PM, James Dugger wrote:<br>
</div>
<blockquote
cite="mid:CAOXWiHjhPoxE5E-1rER1Ltq5RUWp3GDLY0ATUyppbtACg_4zuQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">Wayne,</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">If
you can see the share but can't access it than most likely you
need to set up samba passwords for the users on your system
with:</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">$
sudo smbpasswd -a <username> </div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">If
you are trying to access the share with a user account on the
client that that doesn't exist on the server than you will
need to add that user to the server. You need to do this with
the Linux command </div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">$
sudo adduser</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">samba
will prompt for a password. Once this is complete You will
need to select the share on the client system, it will prompt
for the password and then that client given access.</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">Other
things to check. Are your file permissions correct for the
users that you are trying to connect with?</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">i.e.
if you have user rights for your share of 0775 does the user
you are connecting with included in those rights?</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">instead
of using "writeable = yes" you ,ight consider using "write
list = username1 username2"</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">You
will need to restart samba after any of these changes</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">$
sudo service smbd restart</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small;color:#0b5394">Just
some thoughts.</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Aug 20, 2013 at 9:15 PM, Wayne
Davis <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:waydavis@centurylink.net" target="_blank">waydavis@centurylink.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">#<br>
# Sample configuration file for the Samba suite for Debian
GNU/Linux.<br>
#<br>
#<br>
# This is the main Samba configuration file. You should read
the<br>
# smb.conf(5) manual page in order to understand the options
listed<br>
# here. Samba has a huge number of configurable options most
of which<br>
# are not shown in this example<br>
#<br>
# Some options that are often worth tuning have been
included as<br>
# commented-out examples in this file.<br>
# - When such options are commented with ";", the proposed
setting<br>
# differs from the default Samba behaviour<br>
# - When commented with "#", the proposed setting is the
default<br>
# behaviour of Samba but the option is considered
important<br>
# enough to be mentioned here<br>
#<br>
# NOTE: Whenever you modify this file you should run the
command<br>
# "testparm" to check that you have not made any basic
syntactic<br>
# errors.<br>
# A well-established practice is to name the original file<br>
# "smb.conf.master" and create the "real" config file with<br>
# testparm -s smb.conf.master >smb.conf<br>
# This minimizes the size of the really used smb.conf file<br>
# which, according to the Samba Team, impacts performance<br>
# However, use this with caution if your smb.conf file
contains nested<br>
# "include" statements. See Debian bug #483187 for a case<br>
# where using a master file is not a good idea.<br>
#<br>
<br>
#======================= Global Settings
=======================<br>
<br>
[global]<br>
<br>
## Browsing/Identification ###<br>
<br>
# Change this to the workgroup/NT-domain name your Samba
server will part of<br>
workgroup = workgroup<br>
<br>
# server string is the equivalent of the NT Description
field<br>
server string = %h server (Samba, Ubuntu)<br>
<br>
# Windows Internet Name Serving Support Section:<br>
# WINS Support - Tells the NMBD component of Samba to enable
its WINS Server<br>
# wins support = no<br>
<br>
# WINS Server - Tells the NMBD components of Samba to be a
WINS Client<br>
# Note: Samba can be either a WINS Server, or a WINS Client,
but NOT both<br>
; wins server = w.x.y.z<br>
<br>
# This will prevent nmbd to search for NetBIOS names through
DNS.<br>
dns proxy = no<br>
<br>
# What naming service and in what order should we use to
resolve host names<br>
# to IP addresses<br>
; name resolve order = lmhosts host wins bcast<br>
<br>
#### Networking ####<br>
<br>
# The specific set of interfaces / networks to bind to<br>
# This can be either the interface name or an IP
address/netmask;<br>
# interface names are normally preferred<br>
; interfaces = <a moz-do-not-send="true"
href="http://127.0.0.0/8" target="_blank">127.0.0.0/8</a>
eth0<br>
<br>
# Only bind to the named interfaces and/or networks; you
must use the<br>
# 'interfaces' option above to use this.<br>
# It is recommended that you enable this feature if your
Samba machine is<br>
# not protected by a firewall or is a firewall itself.
However, this<br>
# option cannot handle dynamic or non-broadcast interfaces
correctly.<br>
; bind interfaces only = yes<br>
<br>
<br>
<br>
#### Debugging/Accounting ####<br>
<br>
# This tells Samba to use a separate log file for each
machine<br>
# that connects<br>
log file = /var/log/samba/log.%m<br>
<br>
# Cap the size of the individual log files (in KiB).<br>
max log size = 1000<br>
<br>
# If you want Samba to only log through syslog then set the
following<br>
# parameter to 'yes'.<br>
# syslog only = no<br>
<br>
# We want Samba to log a minimum amount of information to
syslog. Everything<br>
# should go to /var/log/samba/log.{smbd,nmbd} instead. If
you want to log<br>
# through syslog you should set the following parameter to
something higher.<br>
syslog = 0<br>
<br>
# Do something sensible when Samba crashes: mail the admin a
backtrace<br>
panic action = /usr/share/samba/panic-action %d<br>
<br>
<br>
####### Authentication #######<br>
<br>
# "security = user" is always a good idea. This will require
a Unix account<br>
# in this server for every user accessing the server. See<br>
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html<br>
# in the samba-doc package for details.<br>
security = user<br>
<br>
# You may wish to use password encryption. See the section
on<br>
# 'encrypt passwords' in the smb.conf(5) manpage before
enabling.<br>
; encrypt passwords = yes<br>
<br>
# If you are using encrypted passwords, Samba will need to
know what<br>
# password database type you are using.<br>
; passdb backend = tdbsam<br>
<br>
obey pam restrictions = yes<br>
<br>
# This boolean parameter controls whether Samba attempts to
sync the Unix<br>
# password with the SMB password when the encrypted SMB
password in the<br>
# passdb is changed.<br>
unix password sync = yes<br>
<br>
# For Unix password sync to work on a Debian GNU/Linux
system, the following<br>
# parameters must be set (thanks to Ian Kahan <<<a
moz-do-not-send="true"
href="mailto:kahan@informatik.tu-muenchen.de"
target="_blank">kahan@informatik.tu-muenchen.de</a>>
for<br>
# sending the correct chat script for the passwd program in
Debian Sarge).<br>
passwd program = /usr/bin/passwd %u<br>
passwd chat = *Enter\snew\s*\spassword:* %n\n
*Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully*
.<br>
<br>
# This boolean controls whether PAM will be used for
password changes<br>
# when requested by an SMB client instead of the program
listed in<br>
# 'passwd program'. The default is 'no'.<br>
pam password change = yes<br>
<br>
# This option controls how unsuccessful authentication
attempts are mapped<br>
# to anonymous connections<br>
map to guest = bad user<br>
<br>
########## Domains ###########<br>
<br>
# Is this machine able to authenticate users. Both PDC and
BDC<br>
# must have this setting enabled. If you are the BDC you
must<br>
# change the 'domain master' setting to no<br>
#<br>
; domain logons = yes<br>
#<br>
# The following setting only takes effect if 'domain logons'
is set<br>
# It specifies the location of the user's profile directory<br>
# from the client point of view)<br>
# The following required a [profiles] share to be setup on
the<br>
# samba server (see below)<br>
; logon path = \\%N\profiles\%U<br>
# Another common choice is storing the profile in the user's
home directory<br>
# (this is Samba's default)<br>
# logon path = \\%N\%U\profile<br>
<br>
# The following setting only takes effect if 'domain logons'
is set<br>
# It specifies the location of a user's home directory (from
the client<br>
# point of view)<br>
; logon drive = H:<br>
# logon home = \\%N\%U<br>
<br>
# The following setting only takes effect if 'domain logons'
is set<br>
# It specifies the script to run during logon. The script
must be stored<br>
# in the [netlogon] share<br>
# NOTE: Must be store in 'DOS' file format convention<br>
; logon script = logon.cmd<br>
<br>
# This allows Unix users to be created on the domain
controller via the SAMR<br>
# RPC pipe. The example command creates a user account with
a disabled Unix<br>
# password; please adapt to your needs<br>
; add user script = /usr/sbin/adduser --quiet
--disabled-password --gecos "" %u<br>
<br>
# This allows machine accounts to be created on the domain
controller via the<br>
# SAMR RPC pipe.<br>
# The following assumes a "machines" group exists on the
system<br>
; add machine script = /usr/sbin/useradd -g machines -c "%u
machine account" -d /var/lib/samba -s /bin/false %u<br>
<br>
# This allows Unix groups to be created on the domain
controller via the SAMR<br>
# RPC pipe.<br>
; add group script = /usr/sbin/addgroup --force-badname %g<br>
<br>
########## Printing ##########<br>
<br>
# If you want to automatically load your printer list rather<br>
# than setting them up individually then you'll need this<br>
# load printers = yes<br>
<br>
# lpr(ng) printing. You may wish to override the location of
the<br>
# printcap file<br>
; printing = bsd<br>
; printcap name = /etc/printcap<br>
<br>
# CUPS printing. See also the cupsaddsmb(8) manpage in the<br>
# cupsys-client package.<br>
; printing = cups<br>
; printcap name = cups<br>
<br>
############ Misc ############<br>
<br>
# Using the following line enables you to customise your
configuration<br>
# on a per machine basis. The %m gets replaced with the
netbios name<br>
# of the machine that is connecting<br>
; include = /home/samba/etc/smb.conf.%m<br>
<br>
# Most people will find that this option gives better
performance.<br>
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html<br>
# for details<br>
# You may want to add the following on a Linux system:<br>
# SO_RCVBUF=8192 SO_SNDBUF=8192<br>
# socket options = TCP_NODELAY<br>
<br>
# The following parameter is useful only if you have the
linpopup package<br>
# installed. The samba maintainer and the linpopup
maintainer are<br>
# working to ease installation and configuration of linpopup
and samba.<br>
; message command = /bin/sh -c '/usr/bin/linpopup "%f"
"%m" %s; rm %s' &<br>
<br>
# Domain Master specifies Samba to be the Domain Master
Browser. If this<br>
# machine will be configured as a BDC (a secondary logon
server), you<br>
# must set this to 'no'; otherwise, the default behavior is
recommended.<br>
# domain master = auto<br>
<br>
# Some defaults for winbind (make sure you're not using the
ranges<br>
# for something else.)<br>
; idmap uid = 10000-20000<br>
; idmap gid = 10000-20000<br>
; template shell = /bin/bash<br>
<br>
# The following was the default behaviour in sarge,<br>
# but samba upstream reverted the default because it might
induce<br>
# performance issues in large organizations.<br>
# See Debian bug #368251 for some of the consequences of
*not*<br>
# having this setting and smb.conf(5) for details.<br>
; winbind enum groups = yes<br>
; winbind enum users = yes<br>
<br>
# Setup usershare options to enable non-root users to share
folders<br>
# with the net usershare command.<br>
<br>
# Maximum number of usershare. 0 (default) means that
usershare is disabled.<br>
; usershare max shares = 100<br>
<br>
# Allow users who've been granted usershare privileges to
create<br>
# public shares, not just authenticated ones<br>
usershare allow guests = yes<br>
guest ok = yes<br>
; guest account = nobody<br>
username map = /etc/samba/smbusers<br>
<br>
#======================= Share Definitions
=======================<br>
<br>
# Un-comment the following (and tweak the other settings
below to suit)<br>
# to enable the default home directory shares. This will
share each<br>
# user's home director as \\server\username<br>
;[homes]<br>
; comment = Home Directories<br>
; browseable = no<br>
<br>
# By default, the home directories are exported read-only.
Change the<br>
# next parameter to 'no' if you want to be able to write to
them.<br>
; read only = yes<br>
<br>
# File creation mask is set to 0700 for security reasons. If
you want to<br>
# create files with group=rw permissions, set next parameter
to 0775.<br>
; create mask = 0700<br>
<br>
# Directory creation mask is set to 0700 for security
reasons. If you want to<br>
# create dirs. with group=rw permissions, set next parameter
to 0775.<br>
; directory mask = 0700<br>
<br>
# By default, \\server\username shares can be connected to
by anyone<br>
# with access to the samba server. Un-comment the following
parameter<br>
# to make sure that only "username" can connect to
\\server\username<br>
# The following parameter makes sure that only "username"
can connect<br>
#<br>
# This might need tweaking when using external
authentication schemes<br>
; valid users = %S<br>
<br>
# Un-comment the following and create the netlogon directory
for Domain Logons<br>
# (you need to configure Samba to act as a domain controller
too.)<br>
;[netlogon]<br>
; comment = Network Logon Service<br>
; path = /home/samba/netlogon<br>
; guest ok = yes<br>
; read only = yes<br>
<br>
# Un-comment the following and create the profiles directory
to store<br>
# users profiles (see the "logon path" option above)<br>
# (you need to configure Samba to act as a domain controller
too.)<br>
# The path below should be writable by all users so that
their<br>
# profile directory may be created the first time they log
on<br>
;[profiles]<br>
; comment = Users profiles<br>
; path = /home/samba/profiles<br>
; guest ok = no<br>
; browseable = no<br>
; create mask = 0600<br>
; directory mask = 0700<br>
<br>
[printers]<br>
comment = All Printers<br>
browseable = no<br>
path = /var/spool/samba<br>
printable = yes<br>
; guest ok = no<br>
; read only = yes<br>
create mask = 0700<br>
<br>
# Windows clients look for this share name as a source of
downloadable<br>
# printer drivers<br>
[print$]<br>
comment = Printer Drivers<br>
path = /var/lib/samba/printers<br>
; browseable = yes<br>
; read only = yes<br>
; guest ok = no<br>
# Uncomment to allow remote administration of Windows print
drivers.<br>
# You may need to replace 'lpadmin' with the name of the
group your<br>
# admin users are members of.<br>
# Please note that you also need to set appropriate Unix
permissions<br>
# to the drivers directory for these users to have write
rights in it<br>
; write list = root, @lpadmin<br>
<br>
# A sample share for sharing your CD-ROM with others.<br>
;[cdrom]<br>
; comment = Samba server's CD-ROM<br>
; read only = yes<br>
; locking = no<br>
; path = /cdrom<br>
; guest ok = yes<br>
<br>
# The next two parameters show how to auto-mount a CD-ROM
when the<br>
# cdrom share is accesed. For this to work /etc/fstab
must contain<br>
# an entry like this:<br>
#<br>
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user
0 0<br>
#<br>
# The CD-ROM gets unmounted automatically after the
connection to the<br>
#<br>
# If you don't want to use auto-mounting/unmounting make
sure the CD<br>
# is mounted on /cdrom<br>
#<br>
; preexec = /bin/mount /cdrom<br>
; postexec = /bin/umount /cdrom<br>
<br>
[8CoreSHARED]<br>
path = /home/wayne/8CoreSHARED<br>
writeable = yes<br>
; browseable = yes<br>
guest ok = yes<br>
<br>
---------------------------------------------------<br>
PLUG-discuss mailing list - <a moz-do-not-send="true"
href="mailto:PLUG-discuss@lists.phxlinux.org"
target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a moz-do-not-send="true"
href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss"
target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr"><font color="#0b5394">James</font>
<div><br>
<span style="color:rgb(255,255,255)"><span
style="background-color:rgb(11,83,148)"><b><a
moz-do-not-send="true"
href="http://www.linkedin.com/pub/james-h-dugger/15/64b/74a/"
target="_blank"><span
style="background-color:rgb(255,255,255)"><span></span><span
style="color:rgb(11,83,148)">Linkedin<span></span></span></span></a></b></span></span><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">---------------------------------------------------
PLUG-discuss mailing list - <a class="moz-txt-link-abbreviated" href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a>
To subscribe, unsubscribe, or to change your mail settings:
<a class="moz-txt-link-freetext" href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a></pre>
</blockquote>
<br>
</body>
</html>