search for: fsrv

...t:group:g01:rwx #effective:--- default:mask::--- default:other::--- === In need folders have to be seen (and accessed) only by appropriate domain groups. For example, there are domain groups g01, g02, g03, etc, users in these groups have to see only "their" folders: u01 - \\fsrv\n\01, u02 - \\fsrv\n\02, u03 - \\fsrv\n\03 This is done by "Hide unreadable = yes" in smb.conf, by granting access (using "Security" tab in windows' folder rights) for concrete group to concrete directory and then chmod'ing this folder to 0770. But, if then I again mo...

...+0300 Dmitry via samba <samba at lists.samba.org> wrote: > In need folders have to be seen (and accessed) only by appropriate > domain groups. For example, there are domain groups g01, g02, g03, > etc, users in these groups have to see only "their" folders: u01 - > \\fsrv\n\01, u02 - \\fsrv\n\02, u03 - \\fsrv\n\03 > This is done by "Hide unreadable = yes" in smb.conf, by granting > access (using "Security" tab in windows' folder rights) for concrete > group to concrete directory and then chmod'ing this folder to 0770. > But, i...

...if anyone can help me? I recently created an active directory setup with a primary domain controller ad1 and secondary domain controller ad2 for a domain SAMDOM. In-line with what I understand to be Samba best practices I then setup a separate file-server fs1 on which I created a file share, /fsrv/shares/OgdenFiles/. This has all been done using Samba version 4.5.16-Debian, on Raspbian. The domain and fileshare do appear to work, and I have confirmed that I can logon as SAMDOM/Administrator and apparently read and write to the share without issue in Windows 10 without issue. Creation of...

Hi everyone, just tried executing wbinfo -u and wbinfo -g on a particular Samba domain member that is acting as a file server in my setup. Much to my surprise i did not see the list of users or groups that I would normally expect to see outputted from these commands. Instead both commands just exited and returned no output. I have already tried restarting winbind, smbd, and nmbd on the domain

...emplate shell = /bin/bash    winbind use default domain = true    winbind offline logon = false    winbind nss info = rfc2307    winbind enum users = yes    winbind enum groups = yes   vfs objects = acl_xattr   map acl inherit = Yes   store dos attributes = Yes [OgdenFiles]        path = /fsrv/shares/OgdenFiles        read only = no [OgdenUsers]        path = /fsrv/shares/OgdenUsers        read only = no Cheers Stephen Ellwood

...> SAMDOM. Nope, you have two AD DC's, one called 'ad1' and one called 'ad2' Apart from the FSMO roles, all DC's are equal. > In-line with what I understand to be Samba best practices I > then setup a separate file-server fs1 on which I created a file > share, /fsrv/shares/OgdenFiles/. This has all been done using Samba > version 4.5.16-Debian, on Raspbian. Roll on 'Buster' ;-) 4.5.x is well EOL. > > The domain and fileshare do appear to work, and I have confirmed that > I can logon as SAMDOM/Administrator and apparently read and write t...

...security = ADS disable netbios = yes local master = no domain master = no host msdfs = no idmap config * : backend = tdb idmap config * : range = 1000000-1999999 idmap config D : backend = nss idmap config D : range = 1000-999999 idmap negative cache time = 0 netbios name = FSRV server signing = auto create mask = 0644 server string = hide dot files = yes hide files = /Maildir/$RECYCLE.BIN/desktop.ini load printers = no printing = bsd printcap name = /dev/null deadtime = 15 interfaces = 192.168.222.77/32 bind interfaces only = yes unix extensions...

...>> host msdfs = no >> >> idmap config * : backend = tdb >> idmap config * : range = 1000000-1999999 >> idmap config D : backend = nss >> idmap config D : range = 1000-999999 >> idmap negative cache time = 0 >> >> netbios name = FSRV >> server signing = auto >> create mask = 0644 >> server string = >> hide dot files = yes >> hide files = /Maildir/$RECYCLE.BIN/desktop.ini >> load printers = no >> printing = bsd >> printcap name = /dev/null >> deadtime = 15 &...

...t membership. So after reading through the manual I came across Chapter 12: Group Mapping: MS Windows and UNIX (http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/groupmapping.html) and after doing: net groupmap add ntgroup="it_unix" unixgroup=it_unix_posixgroup type=d [root at fsrv-test ~]# net groupmap list verbose it_unix SID : S-1-5-21-3545410113-2264454557-1592041950-11805 Unix gid : 5402 Unix group: it_unix_posixgroup Group type: Domain Group Comment : Domain Unix group I am a membe...

...examples. Without feedback, we do not know of any problem areas. Having got that out of the way, I have gone through your smb.conf and corrected it by removing default lines. I have also added some comments: [global] workgroup = WG security = ADS realm = WG.LOCAL #netbios name = FSRV # see [1] below log level = 0 vfs:1 #idmap config MDS:backend = ad # see [2] below idmap config * : backend = tdb idmap config *:range = 2000-9999 idmap config WG : backend = ad idmap config WG : range = 10000-999999 idmap config WG : schema_mode = rfc2307 # see [3] b...

...> domain master = no > > host msdfs = no > > idmap config * : backend = tdb > idmap config * : range = 1000000-1999999 > idmap config D : backend = nss > idmap config D : range = 1000-999999 > idmap negative cache time = 0 > > netbios name = FSRV > server signing = auto > create mask = 0644 > server string = > hide dot files = yes > hide files = /Maildir/$RECYCLE.BIN/desktop.ini > load printers = no > printing = bsd > printcap name = /dev/null > deadtime = 15 > > interfaces = 19...

...idmap config * : backend = tdb > >>> idmap config * : range = 1000000-1999999 > >>> idmap config D : backend = nss > >>> idmap config D : range = 1000-999999 > >>> idmap negative cache time = 0 > >>> > >>> netbios name = FSRV > >>> server signing = auto > >>> create mask = 0644 > >>> server string = > >>> hide dot files = yes > >>> hide files = /Maildir/$RECYCLE.BIN/desktop.ini > >>> load printers = no > >>> printing = bsd > &g...

.../somepath/dir # file: dir # owner: usr2 # group: dg1 user::rwx group::rwx other::--- === lsattr /somepath/dir also gives none bits are set. Even if file object has 0777 rights - this doesn't help at all... smb.conf: === [global] workgroup = WG security = ADS realm = WG.LOCAL netbios name = FSRV server role = auto encrypt passwords = yes auth methods = winbind log level = 0 vfs:1 idmap config * : backend = rid idmap config * : range = 300000-400000 idmap config * : base_rid = 0 idmap config * :schema_mode = rfc2307 idmap_ldb:use rfc2307 = yes winbind nss info = rfc2307 winbind trusted d...

...ree86-bin 4.2.0-1 XFree86-etc 4.2.0-1 XFree86-f100 4.2.0-1 XFree86-fcyr 4.2.0-1 XFree86-fenc 4.2.0-2 XFree86-fnts 4.2.0-2 XFree86-fscl 4.2.0-1 XFree86-fsrv 4.2.0-1 XFree86-html 4.2.0-1 XFree86-lib 4.2.0-2 XFree86-man 4.2.0-1 XFree86-prog 4.2.0-1 XFree86-prt 4.2.0-1 XFree86-ps 4.2.0-1 XFree86-startup-sc...

Sorry for the delay and thanks for your pointers. "allow insecure wide links" does not change the behaviour, tried that before. Which is strange, if you look at the code. On the other hand it is clearly not a static misconfiguration, otherwise I would be able to reproduce it. About half of the time, we get a PANIC about 5 to 10 minutes after these strange widelinks_warnings appear in

...t;>>> idmap config * : range = 1000000-1999999 > >>>>> idmap config D : backend = nss > >>>>> idmap config D : range = 1000-999999 > >>>>> idmap negative cache time = 0 > >>>>> > >>>>> netbios name = FSRV > >>>>> server signing = auto > >>>>> create mask = 0644 > >>>>> server string = > >>>>> hide dot files = yes > >>>>> hide files = /Maildir/$RECYCLE.BIN/desktop.ini > >>>>> load printers = no...

Hello, we are running CentOS Stream 8 on some of our dedicated servers. On the newer servers that boot with efi, the system that is installed with the default properties in the ISO installer writes itself to the top of the efi boot order. This seems to happen every time after bootup. Since we run all our systems with efi network boot as the first boot option for rescue operation, this would

Hi, Thank you for your answer. That would only solve the problem at initial bootup but not for already installed systems. Inserting such a solution into a late running service would be no option due to it?s destroying the boards storage over time because of the many writes. On Debian/Ubuntu, there are a couple of grub2 debconf parameters. Unfortunately, there seems to be no such system like