search for: testshare

...password server = 10.0.0.250 idmap uid = 10000-20000 idmap gid = 10000-20000 winbind separator = + winbind enum users = Yes winbind enum groups = Yes winbind use default domain = Yes How share is made? DST# cat /etc/samba/smb.conf | tail -n 4 [testshare] path = /srv/testshare browseable = yes writable = yes What permissions has test share? DST# ls -ld /srv/testshare/ drwxrwxrwt+ 2 root root 112 2010-12-28 07:18 /srv/testshare/ DST# getfacl /srv/testshare/ # file: srv/testshare/ # owner: root # group: root user::rwx group::rwx other::rwx...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have seen a weird problem in one of my clients. The reported that when issuing a smbmount command (both client and server are CentOS 4.4), it would take up to 30 second for the mount to complete. To make a long history short, by using strace and the source, I noticed smbmnt is first calling mount() using ascii options for *data. Then that would

...swords = yes case sensitive = yes [myshare] path = /raid/samba/share guest ok = yes read only = no /etc/fstab: /dev/md0 /raid ext4 auto,acl 0 1 2. Debian 6 Client mounts the Samba myshare with: cc at Client:/# mount.cifs //Server/share/ /mnt/testshare/ -o rw,guest,uid=cc,gid=cc 3. Create a symbolic link onto the share, from a file (example /tmp/tt) everything works fine: cc at Client:/# ln -s /tmp/tt /mnt/testshare/ttlink cc at Client:/# cat /mnt/testshare/ttlink I am on Client ! 4. Now, if you create a file with the SAM...

...ying to set up a share which can be read by everyone and written by Domain Admins only. I can see the share on my server as well as a file created in there on the linux command line, but I'm not able to enable write Permission for Domain Admins. I created a directory on the server /space/testshare and did a "chmod 777 /space/testshare" to be shure there's no problem on the linux file system. When I set "read only = no" on the share I can create a file there without any problem. But setting "read only = yes" and "write list = @"TEST\Domain A...

...UNKNOWN (10.33.224.61) # Date: 2013/01/21 10:00:00 [global] interfaces = 10.33.72.67/22, 127.0.0.1 bind interfaces only = Yes security = SHARE encrypt passwords = No log level = 3 os level = 8 local master = No domain master = No idmap config * : range = idmap config * : backend = tdb [testshare] path = /testshare valid users = +titan, benhu read only = No I'm in the group 'titan' also. Here's the log I get at log level = 3: [2013/01/21 10:03:05.928101, 3] param/loadparm.c:9572(lp_load_ex) lp_load_ex: refreshing parameters [2013/01/21 10:03:05.928257, 3] param/...

...doing parameter template shell = /sbin/nologin doing parameter kerberos method = system keytab doing parameter store dos attributes = yes doing parameter vfs objects = acl_xattr [2019/03/01 15:53:46.545450, 2] ../source3/param/loadparm.c:2799(lp_do_section) Processing section "[testshare]" doing parameter comment = testshare doing parameter path = /testshare doing parameter valid users = @pathology_its doing parameter writable = yes doing parameter read only = No [2019/03/01 15:53:46.545573, 4] ../source3/param/loadparm.c:3910(lp_load_ex) pm_process() retur...

Hi, I have a share (testshare) where different unix groups (testgroup1, testgroup2) should have access to. But I want that new files are only created with 660 permissions. Here are the ACL's of testshare: # file: testshare # owner: ralfgro # group: ve user::rwx group::rwx group:testgroup1:rwx group:testgroup2:rwx mask::rw...

I am having a problem getting Samba to use the linux group membership when following a symlink. On the Linux side, I have a soft link from the user's home directory to the shared directory. ln -s /home/shared/testgroup testshare In the smb.conf I have: [homes] comment = Home Directories browseable = no writable = yes valid users = %S force create mode = 0660 delete readonly = yes map archive = no case sensitive = yes follow symlinks = yes [testshared] comment = Test Shared browsable = n...

...hich is where the majority of users that will be useing the share are located). What information should I supply to allow the investigation of these issues [wmsprod1:root]/usr/local/samba/var> testparm Load smb config files from /opt/pware/samba/3.0.23c/lib/smb.conf Processing section "[testshare]" Processing section "[wisk]" Loaded services file OK. Server role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions ^H [global] display charset = UTF8 workgroup = CORP realm = CORP.YW.KELDA security = ADS password serv...

We have Fedora Core 2, samba-3.0.3-5, kernel 2.6.5 We set acl support in fstab We configured samba with acl support + openldap 2.1.29 as passwd backend. In a shared folder "testshare" we set the following directives: [testshare] comment = ...... path = /home/testshare read only = no nt acl support = yes create mask = 0700 directory mask = 0700 security mask = 0777 directory security mask = 0777 dos filemode = yes the output of 'ls -l /''? command is: drwxrwxr...

...e filesystem/ACL permissions allow access to the shared directory, so should Samba. If the filesystem does not allow access to the filesystem, Samba should deny as well. I thought I had this working correctly, but sometimes it randomly breaks. Here is an example of a share's configuration: [testshare] comment = Test Share path = /test/testshare writeable = yes create mask = 770 directory mask = 770 if the share's directory has the following permissions: drwxrwx--- 2 root DOMAIN\testgroup 4096 Dec 7 14:54 testshare Then, anyone in the "DOMAIN\testgroup" should h...

...n't allow connections. Here's the Samba config I'm using on both: Samba 3: [global] encrypt passwords = No log level = 3 os level = 8 local master = No domain master = No idmap config * : range = idmap config * : backend = tdb [testshare] path = /testshare read only = no Samba 4: [global] encrypt passwords = No log level = 3 client max protocol = SMB2 client min protocol = SMB2 os level = 8 local master = No domain master = No idmap config * : range =...

...and/or a user in the "admin users". Configuration: Samba 3.5.11 running on SLES11SP1. The share exported is on a GPFS filesystem and the GPFS vfs object is loaded(not loading it doesn't change the described behaviour) clients: Windows 7 and Windows 2008R2 all at latest update level. [testshare] comment = testshare path = /testfs1/testshare read only = no force create mode = 0666 force directory mode = 0777 force security mode = 0666 force directory security mode = 0777 admin users = testuser If I connect using a user other...

...MYDOM server string = Fileserver security = DOMAIN log level = 2 log file = /usr/local/samba/var/log.%m max log size = 500 name resolve order = host bcast unix extensions = No hide dot files = No csc policy = disable strict locking = No wide links = Yes [testshare] comment = test path = /testshare read only = No inherit permissions = Yes I joined the machine (osuse-test) to the network using this call. I tried a couple of other but this is the only one that produced a join: osuse-test:/usr/local/samba/var # ../bin/net rpc join -v -S PDCHOS...

...es Service principal 05/03/10 18:55:31 05/04/10 04:55:31 krbtgt/DACRIB.LOCAL at DACRIB.LOCAL renew until 05/09/10 22:56:03 05/03/10 23:07:07 05/04/10 04:55:31 cifs/dual-booter.dacrib.local at DACRIB.LOCAL renew until 05/09/10 22:56:03 turgon at workhorse:~$ smbclient //dual-booter/TestShare /mnt -k Domain=[DACRIB] OS=[Unix] Server=[Samba 3.4.0] smb: \> ls . D 0 Sat May 1 19:27:48 2010 .. D 0 Mon May 3 19:58:00 2010 TestFile 0 Sat May 1 19:27:48 2010 37555 blocks of s...

...crobat, the file gets DenyMode DENY_WRITE and the user who can edit the file can't save the document anymore. After the readonly user closes the file, the file can be saved again by the user who is allowed to edit it. 13007 23132 DENY_WRITE 0x120089 RDONLY NONE /data/testshare file1.pdf Fri Dec 19 11:30:16 2014 As far as I can see Word, Excel or any other document don't have this problem. [global] workgroup = DOMAIN realm = DOMAIN.EU server string = %h server security = ADS log file = /var/log/samba/log.%m max log size = 1000 server max protocol = SMB2...

Hello, After an upgrade to samba 3.5.8 (from 3.2.5) the option 'dos filemode' does not seem to work anymore. If I (as a user) do not own the file I can't change permissions. I am user 'felix' and member of supplementary group 'Development'. To test things I use the following share definition: [Temp] path = /srv/samba/file-shares/tmp browseable =

...l] workgroup = AD realm = AD.MYDOMAIN.COM security = ADS server role = member server netbios name = TEST-SERVER log level = 5 [netlogon] path = /usr/local/samba/var/locks/sysvol/somts-test.ucsd.edu/scripts read only = No [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No [testshare] comment = test share path = /space/testshare read only = no valid users = +AD\samba-testshare-group write list = +AD\samba-testshare-group create mask = 0664 force create mode = 0664 directory mask = 02775 force directory mode = 02775 force group = samba-testshare-group browseable = yes...

...solution of syncing the nss infos from AD down to the Unix passwd and group files by a perlscript and doing only authentication against the Active Directory. Now, I have other problems, however. Going through the tests outlined in the Trouble-Shooting Section of the Samba3-Howto, I can smbmount a testshare and display its content, but when trying to access the files, Samba panics: ---------------------------- 8< ---------------------------- smb: \> get SS2.FieldServiceManual.pdf Receiving SMB: Server stopped responding Call returned zero bytes (EOF) opening remote file \SS2.FieldServiceManual....

...t sure if I need to "join the domain" (The new one). However. Just changing workgroup + password server fails: old: When, from an account with the same name/passw as exists in the old win2k3 DC, I issue a net use like this it works fine: C:\Users\myuser>net use z: \\mysolarismachineIP\testshare The command completed successfully. new: it fails: C:\Users\myuser>net use z: \\mysolarismachineIP\testshare Configuration information could not be read from the domain controller, either b ecause the machine is unavailable, or access has been denied. The old smb.conf: workgroup = win.ol...