• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 709
  • Last Modified:

samba version 3.6.9-151.el6_4.1 Red Hat 6.2

moving our database (Universe)  to a new server running Red hat ES6 64 bit version and our old server was a Red hat 9 running samba version 2.2.7a. I need Samba so that it can write to a temp file to allow tiff images to be delivered to them via a tiff viewer. The older version of samba works great, but this new version I am unable to get the share to be able to write. I can view, just cannot write. any help would be greatly appreciated.

here is a copy of my samba config. this is from my older Samba v2 that I copied over to the Samba v3. I have tried uninstalling samba then reinstalling it, using the config that comes with samba. When I try to UNC into the share I can get it, just cannot create a file, or folder. says that I do not have permission. Everyone should have read and write to the temp file.

      log file = /var/log/samba/%m.log
      load printers = yes
      force directory mode = 0777
      encrypt passwords = yes
      winbind trusted domains only = yes
      public = yes
      winbind use default domain = yes
      dns proxy = No
      writeable = yes
      printing = cups
      server string = samba server
      force security mode = 0777
      force create mode = 0777
      os level = 20
      auto services = global
      update encrypted = Yes
      printcap name = cups
      create mode = 0777
      security = share
      max log size = 100
      directory mode = 0777

      guest account =
      create mask = 0777
      browsable = yes
      path = /uv/ccc

#from old server, this wont work with Samba ver 3
#      comment = upload files
#      path = /uv/ccc
#      read only = No
#       writable = yes

      comment = Home Directories
      valid users = %S
      read only = No
      create mask = 0777
      directory mask = 0777
      browseable = No

      comment = All Printers
      path = /var/spool/samba
      printable = Yes
      browseable = No
      available = No

      comment = CAW data files
      path = /uv/cawportal
      valid users = jsheldon
      read only = No

      comment = temp upload for imaging
      delete readonly = yes
      writable = yes
      path = /uv/cubs/temp

      path = /uv/ccc/cudocuments
      guest account = cubs
      force user = cubs
      force group = cubs
      read only = No
      delete readonly = Yes
  • 2
3 Solutions
Can you post the following ?

ls -lah /uv/cubs/temp

Open in new window

My name is MudSystems EngineerCommented:
19.7.2. Share-Level Security

With share-level security, the server accepts only a password without an explicit username from the client. The server expects a password for each share, independent of the username. There have been recent reports that Microsoft Windows clients have compatibility issues with share-level security servers. Samba developers strongly discourage use of share-level security.

In smb.conf, the security = share directive that sets share-level security is:
tjguyAuthor Commented:
this issue was the SELinux blocking all clients to the shared folders. once I disabled SELinux the Samba Shares started to work again as expected.
tjguyAuthor Commented:
after scanning the log I noticed that smb shares were being blocked by something called selinux.

chcon -R -t samba_share_t also seem to help this issue as well. Still disabled SELinux.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Build your data science skills into a career

Are you ready to take your data science career to the next step, or break into data science? With Springboard’s Data Science Career Track, you’ll master data science topics, have personalized career guidance, weekly calls with a data science expert, and a job guarantee.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now