Client that issue referral requests might or might not be joined to a . accessed by the DFS client can be or . DC or DFS Root Target Server To permit the in the referral response to be ordered on the basis of between the client and a DFS target site, a server joined to a is required to determine the site cost of a client from the client's IP address, as specified in section 3.5.4.3.8. If the server intends to support , it is required to have the ability to perform the site cost queries between the client and the DFS targets, as specified in as specified in section 4.1.16. The uses the of a to process referral requests. For , the server is required to access the DFS metadata stored in the object of the DFS namespace. Location and format of the DFS metadata is specified in section 2.3. Applicability Statement The DFS: Referral Protocol is applicable for scenarios in which files that are stored across one or more — possibly including one or more file servers—and the share administrator would like to provide one or more of the following capabilities. A unified namespace across multiple shares, such that from a client's perspective there is no need to know about individual share namespaces. A fault-tolerant namespace, such that failure of a share causes the client to fail over to an alternate share. A geographically optimized namespace, such that the client will automatically access the share that contains the geographically "lowest cost" copy of the files. A that is logically independent of the file server or the actual name of the share on the file server. Versioning and Capability Negotiation A client specifies the highest version supported in the MaxReferralLevel field of the message. A server responds with the highest DFS referral version supported by both the client and the server in the VersionNumber field of each referral entry, as specified in section . Vendor-Extensible Fields There are no vendor-extensible fields defined in the DFS: Referral Protocol. This protocol uses NTSTATUS values taken from the NTSTATUS number space, as specified in . Vendors SHOULD<1> reuse those values with their indicated meaning. Choosing any other value runs the risk of a collision in the future. Standards Assignments None.
Client that issue referral requests might or might not be joined to a . accessed by the DFS client can be or . DC or DFS Root Target Server To permit the in the referral response to be ordered on the basis of between the client and a DFS target site, a server joined to a is required to determine the site cost of a client from the client's IP address, as specified in section 3.5.4.3.8. If the server intends to support , it is required to have the ability to perform the site cost queries between the client and the DFS targets, as specified in as specified in section 4.1.16. The uses the of a to process referral requests. For , the server is required to access the DFS metadata stored in the object of the DFS namespace. Location and format of the DFS metadata is specified in section 2.3. Applicability Statement The DFS: Referral Protocol is applicable for scenarios in which files that are stored across one or more — possibly including one or more file servers—and the share administrator would like to provide one or more of the following capabilities. A unified namespace across multiple shares, such that from a client's perspective there is no need to know about individual share namespaces. A fault-tolerant namespace, such that failure of a share causes the client to fail over to an alternate share. A geographically optimized namespace, such that the client will automatically access the share that contains the geographically "lowest cost" copy of the files. A that is logically independent of the file server or the actual name of the share on the file server. Versioning and Capability Negotiation A client specifies the highest version supported in the MaxReferralLevel field of the message. A server responds with the highest DFS referral version supported by both the client and the server in the VersionNumber field of each referral entry, as specified in section . Vendor-Extensible Fields There are no vendor-extensible fields defined in the DFS: Referral Protocol. This protocol uses NTSTATUS values taken from the NTSTATUS number space, as specified in . Vendors SHOULD<1> reuse those values with their indicated meaning. Choosing any other value runs the risk of a collision in the future. Standards Assignments None.