Any CIFS client can be a destination in an NT DFS setup because of the way it works. If a path is to be rerouted, the client gets a special error, then asks the server for the new path. The client then issues a separate connection to the destination share, which can be on any CIFS server anywhere, including the filer.
Mark Muhlestein
-----Original Message----- From: Brian Tao [mailto:taob@risc.org] Sent: Tuesday, August 24, 1999 8:08 AM To: toasters@mathworks.com Subject: Netapp CIFS as part of DFS tree?
I got this question from one of our NT guys... can a CIFS-enabled Netapp participate in an NT DFS tree? From what I understand, NT's DFS looks and acts like UNIX-style directory mounts (i.e., instead of assigning a drive letter to a shared drive, the drive appears under an existing directory).
On Tue, 24 Aug 1999, Muhlestein, Mark wrote:
Any CIFS client can be a destination in an NT DFS setup because of the way it works.
So to a user, it works pretty much like NFS then. The server doesn't really care about where its exported filesystems are mounted on the client side (whether it is drive I: or Z: or at a specific directory mount point).
-
Brian Tao -
Muhlestein, Mark