similar to: Unable to fetch value for secret BCKUPKEY_, are we an undetected RODC?

Garming - thanks for your quick response. That link you gave me has Samba 3.x patches. I didn't notice any links to 4.x patches. Official Distro Releases are often behind the current stable release, generally. In fact, when I first installed Samba4 the Linux version was more recent than the Ubuntu version. This lag is probably due to abundance of caution and/or lack of manpower. I

If it is that bug that you're referencing, besides obviously upgrading, you could try to patch it yourself. Whether or not you need to patch this, probably depends on whether or not your users are actually seeing issues. All that seems to happen is that it's entering a failure case when it hasn't actually failed. https://www.samba.org/samba/patches/ Cheers, Garming On 04/07/16

Since upgrading S4 DCs I am see the following message in log.samba - DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested: FFFFFFF8Unable to fetch value for secret BCKUPKEY_13bb48fc-0844-4736-9972-e26453333856, are we an undetected RODC? DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested:

On Mon, 19 Sep 2016 10:50:25 -0400 Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > On Mon, 2016-09-19 at 10:45 -0400, Adam Tauno Williams via samba > wrote: > > Since upgrading S4 DCs I am see the following message in log.samba - > > The message "Unable to fetch value for secret BCKUPKEY_13bb48fc-0844 > > -4736-9972-e26453333856, are we an

On Wed, 24 Oct 2018 09:45:39 +1300 Garming Sam <garming at catalyst.net.nz> wrote: > > On 23/10/18 9:48 PM, Rowland Penny via samba wrote: > > On Tue, 23 Oct 2018 10:07:29 +1300 > > Garming Sam via samba <samba at lists.samba.org> wrote: > > > >> Hi, > >> > >> On 20/10/18 1:26 AM, Julien Ropé via samba wrote: > >>>  The

On Tue, 23 Oct 2018 10:07:29 +1300 Garming Sam via samba <samba at lists.samba.org> wrote: > Hi, > > On 20/10/18 1:26 AM, Julien Ropé via samba wrote: > > > >  The deployment works, and computers seems to interact with the > > RODCs as they should, but sometimes computers leave the domain > > after a password change. > > > >  This seems to

Hi Garming, > As far I know, all this should work as you would expect. Quite recently, > Andrew Bartlett and I went about testing some of the behaviour of the > KDC and confirming behaviour such as RODC ticket forwarding. thanks for the input. It gives me hope to dig deeper! I have some more time to spend on this issue today, I gonna try some more scenario. > The one thing to check

Hi Garming, > > If you don't make much progress on your own, one thing you could do is > turn up the logging level and send in some logs and network traces > (and the steps you took). This is usually the easiest way to diagnose > any obvious issues and gives a much better sense of what is actually > happening. sorry to come back to you so late... It seems inded to be some

Hi everyone, I would like to have some input on ressources access from a workstation logged on a RODC server that has to connect on hub site servers. After login in the remote windows workstation, I have LOGONSERVER environment variable set to the local RODC server (workstation and user credentials have been preloaded). Everything works fine on local server. However if I want to connect to

Hi . I upgraded my samba4 servers from 4.1.17 to 4.2.1 . After upgrading , the samba4 servers becomed very slow and these error logs occured : [2015/04/27 08:09:08.279400, 1] ../source4/rpc_server/backupkey/dcesrv_backupke y.c:1423(bkrp_do_retrieve_server_wrap_key) Unable to fetch value for secret BCKUPKEY_34847c15-efd9-4430-ba82-bf7d3160e9e1 , are we an undetected RODC? [2015/04/27

On 03/28/2019 05:32 PM, Rowland Penny via samba wrote: [...] >> Should the samba RDOC act like the windows version or is it different >> by design? >> > > Yes it should and there is a bug report for something similar already, > see here: https://bugzilla.samba.org/show_bug.cgi?id=13377 > > I know that is for members of the denied group, but the substance is

 Hi,  I am working on a deployment of Samba as a domain controller, with one central domain controller and several read-only DC.  The deployment works, and computers seems to interact with the RODCs as they should, but sometimes computers leave the domain after a password change.  This seems to happen only on RODC where the passwords have been replicated - on one occasion the RODC was

Am 22.01.2018 um 21:39 schrieb Andrew Bartlett: > On Mon, 2018-01-22 at 21:30 +0100, Johannes Engel via samba wrote: >> [2018/01/22 21:15:50.022197, 2] >> ../source4/auth/ntlm/auth.c:475(auth_check_password_recv) >> auth_check_password_recv: sam_failtrusts authentication for user >> [MYDOMAIN\ldap] FAILED with error NT_STATUS_NO_TRUST_LSA_SECRET, >>

On 03/29/2019 10:37 AM, Andrew Bartlett wrote: > On Fri, 2019-03-29 at 10:16 +0100, Adam Minski via samba wrote: >> >> On 03/28/2019 05:32 PM, Rowland Penny via samba wrote: >> >> [...] >> >>>> Should the samba RDOC act like the windows version or is it different >>>> by design? >>>> >>> >>> Yes it should and

On 03/29/2019 10:54 AM, Andrew Bartlett wrote: > On Fri, 2019-03-29 at 10:44 +0100, Adam Minski wrote: >> >> On 03/29/2019 10:37 AM, Andrew Bartlett wrote: >>> On Fri, 2019-03-29 at 10:16 +0100, Adam Minski via samba wrote: >>>> On 03/28/2019 05:32 PM, Rowland Penny via samba wrote: >>>> >>>> [...] >>>>

Hi, I've stumbled upon this message: https://lists.samba.org/archive/samba-technical/2013-November/096322.html Which includes a patch to make user preloading in a RODC actually work. I'm running SerNet Samba packages, version 4.1.11, and this patch has not been applied. Is it blocked for some reason? Thanks in advance, -- Roberto Su?rez Soto Allenta Consulting

Hi, I've tried replacing some 2012R2 RODC by samba-4.9.4 RODCs. One question about password replication: Samba wiki (https://wiki.samba.org/index.php/Join_a_domain_as_a_RODC) states that samba RODC acts as a proxy server to a writable DC if users are not member of the Allowed RODC Password Replication Group, which is the behavior we knew (and what we want) from the MS RODCs. Our test

Hi, If you don't make much progress on your own, one thing you could do is turn up the logging level and send in some logs and network traces (and the steps you took). This is usually the easiest way to diagnose any obvious issues and gives a much better sense of what is actually happening. One other thing is that we generally recommend against .LOCAL domains although I would have no

On 23/10/18 9:48 PM, Rowland Penny via samba wrote: > On Tue, 23 Oct 2018 10:07:29 +1300 > Garming Sam via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> On 20/10/18 1:26 AM, Julien Ropé via samba wrote: >>>  The deployment works, and computers seems to interact with the >>> RODCs as they should, but sometimes computers leave the domain

Hi, On 20/10/18 1:26 AM, Julien Ropé via samba wrote: > >  The deployment works, and computers seems to interact with the RODCs > as they should, but sometimes computers leave the domain after a > password change. > >  This seems to happen only on RODC where the passwords have been > replicated - on one occasion the RODC was not set to store password > hashes, and