Fedora Linux Support Community & Resources Center
Old 21st October 2007, 04:49 PM
ariskk Offline
Registered User
Join Date: Sep 2007
Posts: 74
samba, can copy file but can't read or modify it!


I've created a /shared folder, did chown -R nobody:nobody /shared and modified my samba.conf:

guest account = nobody
comment = Shared folder
path = /shared
public = yes
only guest = yes
writable = yes
printable = no

From windows I can copy files to this folder. ll gives me the following output:

[root@laptop samba]# ll /shared/
-rwxr--r-- 1 nobody nobody 5138 Oct 21 16:46 data.csv

So I've copied the data.csv from my windows pc to this shared folder.

But I can't read or modify this file from windows. It might be that samba writes the file with limited permissons? How can I fix this problem?

Here is my full samba.conf file:


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

# server string is the equivalent of the NT Description field
server string = home 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 = user

# 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

# This option tells cups that the data has already been rasterized
cups options = raw

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

# 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
security = share
encrypt passwords = yes
guest ok = yes
guest account = nobody

# 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 ==============================
comment = Home Directories
browseable = no
writeable = 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
; 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
comment = All Printers
path = /usr/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writeable = no
printable = yes

# This one is useful for people to share files
; 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
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; 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.
; 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.
; 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.
; 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.
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no

# 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.
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765

comment = Shared folder
path = /shared
public = yes
only guest = yes
writable = yes
printable = no
Reply With Quote
Old 21st October 2007, 04:51 PM
ariskk Offline
Registered User
Join Date: Sep 2007
Posts: 74
btw, I've a 2 machine setup. I've a workgroup and from my windows pc I can see the linux pc been in the same workgroup.
Reply With Quote
Old 28th October 2007, 07:47 PM
ariskk Offline
Registered User
Join Date: Sep 2007
Posts: 74

can anyone help?
Reply With Quote
Old 29th October 2007, 01:28 AM
jhetrick62 Offline
Registered User
Join Date: Feb 2005
Location: Buffalo, Ny
Posts: 875
I'm no samba expert, although I have used it for over 3 years and migrated my server's and workstations so I guess I get it to work just fine for my purposes. My advice is simple. Don't attempt to set this up for exactly what you are discussing, but instead set it up for a simple solution first and get it to work. THEN, make your changes one at a time to see their effect on your setup.

I don't understand why you would change your permissions on the file to nobody:nobody. Just set file permissions appropriately,meaning if you want it to be world readable use the "r" permission flag in all three positions. If you don't want those folks wriiting to it, limit those permissions.

Unfortuantely, I have no experience in running security=share. I keep my server set to "user" security and anyone who uses it, signs in with a password. Unless you have a very large number of people accessing this share, user security works very well.

You can add an option to control permission in your share definition. I use this one on many of mine:

I also set os levels & wins server designations in my systems. Don't know how much is helps, but mine have always worked.

I hope that helps you. I was lost in the beginning, then I copied a working file from a knoppix live cd that I had used to boot a rouge machine. I then modified it to my liking and have used this with very few changes for the last 3 years from FC4 - FC7 on both workstations & my FC5 file server (still using that beast). I have multiple windows machines and two laptops that have all had no issue with rw to and from this server.

Registered Linux User #411071

If at first you don't suceed, read the man page again!
Reply With Quote
Old 2nd November 2007, 12:34 AM
ariskk Offline
Registered User
Join Date: Sep 2007
Posts: 74
Hi Jeff,

As I just found out, it was a selinux issue!!! I've disabled all security regarding samba and now it works ok.
Reply With Quote
Old 2nd November 2007, 12:48 AM
jhetrick62 Offline
Registered User
Join Date: Feb 2005
Location: Buffalo, Ny
Posts: 875
I'm glad to hear that.
Registered Linux User #411071

If at first you don't suceed, read the man page again!
Reply With Quote

copy, file, modify, read, samba

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Fedora 8 + Samba + CUPS-Add-Modify-Printer client-error-not-possible newhere Using Fedora 8 16th July 2011 12:17 PM
When I modify the session,which file has been changed? lch3920126 Using Fedora 0 26th September 2006 03:49 AM
How can I modify my yum properties file? mikezang Using Fedora 4 10th July 2006 09:11 AM
It is possible to modify a file automatically? stormvice Using Fedora 2 24th October 2005 06:16 PM

Current GMT-time: 06:26 (Wednesday, 23-08-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat