Hi Matthieu: I'll research your follow up questions and will get back to you as soon as I have something concrete.
Regards, Obaid Farooqi Sr. Support Escalation Engineer | Microsoft -----Original Message----- From: Matthieu Patou [mailto:[email protected]] Sent: Thursday, May 13, 2010 3:00 AM To: Obaid Farooqi Cc: MSSolve Case Email; [email protected]; [email protected] Subject: Re: [REG:210050354365053002] more ms-dfsc.pdf questions On 12/05/2010 01:32, Obaid Farooqi wrote: > Hi Matthieu: > We have finished our investigation on your question regarding the effect of > site on the DC referral response. A future version of MS-DFSC will > incorporate the additions/modification as follows: > > Additions to Section " 3.3.1 Abstract Data Model" > ------------------------------------------------------------- > 3.3.1.1 Algorithm for sorting target sites in referral response based on site > location > DFS server places target servers in the referral response in the > following order: > - Targets in the same site as the client are listed at the top of the > referral response in random order. > - Targets outside of the client's site are appended to the response in > random order. > > 3.3.1.2 Algorithm for sorting target sites in referral response based on site > referral cost > The server MUST place the targets in the referral response in the > following order: > 1. Targets in the same site as the client are listed in random order at > the top of the > referral. > 2. Targets outside of the client's site are listed in order of lowest > site cost to highest site > cost. Referrals with the same cost are grouped together and within > each group the > targets are listed in random order. > > Additions to Section "3.3.5.3 Receiving a DC Referral Request" > ----------------------------------------------------------------------------- > The server MUST place target servers in the DC referral response > according to the site location > as specified in section 3.3.1.1 > > When least expensive target selection is enabled<WBN>, the server MUST > place the targets in > the referral response as specified in section 3.3.1.2 > > <WBN> On Windows, least expensive target selection is enabled by > setting SiteCostedReferrals > value in the registry key > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dfs\Parameters\ to > 1. > > > Additions to Section "3.3.5.4 Receiving a sysvol Referral Request" > --------------------------------------------------------------------------------- > The server MUST place target servers in the DC referral response > according to the site location > as specified in section 3.3.1.1 > > When least expensive target selection is enabled<WBN>, the server MUST > place the targets in > the referral response as specified in section 3.3.1.2 > > <WBN> On Windows, least expensive target selection is enabled by > setting SiteCostedReferrals > value in the registry key > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dfs\Parameters\ to > 1. > > > Modification to Section " 3.2.5.5 Receiving a Root Referral Request or Link > Referral Request" > ---------------------------------------------------------------------- > ------------------------------------------ > The following bullet: > " If DFS referral site costing is enabled, sort the targets into target > sets of increasing site cost from the target to the client." > > will be modified as: > " If DFS referral site costing is enabled, sort the targets into target > sets as specified in section 3.3.1.2." > > Ok it looks better, can I see the resulting pdf ? What about > I'll answer your questions in Q&A format for clarity. > > Q. Also where those parameters (same-site target, least-expensive, ...) are > stored (in the DS or somewhere else). > > A. The information about sites and cost is stored in Active Directory. For > information related to sites (and cost), please refer to section " 7.1.1.2.2 > Sites Container" of MS-ADTS. > Well here my question was more about the parameters, for instance the least-expensive parameter is called SiteCostedReferrals and is stored in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dfs\Parameters\. At least there is the same-site parameter that influence the way DFS referral are answered, where this parameter is stored ? Is there any other parameter that influence DFS ? > Q. The next paragraph sates: "From the IP address of the client, determine > the site of the client" what should happen is the client is not in a site > (for instance if it has a static ip and the admin forgot to declare this > subnet in one site)? > > A. Please see section 3.3.1.1, above. > > Ok so we consider that a client not within a site has all the DCs out of his site right ? > > Please let me know if this answers your question. If it does, I'll consider > this issue resolved. > > Regards, > Obaid Farooqi > Sr. Support Escalation Engineer | Microsoft > > >> ________________________________________ >> From: Matthieu Patou [[email protected]] >> Sent: Sunday, May 02, 2010 5:16 AM >> To: Interoperability Documentation Help; [email protected]; >> [email protected] >> Subject: more ms-dfsc.pdf questions >> >> Dear dochelp, >> >> The paragraph "2.2.1.3 Domain Name" >> define domain name as >> " Unless specified otherwise, a domain name MUST be a null-terminated >> Unicode character string >> consisting of the name of a domain. This can be either a NetBIOS name >> or a fully qualified domain >> name (FQDN), as specified in [MS-ADTS]." >> >> So when we have in "3.3.5.3 Receiving a DC Referral Request" >> >> " The domain name in the referral request MUST be either a domain in the >> current forest or a domain >> in a trusted forest. The server MUST fail DC referral requests for >> other domain names with a >> STATUS_INVALID_PARAMETER (0xC000000D) return code." >> >> We expect the client to request either FOOBAR (netbios domain) or >> foobar.demo.com (fqdn). >> >> But it turns out that windows XP at least is requesting \FOOBAR and >> \foobar.demo.com when w7 and w2k8 are requestion FOOBAR and >> foobar.demo.com >> >> Also in the same paragraph "The SpecialNameOffset field MUST be set to the >> offset in bytes from the beginning of the referral entry to the string that >> contains the domain name for the referral response." >> It let me think that this field should contain FOOBAR or foobar.demo.com but >> it turns out that it's \FOOBAR or \foobar.demo.com that is returned (the >> example in the mails out dfs questions from Bill Wesse was also showing >> this). >> >> The same remark apply the ExpandedName that also present a '\'. >> >> >> In this paragraph it stated that: >> "The ExpandedNameOffset field MUST be set to the offset in bytes from the >> beginning of the referral entry to the first null-terminated DC Unicode >> string. Each DC name immediately follows its null-terminated predecessor >> without any padding. An implementation MUST use the value in the >> NumberOfExpandedNames field to determine how many names are present in the >> list at ExpandedNameOffset. >> " >> but in this doc: >> "http://technet.microsoft.com/ru-ru/library/cc782417%28WS.10%29.aspx"; >> this point: >> >> "The client checks its domain cache for an existing domain controller >> referral for the Contoso.com domain. If this referral is in the cache, the >> client proceeds to step 5. If no domain controller referral is in the domain >> cache, the client connects to the IPC$ shared folder of the active domain >> controller in the context of the LocalSystem account and sends a domain >> controller referral request containing the appropriate domain name >> (Contoso.com). The domain controller returns the list of domain controllers >> in the Contoso.com domain. The domain controllers in the clients site are at >> the top of the list. If least-expensive target selection is enabled, domain >> controllers outside of the targets site are sorted by lowest cost. If >> same-site target selection is enabled, DFS ignores this setting and lists >> the remaining domain controllers in random order." >> >> Tells us that the same-site target or other parameters have an influence. >> >> Maybe the MS-DFSC needs to be updated ? Also where those parameters >> (same-site target, least-expensive, ...) are stored (in the DS or somewhere >> else). >> >> The next paragraph sates: "From the IP address of the client, determine the >> site of the client" what should happen is the client is not in a site (for >> instance if it has a static ip and the admin forgot to declare this subnet >> in one site) ? >> >> Regards. >> >> Matthieu. >> >> >> >> >> >> >> > Microsoft is committed to protecting your privacy. Please read the Microsoft > Privacy Statement for more information.The above is an email for a support > case from Microsoft Corp.REPLY ALL TO THIS MESSAGE or INCLUDE > [email protected] IN YOUR REPLY if you want your response added to the > case automatically. For technical assistance, please include the Support > Engineer on the TO: line. Thank you. > _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
