Displaying 20 results from an estimated 2000 matches similar to: "Can't set SeDiskOperatorPrivilege to Domain Admins. (NT_STATUS_NO_SUCH_USER) Error."
2017 Sep 19
0
Can't set SeDiskOperatorPrivilege to Domain Admins. (NT_STATUS_NO_SUCH_USER) Error.
Thanks for everyone chiming in on my problem. I really do appreciate it.
Just to clarify, I’m working on a share called Edwards_Public. I’m trying
to get it so the members of the AD group called do_superintendent are the
only people able to read and write any files in that directory.
Here is my global config:
workgroup = NSD
client signing = yes
client use spnego = yes
kerberos method = secrets
2017 Sep 19
3
Can't set SeDiskOperatorPrivilege to Domain Admins. (NT_STATUS_NO_SUCH_USER) Error.
>From your Global config I see no IDMAP settings. You need that for Linux to
recognize your ad users.
See my blog top post for example: Monklinux.blogspot.com
Try my configuration, should work perfectly. Soz 4 short reply, typing on
phone.
Lemme know if it works. Note, pay attention to section under installing
samba.
On Sep 19, 2017 22:19, "Jamie McParland via samba" <samba at
2017 Sep 19
3
Can't set SeDiskOperatorPrivilege to Domain Admins. (NT_STATUS_NO_SUCH_USER) Error.
Hai,
I've just read you howto, and its a very good start point.
You may have to correct a few small things there, but imo pretty good yes.
This :
> chown root."domain admins" /SHAREPATH
Is/should not needed.
setacl -m g:"domain admins":rwx,g:"domain users":rx /SHARELOCALPATH
^^^^^^ you did mean setfacl ?
But same, yes it works, and better then above, but
2017 Sep 18
1
Can't set SeDiskOperatorPrivilege to Domain Admins. (NT_STATUS_NO_SUCH_USER) Error.
We’ve just recently moved over to Samba 4. It looks as if “force directory
security mode” doesn’t work in samba 4. So I’m trying to setup the Windows
ACLs on our groups share.
I’ve been working on this for a few days. I’ve read over the docs, it seems
like all the google links are purple and I’m still stuck. Hopefully someone
here will have an idea.
We’re running Windows 2008R2 for our AD
2017 Sep 19
2
Can't set SeDiskOperatorPrivilege to Domain Admins. (NT_STATUS_NO_SUCH_USER) Error.
On Tue, 19 Sep 2017 13:13:45 -0700
Jamie McParland via samba <samba at lists.samba.org> wrote:
> Thanks for everyone chiming in on my problem. I really do appreciate
> it.
>
> Just to clarify, I’m working on a share called Edwards_Public. I’m
> trying to get it so the members of the AD group called
> do_superintendent are the only people able to read and write any
>
2017 Sep 19
0
Can't set SeDiskOperatorPrivilege to Domain Admins. (NT_STATUS_NO_SUCH_USER) Error.
Yes, I’m using sssd.
> On Sep 19, 2017, at 1:33 PM, Rowland Penny <rpenny at samba.org> wrote:
>
> On Tue, 19 Sep 2017 13:13:45 -0700
> Jamie McParland via samba <samba at lists.samba.org> wrote:
>
>> Thanks for everyone chiming in on my problem. I really do appreciate
>> it.
>>
>> Just to clarify, I’m working on a share called Edwards_Public.
2014 Apr 03
1
Domain Admins and SeDiskOperatorPrivilege
I am having trouble giving the Domain Admin group the
'SeDiskOperatorPrivilege' privilege on a member server.
Running 'net rpc rights list accounts -UAdministrator'
Results in this:
Enter Administrator's password:
BUILTIN\Print Operators
No privileges assigned
BUILTIN\Account Operators
No privileges assigned
BUILTIN\Backup Operators
No privileges assigned
BUILTIN\Server
2024 Jan 12
1
error: cannot write zone : Permission denied
Hello,
NSD 4.8.0 running on FreeBSD 13.2-RELEASE-p9 and serving both plain
and DNSSEC signed zones.
I noticed Permission denied errors in the logs for all domains listed
in nsd.conf:
[2024-01-12 12:20:05.710] nsd[8655]: info: writing zone
domain-plain.org to file domain-plain.org
[2024-01-12 12:20:05.710] nsd[8655]: error: cannot write zone
domain-plain.org file domain-plain.org~: Permission
2013 Mar 11
1
nsd4 process weirdness?
Hi,
I was playing with the munin plugin in nsd4 beta4, and saw some strange
errors. Directly after starting nsd on linux, I'm seeing:
$ ps ax -o pid,ppid,user,args | grep nsd
1638 1 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf
1641 1638 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf
1647 1641 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf
$ sudo munin-run nsd_munin_memory
2023 Jul 27
1
High memory consumption for small AXFR
Hello!
I use NSD 4.7.0 self compiled:
Configure line: --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking
2019 Dec 28
2
tinydns to nsd
On Sat, 28 Dec 2019 17:02:09 +0100
richard lucassen via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote:
> The problem is (was) that I used "include:" statements in nsd.conf
> to load zone information. Apparently nsd does not reread the include
> files upon a SIGHUP. I scripted everything into 1 file and a HUP
> rereads the zone info now.
Wrong, I made a mistake it
2008 Jan 15
1
problem using nsd
Hello I have this problem since a week or so:
The nsd daemon crashes unexpectedly and the nsd log files shows this:
[1200299533] nsd[3736]: info: XSTATS 1200299533 1200298484 RR=0 RNXD=0
RFwdR=0 RDupR=0 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=0
SAns=40 SFwdQ=0 SDupQ=0 SErr=0 RQ=37 RIQ=0 RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=0
SFail=30 SFErr=0 SNaAns=0 SNXD=0 RUQ=0 RURQ=0 RUXFR=0 RUUpd=1
2013 Nov 06
1
Frequent RRL false negatives when using multiple server processes on Linux
Hi,
Please advise how to use Response Rate Limiting on a server which has
multiple NSD server processes (nsd.conf server section has server-count
> 1).
We have a problem with NSD v3.2.16 repeatedly unblocking and blocking
again a single source which is flooding positive queries at a ~steady
700 qps rate. rrl-ratelimit setting is the default 200 qps. The
unblock-block happens multiple times
2013 Oct 18
1
nsd-4.0.0b5(and rc2) and changing zone from master to slave ?
Hi,
I'm doing some quick tests with nsd-4.0.0b5 and (rc2). And found
something strange when changing (nsd-control reconfig) one
zone from:
zone:
name: 10.in-addr.arpa
zonefile: /zones/empty.zone
to
zone:
name: 10.in-addr.arpa
request-xfr: 192.168.122.12 NOKEY
allow-notify: 192.168.122.12 NOKEY
zonefile: /zones/slave/10.rev
and doing nsd-control reconfig.
After
2024 Jan 11
1
support for ALIAS records
While SVCB/HTTPS provides a better solution for the browsing use case, I see other use cases where ALIAS/ANAME would be ideal, notably in apex RRs.
So while fostering SVCB/HTTPS deployment is a good thing, I wouldn?t mind name server software implementing ALIAS. Including NSD, but I reckon it?s much more challenging to do due to NSD architecture than it was to implement it in PowerDNS.
But if
2023 Jun 26
1
NSD reload and restart : in-memory data
Hi,
I'm new to NSD and would really appreciate if someone can point me to the
right direction.
I have like 8 NSD servers (secondary) serving around 30,000 zones.
Zone updates are transferred from the primary DNS servers by AXFR/IXFR.
The 8 NSD servers do not save the zones file on disk but are only held in
memory.
Therefore after NSD service is restarted zone transfer requests are being
2023 Dec 05
1
Question on slave
Hi Jean-Christophe,
Anand's answer is entirely correct.
Once 4.8.0 is released, zone files will be written once per hour by
default.
Best regards,
Jeroen
On Tue, 2023-12-05 at 10:48 +0100, Anand Buddhdev via nsd-users wrote:
> On 04/12/2023 13:47, Jean-Christophe Boggio via nsd-users wrote:
>
> Hi Jean-Christophe,
>
> > When syncing between master and slaves, am I
2023 Dec 05
1
Question on slave
On 04/12/2023 13:47, Jean-Christophe Boggio via nsd-users wrote:
Hi Jean-Christophe,
> When syncing between master and slaves, am I supposed to see new files
> appear in the slave's "zonesdir" directory? Because, as you might
> expect, I see nothing here. Is this behavior normal? From what I
> understand, the slave "caches" the data in /var/lib/nsd/nsd.db
2013 Feb 04
1
NSD 3.2.15 released (+RRL)
Dear NSD users,
Here is the release candidate for NSD 3.2.15. This comes with ILNP
support, NSD-RRL and different TSIG initialization (it fails if it can't
find no suitable algorithms, instead of can't find 'one of the'). Plus
some bugfixes.
The NSD-RRL implementation is based on the work by Vixie and Schryver.
However, because of the code-diversity argument that is at the basis
2023 Apr 24
1
nsd issue
Hi Jean Claude,
The message is printed when the bind operation failed. Why that happens
is hard to say, I'd need more information for that. As the message does
not say: address already in use (or similar), I'm guessing the address
is not configured?
Best regards,
Jeroen
On Fri, 2023-04-21 at 18:03 +0200, HAKIZIMANA Jean Claude via nsd-users
wrote:
> Dear nsd Users,
> kindly can