Welcome! Log In


Voir aussi à bien configurer "Active Directory Sites and Services" !!!! Dans le cas de serveurs multi-sites.

cf: http://technet.microsoft.com/en-us/library/cc782417(WS.10).aspx

How DFS Works
Updated: March 28, 2003

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

In this section

DFS Terminology

DFS Client and Server Compatibility

Characteristics of Namespace Types

DFS Architecture

DFS Physical Structures and Caches

DFS Processes and Interactions

DFS Protocols

DFS Interfaces

Network Ports Used by DFS

Related Information

Distributed File System (DFS) allows administrators to group shared folders located on different servers by transparently connecting them to one or more DFS namespaces. A DFS namespace is a virtual view of shared folders in an organization. Using the DFS tools, an administrator selects which shared folders to present in the namespace, designs the hierarchy in which those folders appear, and determines the names that the shared folders show in the namespace. When a user views the namespace, the folders appear to reside on a single, high-capacity hard disk. Users can navigate the namespace without needing to know the server names or shared folders hosting the data. DFS also provides many other benefits, including fault tolerance and load-sharing capabilities, making it ideal for all types of organizations. For more information about the scenarios in which DFS is commonly used, see “What Is DFS?”.

These sections provide an in-depth view of how DFS works in an optimal environment. An optimal environment for DFS is defined as follows:

Domain Name System (DNS) and Active Directory replication are working properly.

Sites and site costs in Active Directory are configured properly.

The domain controller acting as the primary domain controller (PDC) emulator is working properly.

The Distributed File System (DFS) service is running on all domain controllers and root servers.

Client computers are running one of the following operating systems: Windows NT 4.0 with Service Pack 6a, Windows 2000 with Service Pack 4 or later, Windows XP with Service Pack 1 or later, or Windows Server 2003.

Client computers are properly joined to the domain.

No firewalls block remote procedure call (RPC) ports used by DFS and the DFS root server that hosts DFS. These ports are described in “Network Ports Used by DFS” later in this section.

The Bridge all site links option in Active Directory must be enabled. (This option is available in the Active Directory Sites and Services snap-in.) Turning off Bridge all site links can affect the ability of DFS to refer client computers to target computers that have the least expensive connection cost. An Intersite Topology Generator that is running Windows Server 2003 relies on the Bridge all site links option being enabled to generate the intersite cost matrix that DFS requires for its site-costing functionality. If you turn off this option, you must create site links between the Active Directory sites for which you want DFS to calculate accurate site costs. Any sites that are not connected by site links will have the maximum possible cost. For more information about site link bridging, see “Active Directory Replication Topology Technical Reference.”

Windows 2000 domain controllers and Windows 2000 DFS root servers do not have the restrictanonymous registry entry set to 2. (This registry entry is located at HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa.) For more information about this registry entry, see “DFS Client and Server Compatibility” and “How Site Discovery Works” later in this section.
Sorry, only registered users may post in this forum.

Click here to login