On Mon, 25 Aug 2008 15:51:03 -0700, Daniel Kaliel
<> wrote:
>I tried adding the DC's in our domain to the namespaces and still did not see
>the shares when I would browse to \\my.domain from a workstation. I still
>needed to browse to \\server1 in order to see the dfs shares.
That is what I expected. Not publishing the Root in the browser list was
discussed a couple of years ago and somebody from MS did say this was being
considered for a future enhancement. It is a pity is has not been added as
having to rely upon a single server to locate the root name flies in the face of
fault tolerant. It may have the added benefit of enabling none domain member
computers to use the Root to access the namespace. At present this can only be
done by browsing one of the name servers.
>
>"DaveMills" wrote:
>
>> On Fri, 8 Aug 2008 18:01:18 +0200, "Brian Kirkegaard" <> wrote:
>>
>> >Hi Dave,
>> >
>> >Thanks for your response - this is quite unfortuante.
>> >
>> >What we can do is to install DFS services on all DC's and add these to the
>> >namespaces, thereby making it possible to browse the root domain.
>>
>> I am not sure this will work either, I have had DFS on the DCs in the past but
>> not now so I cannot test it. I still do not think is will allow you to browse
>> the domain for the root. You will have to browse the DC by name.
>>
>> Let us (me) know if this is not correct.
>>
>> I do not think having DFS on a DC is exactly poor implementation I just like the
>> idea that the DFS server job should be part of the file servers role.
>>
>> >
>> >This approach leads to two new questions:
>> >
>> >1) Would this break any "best practice" and would there be a substantial
>> >impact on the DC roles if we do this? Could we somehow prioritize the
>> >primary DFS management servers to answer most queries except root browsing?
>> >2) Is there some way to hide the "NETLOGON", "SYSVOL" and "Printers"
>> >shares?.
>> >
>> >Thanks,
>> >-Brian
>> >
>> >
>> >"DaveMills" <> wrote in message
>> >news:.. .
>> >> This have never worked. It is a "feature" but not a good one. You can see
>> >> the
>> >> Nomespace01 share if you browse one of the namespace servers.
>> >>
>> >> I think that while not publishing the name in the browse list is not
>> >> really a
>> >> bug it is an oversight which if corrected would improve the DFS system in
>> >> the
>> >> direction of fault tolerance and user acceptance.
>> >>
>> >>
>> >> On Wed, 6 Aug 2008 11:37:51 +0200, "Brian Kirkegaard" <>
>> >> wrote:
>> >>
>> >>>Hi
>> >>>
>> >>>We're in the process of testing DFS domain-based namespaces in Windows
>> >>>server 2008.
>> >>>We have set up a very small test environment consisting of one domain
>> >>>controller (dc01) and one DFS Namespace server (dfs01).
>> >>>We have only one namespace (namespace01) with several folders at the
>> >>>moment.
>> >>>
>> >>>The problem we're having is that we cannot see the the namespace root
>> >>>(namespace01) when browsing \\dom.com.
>> >>>We CAN see the folders in the namespace if we browse
>> >>>\\dom.com\namespace01.
>> >>>
>> >>>What should we do to make the namespace roots visible at the domain level?
>> >>>
>> >>>Thanks,
>> >>>-Brian
>> >>>
>> >> --
>> >> Dave Mills
>> >> There are 10 type of people, those that understand binary and those that
>> >> don't.
>> >
>> --
>> Dave Mills
>> There are 10 type of people, those that understand binary and those that don't.
>>
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.
|
Similar Threads
Linear Mode
