[cifs-protocol] nTDSDSA Object and serverreference attribute
Sebastian.Canevari at microsoft.com
Mon Nov 12 08:59:40 MST 2012
Sorry, I thought I had sent you this before but it was saved in my drafts.
Today, I was wondering what may have happened to your response and found out I hadn't sent it after all.
What makes you think that the attribute was populated from a Windows 2008R2 server and not by Samba?
Sebastian Canevari | Escalation Engineer | US-CSS Developer Support Core (DSC) Protocol Team
P +1 469 775 7849
One Microsoft Way, 98052, Redmond, WA, USA http://support.microsoft.com
From: Matthieu Patou [mailto:mat at samba.org]
Sent: Friday, November 02, 2012 12:23 PM
To: Sebastian Canevari
Cc: Interoperability Documentation Help; cifs-protocol at samba.org; pfif at tridgell.net
Subject: Re: nTDSDSA Object and serverreference attribute
On 10/25/2012 09:25 AM, Sebastian Canevari wrote:
> Hi Matt,
> I have tested the population of the serverReference attribute in the NTDSSettings object and I've confirmed that it does not get populated by Windows.
> Anyways, I've consulted with the PG and they confirmed my findings and pointed me to [MS-DRSR] 126.96.36.199.3 " CreateNtdsDsa" where the pseudo code states:
> /* serverReference attribute is not updated here; instead, it is used
> * to find the computer object of the DC so that the replication SPN
> * can be added to the DC's computer object. */
> sl := ENTINF_GetValue(e, serverReference, prefixTable)
> ENTINF_SetValue(e, serverReference, null, prefixTable) ...
> In conclusion, the ServerReference attribute for nTDSDSA Object should not be updated at the NTDSSettings level but only at the server object level.
Ok but then how to explain that windows 2008R2 actually populate this attribute.
Thanks for the information.
More information about the cifs-protocol