Andrew, Thank you for your request concerning the [MS-ADTS] specifications. I have created a case for this (see info below); one of my colleagues will be in touch with you soon.
SRX080911600206 - ProtoDoc 99999: PFIF: [MS-ADTS]: 3.1.1.3.1.3.3 Clarify Ambiguous Name Resolution Best regards, Edgar A. Olougouna Sr. SEE, DSC Protocol Team, Microsoft | Email: [EMAIL PROTECTED], Tel: +1.469.775.7189 x 57189 -----Original Message----- From: Andrew Bartlett [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 2:02 AM To: Interoperability Documentation Help Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: ANR and anr==andrew In MS-ADTS 3.1.1.3.1.3.3 Ambiguous Name Resolution is described. In this, the syntax and behaviour for 'anr=andrew' is defined, and Samba4 implements this. However, we also have seen behaviour for 'anr==andrew'. However, I can't find this in the docs. A URL describing some of this behaviour (Specific Match) is: http://www.msexchange.org/articles/Ambiguous-Name-Resolution.html We thought we had this implemented, but when we fixed other bugs, our implementation would no longer pass our self-tests, and it has been abandoned pending clarification. Can you provide me some more details on this behaviour? Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
