Hi, Jas
If I understand the problem correctly, the DFS clients are accessing the DFS
root server in a remote site, even though the local site is available. If
that's the case, this KB article might help:
http://support.microsoft.com/kb/944505
SYMPTOMS
Consider the following scenario:
. In a Windows Server 2003-based domain, you configure the Distributed
File System (DFS) together with multiple DFS root servers. Some servers are
located in the local site, and the other servers are located in a remote
site.
. Users in the local site use DFS to access shares.
In this scenario, the active DFS target may switch to a server in the remote
site even if the DFS root server in the local site is available. This
problem may cause the users in the domain to experience a slow response when
they access a DFS share.
Hope it helps...
--Malu
"jas0n" <> wrote in message
news:. ..
>I have domain based dfs namespaces and where the namespace points to
> folder tartget residing on a server in a different site it reports the
> correct site.
>
> The problem seems to be where the namespace is pointing to another
> domain based dfs namespace, this one reports a remote site, I guess Im
> expecting the main site where the pdc is held to be shown as the site.
> Not sure where it picks up this information?
>
> Example:-
>
> Namespace: \\domain.local\share
>
> Folder Target 1: \\remoteserver\share - correct site shown
> Folder Target 2: \\domain.local\share - incorrect site shown
>
> Would it be showing the site where the dfs namespace was originally
> created?
>
> The domain is a mix of 2000/2003 DC's, the site shown for folder target
> 2 is a Windows 2000 server.