Hi Matt,
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. My apologies. ========================= What makes you think that the attribute was populated from a Windows 2008R2 server and not by Samba? ======================= Thanks! Sebas 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 -----Original Message----- From: Matthieu Patou [mailto:[email protected]] Sent: Friday, November 02, 2012 12:23 PM To: Sebastian Canevari Cc: Interoperability Documentation Help; [email protected]; [email protected] 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] 4.1.1.2.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. Matthieu -- Matthieu Patou Samba Team http://samba.org _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
