search for: smbshares

Hello, After researching the subject on the internet I concluded that Samba should take into account Unix file acls. During my tests I found the opposite. Only Unix file mode bits are respected, and file acls are ignored. If my initial assumption is correct and Samba do respect Unix file acls, then I am doing something wrong. Please see the setup below and point to what I am doing wrong.

Hello, I have a general administrative question concerning Samba shares. I have a large amount of data that about 25 users have limited access to. I only want these users to have access to a sub-set of this data, but I also only want the users to see that which they have access to. So, for example, suppose that the share looks like thus: /smbshare /smbshare/dir1 /smbshare/dir2

(I'm not subscribed to the list: please keep me in CC) I'm copying files between two samba server using robocopy from a third Windows PC and i'm experiencing disk usage that is much higher on the destination PC. The origin samba server is Debian Lenny with samba 3.2.5. The destination samba server is Debian Wheezy with samba 3.6.9 The PC running robocopy is Windows Server 2003 with

On Fri, Dec 19, 2014 at 12:47:51PM -0500, Rufe Glick wrote: > Hello, > > After researching the subject on the internet I concluded that Samba should take into account Unix file acls. During my tests I found the opposite. Only Unix file mode bits are respected, and file acls are ignored. If my initial assumption is correct and Samba do respect Unix file acls, then I am doing something

Hello Jeremy, Friday, December 19, 2014, 3:48:51 PM, you wrote: > On Fri, Dec 19, 2014 at 12:47:51PM -0500, Rufe Glick wrote: >> Hello, >> After researching the subject on the internet I concluded that Samba should take into account Unix file acls. During my tests I found the opposite. Only Unix file mode bits are respected, and file acls are ignored. If my initial assumption is

Hi, I have one NAS which I can access via NFS or Samba. This storage is accessed by 2 linux servers with Samba where I re-export the NAS share. This is sort of an active/active loadbalancing cluster. The only thing not working is locking... If a client opens a Word-File via server1 and another opens the same via server2 it won't inform the user that he can only open the file readonly. I was

I have a server 192.168.0.14 and the directory I wish to share is /home/photo I can mount from 192.168.0.1 with mount -t smbfs -o "username=photo" //192.168.0.14/photo /mnt/smbshare it prompts me for a password and I can see the contents of the share but I cannot write to it. Any pointers gladly recieved kind regards Kevin -- "Democracy is two wolves and a lamb voting on what to

...jobs = 100 lpq cache time = 100 ;disable spoolss = no max reported print jobs = 1000 ## PRINTERS -- This section gets applied to every printer found in cups (load printers = yes). [printers] comment = All Network Printers printable = yes path = /var/smbshares/spool guest ok = yes public = yes read only = yes create mode = 0777 browseable = no use client driver = no ## Win2K, WinXP Print Clients [print$] comment = Printer Driver Downloads path = /var/smbshares/prndrivers browseable...

...gt; veto files = /.bash_logout/.bash_profile/.bash_history/.bashrc/ > hide unreadable = yes > > # disable printing completely > load printers = no > printing = bsd > printcap name = /dev/null > disable spoolss = yes > > > [home] > path = /mnt/smbshares/home > read only = no > > [profiles$] > path = /mnt/smbshares/profiles > read only = no > admin users = +"HO\Domain Admins" > profile acls = yes > csc policy = disable > > [public] > path = /mnt/smbshares/public > read only = no...

Hi everybody - I'm trying to write a Perl wrapper for some rsync tasks that need doing. Problem is, there's some sort of odd interaction going on between Perl and the daemon mode communication for the rsync client, and I'm at my wit's end in trying to figure it out. Here's the Perl script: #####################################################

...winbind gid = 10000-15000 winbind separator = + winbind use default domain = yes security = ADS encrypt passwords = Yes password server = win2003.mydomain.com client use spnego = yes [test1] comment = test1 path = /smbshares/test1 public = Yes valid users = user1, user2, user3 writable = YES [test2] comment = test2 path = /smbshares/test2 public = Yes valid users = @group1 writable = YES [test3] comment = test3 path = /smbs...

Greetings, I think I may be having a slight configuration problem with Samba and FreeBSD-5.1. I'm trying to use FreeBSD's mount_smbfs(8) to mount a remote Samba share onto my local FreeBSD filesystem. With the configuration below, I can read all (almost; explained below) files and directories just fine. All permissions are correct. But whenever I try to write to the share, the write fails

Hello Jeremy, Friday, December 19, 2014, 7:00:06 PM, you wrote: > On Fri, Dec 19, 2014 at 06:31:33PM -0500, Rufe Glick wrote: >> Hello Jeremy, >> Friday, December 19, 2014, 4:55:21 PM, you wrote: >> > On Fri, Dec 19, 2014 at 03:58:58PM -0500, Rufe Glick wrote: >> >> Hello Jeremy, >> >> > Do alice and bob have the same user ids on client

We have ClearCase database on unix and users on windows. We are creating Unix users locally on that Clearcase server. Samba is also installed on that server. User windows machines are part of domain. Groups,usres are created on domain and same users,groups are created on unix server. Now problem is occuring when a windows user is changing the password for his domain login. as soon as user is

...store dos attributes = Yes vfs objects = dfs_samba4, acl_xattr [netlogon] path = /var/lib/samba/sysvol/avails.avails.com/scripts read only = No [sysvol] path = /var/lib/samba/sysvol read only = No [home] comment = Home Directories path = /smbshares/home admin users = Administrator read only = No [Profiles] comment = Roaming Profile Share path = /smbshares/profiles admin users = Administrator read only = No -- Bo Kersey VirCIO - managed network solutions 4314 Avenue C Austin, TX 78751 ph...

Hi list - I've been using Samba since 2.x in the early 2000's, and a papercut I had eight years ago still plagues me today - when anyone on a Windows client right-clicks a folder on a Samba share and tries to view or change its permissions, it doesn't work right. The folder appears to have no permissions enabled for owner, group, or world (regardless of what the permissions

Hello all, I have been struggling with a permission issue with Samba for over a week now. I've tried many different setup, without much success. I am using samba 3.6 on Arch Linux. The user I am testing with is a member of the group nobody. I have a share defined as it : security = share [public] path = /home/smbshare public = yes only guest = yes writable = yes printable =

Hi folks, I'm running samba 3.0.33 on Solaris 9 hosts. I have a host that has two hostnames (actual + alias). I would like to be able to connect to this host via either hostname and be able to access this samba data. Note: I would prefer not to run multiple samba instances... Has anyone else experienced this sort of issue, and have you been able to resolve it? - Avron

...ode = 770 browseable = no guest ok = no followsymlinks = yes [printers] admin users = @tech comment = All Printers path = /var/spool/samba browseable = Yes printable = Yes [netlogon] comment = NETLOGON Service path = /smbshares/netlogon/%G admin users = @tech read only = yes write list = @tech public = no browseable = no [tech] admin users = @tech valid users = @tech tshrum comment = Bryant root directory path = /smbshares followsymlinks = ye...

Hello everybody. I am having troubles to log on a samba domain from winxp and win 2000 workstations. I patched the registry with the requiresignorseal=0, changed the local and group policies (following various comments found on the web), and added the machine account for samba (obviously, /etc/passwd too). I tried with samba 3.0.7, 3.0.10 and 3.0.13, Winxp with and without sp2, and win200