HP CIFS Windows 2000 Interoperability (October 2002)

CIFS/9000 and Windows 2000 Interoperability

Hewlett-Packard

The DFS administration tool resides on the ADS server. If the DFS root is a standalone

server, then it must be administered on that server. If the DFS root is on ADS, then it can

be administered on any DC in the domain. The following details apply to Windows 2000

DFS:

• There can be 1 DFS root per domain controller

• 32 domain controllers can host the same DFS root in one domain (for

exceptional fault tolerance)

• There can be unlimited DFS roots in the domain (except that the limit is

one per domain controller, so the practical limit is the number of domain

controllers in the domain)

• Automatic replication requires NTFS 5.0

• A DFSLink (leaf node) can exist on any UNC path (Universal Naming

Convention: \\Servername\Sharename) in the domain.

7.6 Windows 2000 DFS: CIFS/9000 Interoperability

CIFS/9000 Server can participate in a Windows 2000 DFS as a DFSLink (leaf node) only. A

DFSLink is the target of a referral by the DFS root. The DFSLink role for a CIFS/9000

Server is consistent with the member server status of CIFS/9000 in a Windows 2000 domain.

Root node status - whether standalone or ADS integrated - requires domain controller

capability.

Domain root nodes that are configured in the ADS are fault tolerant if they are replicated to

other DCs in the domain. DFSLinks can be configured for automatic file replication, which

enables fault tolerance. A CIFS/9000 server cannot execute automatic file replication, but

can be configured for fault tolerance. Providing replication for a CIFS/9000 server DFSLink

requires some method of file replication from one DFSLink to another, either manually or

through a mechanism such as rsync (http://samba.anu.edu.au/rsync/).