Good morning Tridge - we have created case SRX091002600036 "[MS-ADTS] 7.3.3.2 DS_FLAG option bits" to track work against your question concerning the DC_FLAG option bits.
I will begin work on this today, and will update you with my findings as soon as possible. Regards, Bill Wesse MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM 8055 Microsoft Way Charlotte, NC 28273 TEL: +1(980) 776-8200 CELL: +1(704) 661-5438 FAX: +1(704) 665-9606 -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Thursday, October 01, 2009 9:08 PM To: Interoperability Documentation Help Cc: [email protected] Subject: CAR: DS_FLAG Option bits Hi, We've been looking at the DS_FLAG option bits returned by a w2k8-r2 server in CLDAP (see MS-ADTS section 7.3.1.2). We've found that a w2k8-r2 domain controller for a single domain in a forest returns 0x33fd. Can you tell us why it doesn't add the DS_DNS_CONTROLLER_FLAG, DS_DNS_DOMAIN_FLAG and DS_DNS_FOREST_FLAG bits? The description of those bits would seem to match the windows DC, so we're wondering if perhaps we've misunderstood them. In 7.3.3.2 it says: - If the server has a DNS name, the DS_DNS_CONTROLLER_FLAG bit is set. - If the DnsDomain value specified in the search filter is the DNS name of the default NC, the DS_DNS_DOMAIN_FLAG bit is set. - If the DnsDomain value specified in the search filter is the forest name, the DS_DNS_FOREST_FLAG bit is set. My test w2k8-r2 DC definately has a DNS name, and the search filter was for the default NC, and it is the forest name, so I expected all 3 bits to be set. See http://samba.org/tridge/sniffs/w2k8b-join-w2k8-dc.cap frame 14. The two machines are both w2k8-r2. The DC is 10.0.0.4. Cheers, Tridge _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
