1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Hosting a Microsoft Distributed File System tree on Samba</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
11 TITLE="SAMBA Project Documentation"
12 HREF="samba-howto-collection.html"><LINK
14 TITLE="Optional configuration"
15 HREF="optional.html"><LINK
17 TITLE="Configuring PAM for distributed but centrally
18 managed authentication"
21 TITLE="Printing Support"
22 HREF="printing.html"></HEAD
33 SUMMARY="Header navigation table"
42 >SAMBA Project Documentation</TH
77 NAME="MSDFS">Chapter 13. Hosting a Microsoft Distributed File System tree on Samba</H1
83 NAME="AEN1859">13.1. Instructions</H1
85 >The Distributed File System (or Dfs) provides a means of
86 separating the logical view of files and directories that users
87 see from the actual physical locations of these resources on the
88 network. It allows for higher availability, smoother storage expansion,
89 load balancing etc. For more information about Dfs, refer to <A
90 HREF="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp"
92 > Microsoft documentation</A
95 >This document explains how to host a Dfs tree on a Unix
96 machine (for Dfs-aware clients to browse) using Samba.</P
98 >To enable SMB-based DFS for Samba, configure it with the
104 > option. Once built, a
105 Samba server can be made a Dfs server by setting the global
107 HREF="smb.conf.5.html#HOSTMSDFS"
115 > parameter in the <TT
119 > file. You designate a share as a Dfs root using the share
121 HREF="smb.conf.5.html#MSDFSROOT"
129 > parameter. A Dfs root directory on
130 Samba hosts Dfs links in the form of symbolic links that point
131 to other servers. For example, a symbolic link
134 >junction->msdfs:storage1\share1</TT
136 the share directory acts as the Dfs junction. When Dfs-aware
137 clients attempt to access the junction link, they are redirected
138 to the storage location (in this case, \\storage1\share1).</P
140 >Dfs trees on Samba work with all Dfs-aware clients ranging
141 from Windows 95 to 2000.</P
143 >Here's an example of setting up a Dfs tree on a Samba
147 CLASS="PROGRAMLISTING"
148 ># The smb.conf file:
154 path = /export/dfsroot
159 >In the /export/dfsroot directory we set up our dfs links to
160 other servers on the network.</P
168 >cd /export/dfsroot</B
178 >chown root /export/dfsroot</B
188 >chmod 755 /export/dfsroot</B
198 >ln -s msdfs:storageA\\shareA linka</B
208 >ln -s msdfs:serverB\\share,serverC\\share linkb</B
212 >You should set up the permissions and ownership of
213 the directory acting as the Dfs root such that only designated
214 users can create, delete or modify the msdfs links. Also note
215 that symlink names should be all lowercase. This limitation exists
216 to have Samba avoid trying all the case combinations to get at
217 the link name. Finally set up the symbolic links to point to the
218 network shares you want, and start Samba.</P
220 >Users on Dfs-aware clients can now browse the Dfs tree
221 on the Samba server at \\samba\dfs. Accessing
222 links linka or linkb (which appear as directories to the client)
223 takes users directly to the appropriate shares on the network.</P
229 NAME="AEN1894">13.1.1. Notes</H2
235 >Windows clients need to be rebooted
236 if a previously mounted non-dfs share is made a dfs
237 root or vice versa. A better way is to introduce a
238 new share and make it the dfs root.</P
242 >Currently there's a restriction that msdfs
243 symlink names should all be lowercase.</P
247 >For security purposes, the directory
248 acting as the root of the Dfs tree should have ownership
249 and permissions set so that only designated users can
250 modify the symbolic links in the directory.</P
261 SUMMARY="Footer navigation table"
281 HREF="samba-howto-collection.html"
300 >Configuring PAM for distributed but centrally
301 managed authentication</TD
315 >Printing Support</TD
git.samba.org / kai / samba.git / blob