Hi, John, Please disregard this request and close the issue.
As Tridge pointed out I had missed that MS-LSAD contains an older/subset of the full IDL in MS-LSAT. I have all the information I need in MS-LSAT. regards ronnie sahlberg On Thu, Oct 2, 2008 at 12:55 AM, John Dunning <[EMAIL PROTECTED]> wrote: > Hello Ronnie, > I wanted to let you know that I had received this request. Myself or one of > my teammates will look into this issue and get back to you as soon as > possible. > > Thanks > John Dunning > Senior Escalation Engineer Microsoft Corporation US-CSS DSC PROTOCOL TEAM > Email: [EMAIL PROTECTED] > Tele: (469)775-7008 > > -----Original Message----- > From: ronnie sahlberg [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 30, 2008 8:04 PM > To: Interoperability Documentation Help > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: MS-LSAD Missing procedures > > Hi, > > I am a pfif subcontractor. > > When looking at the IDL in the latest version of MS-LSAD this > describes procedures > 0 - LsarClose() > to > 74 - LsarSetForestTrustInformation() > > > However, both Wireshark and also Samba4 IDL files contain hints that > there should be more procedures on this interface : > > /* Function 0x4b */ > NTSTATUS lsa_CREDRRENAME(); > > /* Function 0x4c */ > NTSTATUS lsa_LookupSids3( > > /* Function 0x4d */ > NTSTATUS lsa_LookupNames4( > > /* Function 0x4e */ > NTSTATUS lsa_LSAROPENPOLICYSCE(); > > /* Function 0x4f */ > NTSTATUS lsa_LSARADTREGISTERSECURITYEVENTSOURCE(); > > /* Function 0x50 */ > NTSTATUS lsa_LSARADTUNREGISTERSECURITYEVENTSOURCE(); > > /* Function 0x51 */ > NTSTATUS lsa_LSARADTREPORTSECURITYEVENT(); > > > Please add these procedures to the IDL file. > > > regards > ronnie sahlberg > > _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
