Currently, CIFS service is only supported for the global zone so DFS support is only available in the global zone as well.
When AD support is added, DFS namespace will be created and managed on AD domain controller instead of the Solaris system running CIFS server. CIFS server as a root server obtains the namespace information from AD domain controller using LDAP queries. So, most changes for supporting AD would be internal to CIFS server. Afshin Glenn Skinner wrote: > Date: Wed, 07 Oct 2009 10:10:47 -0700 > From: Jordan Brown <Jordan.Brown at sun.com> > Subject: PSARC 2009/534 - SMB/CIFS Standalone DFS > To: PSARC-ext at sun.com > > I'm sponsoring the following for fast track approval. The timer > expires 14 October 2009. > > ... > STANDALONE NAMESPACES IN SOLARIS > > ... > Only one standalone DFS namespace is supported per system. > Multiple DFS namespace support will be available in a future > project based on Active Directory (AD) domain-based DFS > namespaces. Once domain-based namespaces are supported, the > CIFS Service will also support multiple standalone DFS > namespaces - these are tied together by the DFS support level > that is announced by a server. > > When I saw "per system" above, it made me wonder about zones. > > So, could you say a a bit about how zones interact with this feature > (and what changes you anticipate when AD support is added)? > > -- Glenn >
