Samba sharing help :)

penguinstarship · 2007-03-03 18:37:13

I've got Samba set up as far as being able to get files off of my Windows machine, but I can't do it the other way around, get files off of Linux from my Windows machine, I've been reading around for a bit and am still stumped so I brought it to the Arch forum, I'm sure someone can help, I'm trying to share my music directory and be able to access it from Windows but I'm getting the error

\\tuxcomp\David's Music is not accessible. you might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The network path was not found

Here's my smb.conf

# 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 (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-H … ection.pdf
#
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# 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]
# 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
# 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/log.%m
# 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
restrict anonymous = no
domain master = no
preferred master = no
max protocol = NT
acl compatibility = winnt
ldap ssl = No
server signing = Auto
encrypt passwords = no
# 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
printable = yes

[David's Music]
case sensitive = no
strict locking = no
guest ok = yes
msdfs proxy = no
path = /home/tux/Music/
read only = no
guest account =

billy · 2007-03-03 18:58:10

is your hostname maybe localhost? at my home windows didn't want to connect to linux because of this....don't know why. maybe this name is reserved. well you can change the hostname of your computer in rc.conf but if you want to keep it you can add this line to /etc(samba/smb.conf :

netbios name = something_different_than_localhost

like i did.

bigbob73 · 2007-03-03 19:02:08

Sounds like a permission problem on the linux folder.

fk · 2007-03-03 20:48:34

Try without ' and space

Alternativ you can use FTP

penguinstarship · 2007-03-03 20:55:38

Awesome! Your guys suggestions were very appreciated, I tried all of them. Then what it came down to was me trying a random directory, Photos directory and sharing that through the KDE GUI and that went up fine, so I moved the contents of my Music directory and then removed it from my /etc/samba/smb.conf and then created a new one, added the contents, and then used the KDE GUI to extend it to the network, glad to get this one solved and I hope this helps someone else down the line thanks again

pelle.k · 2007-03-04 00:58:31

either way, "security = share" is good. i would have done this;

[Davids_Music]
comment = davids music
path = /home/tux/Music/
writable = yes
public = yes
force user = david
force group = users

this way, if you can access the music as david (or is it tux?), then samba users would have no problems as well.

Purch · 2007-03-04 15:26:32

I have arch box as a gateway and it takes care of samba on the LAN too (laptops, arch boxes and XP). Unix extensions = no, is good to have if you have symlinks in your samba share, which you access from windows machine or otherwise symlinks wont work. Following is my smb.conf. Comments are welcome as samba is one big pain in the ass to configure.

[global]
   workgroup = WG
   server string = Samba Server
   security = user
   hosts allow = 192.168. 127.
   printing = cups
   log file = /var/log/samba/log.%m
   max log size = 50
   socket options = TCP_NODELAY
interfaces = eth1
   local master = yes
   dns proxy = no

unix extensions = no  ## so that symlinks work when browsing linux samba share from windows
encrypt passwords = yes

[user1]
comment=user1's home
path = /home/user1
public = yes
force user = user1
read only = no
valid users = user1
follow symlinks = yes

[user2]
comment=user2's home
path = /home/user2
public = yes
force user = user2
writable = yes
valid users = user2
follow symlinks = yes

[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = yes
   public = yes
   guest ok = yes
   writable = no
   printable = yes

pelle.k · 2007-03-05 18:10:47

I can assure you, "Unix extensions = no" is _not_ needed for a windows client anymore. I have spent over one week trying to figure out why i _could_ resolve symlinks from windows xp, but not from a linux machine where i mounted the share with cifs. Unix extensions was most certainly on, because when i turned them off, i could resolve symlinks from both machines/OS:es. Really odd though....

Purch · 2007-03-05 20:35:10

hmm, maybe it that way around in my case too, but anyway with that setup symlinks work in XP and arch clients.

OssiR · 2007-06-09 22:39:16

billy wrote:

is your hostname maybe localhost? at my home windows didn't want to connect to linux because of this....don't know why. maybe this name is reserved. well you can change the hostname of your computer in rc.conf but if you want to keep it you can add this line to /etc(samba/smb.conf :
netbios name = something_different_than_localhost
like i did.

That worked on my Arch. Pretty strange cause i had it up running like 2 months and after i had to do reboot on my machine it suddenly stopped working. But anyways, changing the netbios name worked on my situtation.

Arch Linux

#1 2007-03-03 18:37:13

Samba sharing help :)

#2 2007-03-03 18:58:10

Re: Samba sharing help :)

#3 2007-03-03 19:02:08

Re: Samba sharing help :)

#4 2007-03-03 20:48:34

Re: Samba sharing help :)

#5 2007-03-03 20:55:38

Re: Samba sharing help :)

#6 2007-03-04 00:58:31

Re: Samba sharing help :)

#7 2007-03-04 15:26:32

Re: Samba sharing help :)

#8 2007-03-05 18:10:47

Re: Samba sharing help :)

#9 2007-03-05 20:35:10

Re: Samba sharing help :)

#10 2007-06-09 22:39:16

Re: Samba sharing help :)

Board footer