The only odd thing I've seen is that if your dfs structure and isilon cluster are in different but trusted domains, like this:  cluster01 in the dev.domain.com domain dfs root is \\domain.com  Sample leaf is: \\domain.com\hr\employeehandbook --> \\cluster01-smb.dev.domain.com\employeehandbook$ where: cluster01-smb.dev.domain.com is the SmartConnect Zone Name  What can occur depending upon the direction of the trust and the domain functional level is that when connecting directly to the share on Isilon for a given user it works fine.  If they instead connect to the DFS leaf it'll prompt for credentials, and no matter what credentials are entered it won't work.  Where is the resolution?  I cannot honestly explain it, but the 1 time that I've seen this changing the SmartConnect zone name from the FQDN of 'cluster01-smb.dev.domain.com' to simply the short name of 'cluster01-smb' did the trick.  Note this had nothing to do with SPN changes on the machine account.  Again this was certainly a corner case, but just in case you encounter it, this might be your fix.  ~Chris Klosterman Senior Solution Architect EMC Isilon Offer & Enablement Team chris.klosterman[NAME].com twitter: [NAME]
is there any limations or precaustions when you use Isilon as DFS Leaf?  And i want to know any defferences at all to use Windows as a DFS leaf or isilon as a DFS leaf.
Isilon DFS Leaf