search for: share1

...e live server, there are several partitions with shares split across the several partitions. The setup is the same, in terms of having the above entered into the individual shares and the RecycleBin for each share is located on the same partition/mount point that the share is located. Example: [share1] wide links = no writeable = yes path = /mnt/disk2/share1 write list = @share1 force group = share1 comment = Job Files and Related valid users = @share1 create mode = 770 user = @share1 directory mode = 770 vfs...

We restored to 3.0.23d after update to 3.0.25a because of strange dfs behavior. the detailed situation: on msdfs root server 'samba' ls -lR dfsroot/: drwxr-xr-x appl1 dfsroot/appl1 lrwxrwxrwx share1 -> msdfs:server1\share1 [dfs] comment = "SaMBa DFS root" path = /path.../dfsroot # next line does not work prior 3.0.25 !!! # hide unreadable = Yes msdfs root = Yes on 'server1' ls -lR share1: drwxrws--- folder1 drwxrws--- folder2 [shar...

..."msdfs proxy" parameter, and was hoping to get some advice from the community on this. My issue is that various SMB clients seem to behave differently when this parameter is pointed as a path that includes a sub-folder under the root share. So, given the following share configuration: [share1] comment = My DFS Proxy Share msdfs root = yes msdfs proxy = \fileserver1.example.com\shares\share1 I see the following behavior: * Windows: Windows clients accessing this \\dfsserver\share1 path see the intended destination - the contents of the \\fileserver1.example.com\shares\share1...

Hello all, Got samba with AD integration and extended ACL up and running. Here is what I am trying to do. share1 in smb.conf: [share1] comment = share1 path = /mnt/data/share1 public = no writable = yes printable = no valid users = @DOMAIN+group1 user1 and user2 are members of group1 user3 is not user1 creates \\server\share1\dir1\user3 user1 gr...

...over a decade and, from what I remember, I don?t think this is possible. Whenever I search for "two mount points" or "multiple mount points," I get hits for "multiple users," but not for mount points. I have the following directories I want to share through Samba: /share1/DVR /share1/Audio /share2/Video /share2/Backups /share1 is on /dev/sdb /share2 is on /dev/sdc Due to the amount of data on each one and the size of the devices, I can?t put all the shares on one device. I want to have one mount point, media, and it would have: /medium/DVR /medium/Audio /medium...

Hello Jeremy, I think you missed a "/" in: mount --bind /share1/DVR /medium/DVR mount --bind /share1/Audio /medium/Audio mount --bind /share2/Video /medium/Video mount --bind /share2/Backups /medium/Backups BR, Matt On Thu, Feb 13, 2020 at 5:15 PM Jeremy Allison via samba < samba at lists.samba.org> wrote: > On Thu, Feb 13, 2020 at 04:45:16PM -0500...

...25a after client reboot and remapping > > We restored to 3.0.23d after update to 3.0.25a because of strange dfs behavior. > > the detailed situation: > > on msdfs root server 'samba' ls -lR > > dfsroot/: > drwxr-xr-x appl1 > > dfsroot/appl1 > lrwxrwxrwx share1 -> msdfs:server1\share1 > > [dfs] > comment = "SaMBa DFS root" > path = /path.../dfsroot > # next line does not work prior 3.0.25 !!! > # hide unreadable = Yes > msdfs root = Yes > > on 'server1' ls -lR > > sh...

...with the same numbers. Testparm says the Samba is the domain PDC. My PC successfully boots into the domain with me (or root, as the case may be) as the logged in user. So, how can I tell whether I've correctly joined the domain? The second part of this is that with each of two shares (<share1> and <share2>), set up as below (I've only used bandwidth on one share; their set up is identical), I get BAD_NETWORK_NAME from an smbclient //<server>/<share1> -U <user> call. With valid user set to @group in <share1> only, this changes to a bad login erro...

...ameter, and was hoping >to get some advice from the community on this. My issue is that >various SMB clients seem to behave differently when this parameter is >pointed as a path that includes a sub-folder under the root share. > >So, given the following share configuration: > >[share1] > comment = My DFS Proxy Share > msdfs root = yes > msdfs proxy = \fileserver1.example.com\shares\share1 > >I see the following behavior: >* Windows: Windows clients accessing this \\dfsserver\share1 path see >the intended destination - the contents of the >\\files...

...1 (from 4.10) I noticed that python scripts using tempfile.mkstemp fail when run against samba cifs mounts. Before I submit a bug report, could someone else try this out so it's not just my setup? How to reproduce: 1. Mount a Samba 4.11 share using the mount command: mount //server1/share /tmp/share1 2. Run python script that is using mkstemp: import shutil import tempfile tmp_dest_fd, tmp_dest_name = tempfile.mkstemp(prefix=b'.file_tmp', dir='/tmp/share1', suffix='test.pdf') shutil.move('testfile', tmp_dest_name) Result: Traceback (most recent...

I encountered strange behaviour of "msdfs" when using together with "netbios aliases". E.g I have in smb.conf: [global] netbios name = server netbios aliases = server-oldname .... host msdfs = Yes [share1] path = /var/samba/share1 [share2] msdfs root = Yes msdfs proxy = \penguin\share2 .... From a windows (XP) machine I can now see: \\server\share1 and \\server\share2 where share2 is succesfully redirected as a DFS to \\penguin\share2. But when trying to connect via the aliased name to \\se...

Hi list! I've read some remarks here and in other places that it would be good practice to not edit the smb.conf file directly but rather keep a smb.conf.master file, edit that and then do a testparm -s > smb.conf. Here comes my problem: My smb.conf file uses some include statements. When using testparm those include lines are still in the output directly followed by the content of the

...yes security = user encrypt passwords = true passdb backend = tdbsam obey pam restrictions = yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n pam password change = yes map to guest = bad user [share1] comment = share1 writeable = yes path = /srv/files/share1 create mask = 770 directory mask = 770 valid users = +share1 browseable = yes guest ok = no Any ideas for solving the problem? Thanks and with kind regards, markus PS: Same Problem on samba 3.0.14/ dabian sarge with a different config.

A sysadmin moved a share from one Windows server to another. I am now getting error 13 when trying to mount the share from the new server. The following worked before the server was replaced: mount.cifs //ipaddress1/share1$ /mnt/share1 -o credientials/home/whatever/.smbcredentials,rw mount.cifs //ipaddress2/share2$ /mnt/share2 -o credientials/home/whatever/.smbcredentials,ro Change: server ipaddress2 was replaced with server ipaddress3 and share2$ was created on that server. mount.cifs //ipaddress1/share1$ /mnt/sha...

...ug timestamp = No socket options = TCP_NODELAY IPTOS_LOWDELAY disable spoolss = Yes os level = 8 idmap uid = 10000-30000 idmap gid = 10000-30000 template homedir = /mnt/NAS/home/%D/%U template shell = /bin/bash winbind cache time = 15 [share1] comment = <new share description> path = /mnt/NAS/share1/share1 valid users = admin, @users read only = No security mask = 0760 force security mode = 0760 directory security mask = 0770 force directory security mode = 0770...

Hi, On the Debian Linux server, followings had been istalled since May, 2006. Group1 users on Windows 2003 AD are able to access the share e.g. share1. I added a new share, share2 for group2 users, but none of user from group2 can access the new share. They always prompted for password. group1 and group2 are on same AD. ii samba 3.0.20b a LanManager-like file and printer server fo ii samba-common 3.0.20b Samba common files used...

...stored to 3.0.23d after update to 3.0.25a because of strange dfs > behavior. > > > > the detailed situation: > > > > on msdfs root server 'samba' ls -lR > > > > dfsroot/: > > drwxr-xr-x appl1 > > > > dfsroot/appl1 > > lrwxrwxrwx share1 -> msdfs:server1\share1 > > > > [dfs] > > comment = "SaMBa DFS root" > > path = /path.../dfsroot > > # next line does not work prior 3.0.25 !!! > > # hide unreadable = Yes > > msdfs root = Yes > > >...

Hi, Can anyone tell me if the following is possible I need 2 Samba Shares for example share1 and share2, both sharing an identical location, however I want once PC to connect using share1 and everyone else to use share2 so far so good this works. However, at 1am in the morning I want to stop share2 and disconnect users whilst not effecting access via share1. Then at 2am restart share2.

...e SA defined a shared resource. The share-permissions tab the "domain users" group has typical permissions, and in the security permissions tab the "domain users" has "read & exec", "show" and "read". In the server the structure is \\w2k3server\share1\dir1\dir2\target the "share" resource maps to c:\share, with the permissions described above. Both folders dir1 and dir2 haven't any permissions to the user I'm using to connect (test-user) "Target" folder has permissions to allow test-user to read, list, write, modify...

Recently a production "stable" samba server started producing this: samba-log.cpr8r: oplock_break failed for file Share1/Files/Financial/Comms.xls (dev = b, inode = 151073815, file_id = 31). samba-log.cpr8r: oplock_break failed for file Share1/Files/Financial/Futures.xls (dev = b, inode = 411546895, file_id = 31). samba-log.cpr8r: oplock_break failed for file Share1/Files/Financial/Historical.xls (dev = b, inode =...