You are not logged in.

#1 2012-02-15 03:48:32

LuckyStrike
Member
Registered: 2012-02-15
Posts: 13

Sharing Files Between 3 Arch Computers Using SAMBA [SOLVED]

I am trying to network 3 of my computers together.  They are all running Arch 64.  I setup the smb.conf file according to various tutorials and then the folders show up on the other computers, but when you double click them (using Gnome 3) it gives an error "unable to mount location, failed to mount windows share"

I know this has to be some permission issue but I have spent hours on this and am hitting a brick wall.  Here is my smb.conf file.

#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = Samba Server

# Security mode. Defines in which mode Samba will operate. Possible 
# values are share, user, server, domain and ads. Most people will want 
# user level security. See the Samba-HOWTO-Collection for details.
   security = share
   guest account = nobody

[Z]
path = /media/Z
public = yes
guest ok = yes
writeable = yes
only guest = yes
browseable = yes

[Documents]
path = /home/myname/Documents
public = yes
guest ok = yes
writeable = yes
browseable = yes
only guest = yes




# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   load printers = yes

# you may wish to override the location of the printcap file
;   printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
;   printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
;   printing = cups

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest

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

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Use password server option only with security = server
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
;   password server = <NT-Server-Name>

# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
;   realm = MY_REALM

# Backend to store user information in. New installations should 
# use either tdbsam or ldapsam. smbpasswd is available for backwards 
# compatibility. tdbsam requires no further configuration.
;   passdb backend = tdbsam

# 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.
# Note: Consider carefully the location in the configuration file of
#       this line.  The included file is read at that point.
;   include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24 

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
;   local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
;   domain master = yes 

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;   preferred master = yes

# Enable this if you want Samba to be a domain logon server for 
# Windows95 workstations. 
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's 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

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one	WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
   dns proxy = no 

# These scripts are used on a domain controller or stand-alone 
# machine to add or delete corresponding unix accounts
;  add user script = /usr/sbin/useradd %u
;  add group script = /usr/sbin/groupadd %g
;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
;  delete user script = /usr/sbin/userdel %u
;  delete user from group script = /usr/sbin/deluser %u %g
;  delete group script = /usr/sbin/groupdel %g


#============================ Share Definitions ==============================
[homes]
   comment = Home Directories
   browseable = no
   writable = yes

[Z]
path = /media/Z
public = yes
guest ok = yes
writable = yes
only guest = yes
browseable = yes


# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /usr/local/samba/lib/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /usr/local/samba/profiles
;    browseable = no
;    guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to 
# specifically define each individual printer
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
# Set public = yes to allow user 'guest account' to print
   guest ok = no
   writable = no
   printable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = no
;   printable = no
;   write list = @staff

# Other examples. 
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

[Z]
path = /media/Z
public = yes
guest ok = yes
writable = yes
only guest = yes
browseable = yes

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

I know Z is in there twice, I tried adding it in a different spot after watching a tutorial, this doesn't have any bearing on my problem.

Last edited by LuckyStrike (2012-02-18 00:26:51)

Offline

#2 2012-02-15 23:41:26

allen875
Member
From: Winchester, VA
Registered: 2011-09-02
Posts: 46
Website

Re: Sharing Files Between 3 Arch Computers Using SAMBA [SOLVED]

Try setting it up this way...

#======================= Global Settings =======================
[global]
	log file = /var/log/samba/log.%m
	so_rcvbuf = 8192 SO_SNDBUF=8192
	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
	obey pam restrictions = yes
	socket options = TCP_NODELAY
	map to guest = bad user
	encrypt passwords = true
	passdb backend = tdbsam
	passwd program = /usr/bin/passwd %u
	dns proxy = no
	netbios name = ArchLinux
	server string = %h server (Samba, Arch)
	path = /home/username
	default = global
	unix password sync = yes
	os level = 20
	auto services = homes
	syslog = 0
	panic action = /usr/share/samba/panic-action %d
	usershare allow guests = yes
	max log size = 1000
	pam password change = yes

#======================= Share Definitions =======================
[Home]
	guest account = nobody
	comment = Home Folder
	writeable = yes

[Z]
	guest account = nobody
	comment = Z-Drive
	writeable = yes
	path = /media/Z

[Documents]
	guest account = nobody
	comment = Documents Folder
	writeable = yes
	path = /home/myname/Documents

Changing the username parts and other as necessary of course.

Offline

#3 2012-02-16 15:19:11

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,619

Re: Sharing Files Between 3 Arch Computers Using SAMBA [SOLVED]

If you're doing Linux-only sharing, why are you using samba rather than nfs?


But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#4 2012-02-16 17:56:04

zenlord
Member
From: Belgium
Registered: 2006-05-24
Posts: 1,209
Website

Re: Sharing Files Between 3 Arch Computers Using SAMBA [SOLVED]

alphaniner wrote:

If you're doing Linux-only sharing, why are you using samba rather than nfs?

+1

SAMBA/CIFS is only necessary if you want to share with Windows OS. Linux, BSD and also Mac OSX can use NFS, which is faster than SAMBA/CIFS...

Offline

#5 2012-02-16 19:36:35

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,619

Re: Sharing Files Between 3 Arch Computers Using SAMBA [SOLVED]

I can't speak to performance of samba vs nfs.  But regarding ease of setup... my /etc/exports file is two lines long for cryin out loud!


But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#6 2012-02-16 22:47:58

allen875
Member
From: Winchester, VA
Registered: 2011-09-02
Posts: 46
Website

Re: Sharing Files Between 3 Arch Computers Using SAMBA [SOLVED]

I agree with the NFS over Samba replies for Linux to Linux networking.

Offline

#7 2012-02-17 16:03:45

LuckyStrike
Member
Registered: 2012-02-15
Posts: 13

Re: Sharing Files Between 3 Arch Computers Using SAMBA [SOLVED]

allen875 wrote:

Try setting it up this way...

Changing the username parts and other as necessary of course.

Thank you very much it worked!

Offline

#8 2012-02-17 16:05:24

LuckyStrike
Member
Registered: 2012-02-15
Posts: 13

Re: Sharing Files Between 3 Arch Computers Using SAMBA [SOLVED]

alphaniner wrote:

If you're doing Linux-only sharing, why are you using samba rather than nfs?

I wouldn't mind doing NFS, but I had done samba in the past and was more familiar with the process.  I tried NFS briefly but never could get it working either, and I got farther with samba.

Offline

#9 2012-02-17 22:49:34

allen875
Member
From: Winchester, VA
Registered: 2011-09-02
Posts: 46
Website

Re: Sharing Files Between 3 Arch Computers Using SAMBA [SOLVED]

LuckyStrike wrote:
allen875 wrote:

Try setting it up this way...

Changing the username parts and other as necessary of course.

Thank you very much it worked!

Could you please edit the Title to say solved, Thanks.

Offline

Board footer

Powered by FluxBB