| Author |
Message |
andrew
Guest
|
 Posted:
Wed Jan 19, 2005 5:37 pm Post subject:
DFS - wrong active server |
|
|
DFS clients are finding that their default active server is often not the
nearest. This is causing us all sorts of issues.
Our DFS share has 2 Root Targets, both on Windows 2003 servers. The servers
are in different sites and subnets (File-1 in Site-1, File-2 in Site-2).
They were initially set up in the same site and subnet and then File-2 was
moved to Site-2. The site move took place 2 weeks ago, so time has elapsed
for the change to be registered, and the Dfsutil /view command list the 2
servers in different sites. All Domain Controllers are running Win2K3.
Does anyone know what might be causing this and what we can do to change it?
We need Site-1 users' active server to default to File-1 and Site-2 users to
default to Site-2.
Thanks |
|
| Back to top |
|
 |
Jill Zoeller [MSFT]
Guest
|
| Posted:
Thu Jan 20, 2005 3:54 am Post subject:
Re: DFS - wrong active server |
|
|
This is a tough type of problem to troubleshoot, especially if the servers
are properly set up in their own sites. I'm pasting a list of potential
causes in hopes that one might apply to your case. Take a look and see if
anything rings a bell.
.. The same-site target is temporarily unavailable (due to server or network
issues), and the client fails over to the next target, which could be
outside of the client's site.
.. DFS uses the IP address-to-site mappings in Active Directory to determine
the site of a target. If a target's IP address is not mapped to its current
site, DFS cannot properly order that target in a referral. Incorrect site
mappings can occur when subnets are not configured correctly or when a
server or domain controller is moved to another site in the Active Directory
Sites and Services snap-in, but the server's or domain controller's IP
address still maps to the subnet of the previous site. Incorrect site
mappings often occur when domain controllers are not moved to the site that
corresponds to their IP address or when domain controllers are left in the
default first site or the site where they originally belonged.
.. If no same-site targets exist and a client unexpectedly chooses a
high-cost target, it might be caused by an incorrect site cost setting.
.. The client's IP address is not in a subnet that is defined in Active
Directory and so DFS cannot obtain site information about the client.
.. The target's IP address is not in a subnet that is defined in Active
Directory and so DFS cannot obtain site information about the target.
.. DNS lookup issues on the DFS root server are causing DNS name-to-IP
address mappings to fail. The problem might be caused by DNS issues or when
a server has multiple IP addresses but not all of those addresses are mapped
to sites in Active Directory.
.. The client is using a cached referral that has become outdated due to
target changes, site changes, or both. For example, a target was added or
removed from a link or root, or a target was moved from one site to another.
The client will obtain an updated referral after the referral expires, the
client's cache is cleared (using the Dfsutil.exe /pktflush command), or the
client is rebooted.
.. Site information has changed, but the old site information is still cached
on the root server or domain controller in the target site cache, client
site cache, or site cost cache.
.. The DFS object is not up-to-date when the root server polls a domain
controller. This can be caused by Active Directory replication latency or
failure.
.. The Bridge all site links option is disabled. (This option is available in
the Active Directory Sites and Services snap-in.) Turning off Bridge all
site links can affect the ability of DFS to refer client computers to target
computers that have the least expensive connection cost. An Intersite
Topology Generator that is running Windows Server 2003 relies on the Bridge
all site links option being enabled to generate the intersite cost matrix
that DFS requires for its site-costing functionality. If you turn off this
option, you must create site links between the Active Directory sites for
which you want DFS to calculate accurate site costs. Any sites that are not
connected by site links will have the maximum possible cost. For more
information about site link bridging, see Active Directory Replication
Topology Technical Reference.
.. Site awareness is not working correctly because the restrictanonymous
registry entry located at
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa is set to 2 on
Windows 2000 domain controllers. If this registry entry is set to 2, DFS
root servers that are not domain controllers (and are running either Windows
2000 Server or Windows Server 2003) randomly sort the targets in a referral,
regardless of the namespace type (stand-alone or domain-based), target
selection method, or client operating system.
.. Domain controllers do not consistently provide site-costed SYSVOL
referrals because the SiteCostedReferrals registry entry was not set on all
domain controllers.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"andrew" <andrew@discussions.microsoft.com> wrote in message
news:90627F62-76C4-4A98-A49F-156107DC0ACA@microsoft.com...
| Quote: | DFS clients are finding that their default active server is often not the
nearest. This is causing us all sorts of issues.
Our DFS share has 2 Root Targets, both on Windows 2003 servers. The
servers
are in different sites and subnets (File-1 in Site-1, File-2 in Site-2).
They were initially set up in the same site and subnet and then File-2 was
moved to Site-2. The site move took place 2 weeks ago, so time has
elapsed
for the change to be registered, and the Dfsutil /view command list the 2
servers in different sites. All Domain Controllers are running Win2K3.
Does anyone know what might be causing this and what we can do to change
it?
We need Site-1 users' active server to default to File-1 and Site-2 users
to
default to Site-2.
Thanks
|
|
|
| Back to top |
|
|
andrew
Guest
|
| Posted:
Fri Jan 21, 2005 5:47 pm Post subject:
Re: DFS - wrong active server |
|
|
The SiteCostedReferrals registry entry was not present at all in any of the
Domain Controllers. I have added it in and will restart the DFS service at a
suitable point. Should this entry be added by default, by what application
and where?
Thanks
Andrew
"Jill Zoeller [MSFT]" wrote:
| Quote: | This is a tough type of problem to troubleshoot, especially if the servers
are properly set up in their own sites. I'm pasting a list of potential
causes in hopes that one might apply to your case. Take a look and see if
anything rings a bell.
.. The same-site target is temporarily unavailable (due to server or network
issues), and the client fails over to the next target, which could be
outside of the client's site.
.. DFS uses the IP address-to-site mappings in Active Directory to determine
the site of a target. If a target's IP address is not mapped to its current
site, DFS cannot properly order that target in a referral. Incorrect site
mappings can occur when subnets are not configured correctly or when a
server or domain controller is moved to another site in the Active Directory
Sites and Services snap-in, but the server's or domain controller's IP
address still maps to the subnet of the previous site. Incorrect site
mappings often occur when domain controllers are not moved to the site that
corresponds to their IP address or when domain controllers are left in the
default first site or the site where they originally belonged.
.. If no same-site targets exist and a client unexpectedly chooses a
high-cost target, it might be caused by an incorrect site cost setting.
.. The client's IP address is not in a subnet that is defined in Active
Directory and so DFS cannot obtain site information about the client.
.. The target's IP address is not in a subnet that is defined in Active
Directory and so DFS cannot obtain site information about the target.
.. DNS lookup issues on the DFS root server are causing DNS name-to-IP
address mappings to fail. The problem might be caused by DNS issues or when
a server has multiple IP addresses but not all of those addresses are mapped
to sites in Active Directory.
.. The client is using a cached referral that has become outdated due to
target changes, site changes, or both. For example, a target was added or
removed from a link or root, or a target was moved from one site to another.
The client will obtain an updated referral after the referral expires, the
client's cache is cleared (using the Dfsutil.exe /pktflush command), or the
client is rebooted.
.. Site information has changed, but the old site information is still cached
on the root server or domain controller in the target site cache, client
site cache, or site cost cache.
.. The DFS object is not up-to-date when the root server polls a domain
controller. This can be caused by Active Directory replication latency or
failure.
.. The Bridge all site links option is disabled. (This option is available in
the Active Directory Sites and Services snap-in.) Turning off Bridge all
site links can affect the ability of DFS to refer client computers to target
computers that have the least expensive connection cost. An Intersite
Topology Generator that is running Windows Server 2003 relies on the Bridge
all site links option being enabled to generate the intersite cost matrix
that DFS requires for its site-costing functionality. If you turn off this
option, you must create site links between the Active Directory sites for
which you want DFS to calculate accurate site costs. Any sites that are not
connected by site links will have the maximum possible cost. For more
information about site link bridging, see Active Directory Replication
Topology Technical Reference.
.. Site awareness is not working correctly because the restrictanonymous
registry entry located at
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa is set to 2 on
Windows 2000 domain controllers. If this registry entry is set to 2, DFS
root servers that are not domain controllers (and are running either Windows
2000 Server or Windows Server 2003) randomly sort the targets in a referral,
regardless of the namespace type (stand-alone or domain-based), target
selection method, or client operating system.
.. Domain controllers do not consistently provide site-costed SYSVOL
referrals because the SiteCostedReferrals registry entry was not set on all
domain controllers.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"andrew" <andrew@discussions.microsoft.com> wrote in message
news:90627F62-76C4-4A98-A49F-156107DC0ACA@microsoft.com...
DFS clients are finding that their default active server is often not the
nearest. This is causing us all sorts of issues.
Our DFS share has 2 Root Targets, both on Windows 2003 servers. The
servers
are in different sites and subnets (File-1 in Site-1, File-2 in Site-2).
They were initially set up in the same site and subnet and then File-2 was
moved to Site-2. The site move took place 2 weeks ago, so time has
elapsed
for the change to be registered, and the Dfsutil /view command list the 2
servers in different sites. All Domain Controllers are running Win2K3.
Does anyone know what might be causing this and what we can do to change
it?
We need Site-1 users' active server to default to File-1 and Site-2 users
to
default to Site-2.
Thanks
|
|
|
| Back to top |
|
|
Jill Zoeller [MSFT]
Guest
|
| Posted:
Fri Jan 21, 2005 11:07 pm Post subject:
Re: DFS - wrong active server |
|
|
This value applies only to SYSVOL referrals, not to general DFS referrals.
Unfortunately I don't think this will solve your problem.
Your best bet is to work with Microsoft product support services to
troubleshoot this problem.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"andrew" <andrew@discussions.microsoft.com> wrote in message
news:E029784C-4F4F-428D-AE7D-D9DF33AA248A@microsoft.com...
| Quote: | The SiteCostedReferrals registry entry was not present at all in any of
the
Domain Controllers. I have added it in and will restart the DFS service
at a
suitable point. Should this entry be added by default, by what
application
and where?
Thanks
Andrew
"Jill Zoeller [MSFT]" wrote:
This is a tough type of problem to troubleshoot, especially if the
servers
are properly set up in their own sites. I'm pasting a list of potential
causes in hopes that one might apply to your case. Take a look and see if
anything rings a bell.
.. The same-site target is temporarily unavailable (due to server or
network
issues), and the client fails over to the next target, which could be
outside of the client's site.
.. DFS uses the IP address-to-site mappings in Active Directory to
determine
the site of a target. If a target's IP address is not mapped to its
current
site, DFS cannot properly order that target in a referral. Incorrect site
mappings can occur when subnets are not configured correctly or when a
server or domain controller is moved to another site in the Active
Directory
Sites and Services snap-in, but the server's or domain controller's IP
address still maps to the subnet of the previous site. Incorrect site
mappings often occur when domain controllers are not moved to the site
that
corresponds to their IP address or when domain controllers are left in
the
default first site or the site where they originally belonged.
.. If no same-site targets exist and a client unexpectedly chooses a
high-cost target, it might be caused by an incorrect site cost setting.
.. The client's IP address is not in a subnet that is defined in Active
Directory and so DFS cannot obtain site information about the client.
.. The target's IP address is not in a subnet that is defined in Active
Directory and so DFS cannot obtain site information about the target.
.. DNS lookup issues on the DFS root server are causing DNS name-to-IP
address mappings to fail. The problem might be caused by DNS issues or
when
a server has multiple IP addresses but not all of those addresses are
mapped
to sites in Active Directory.
.. The client is using a cached referral that has become outdated due to
target changes, site changes, or both. For example, a target was added or
removed from a link or root, or a target was moved from one site to
another.
The client will obtain an updated referral after the referral expires,
the
client's cache is cleared (using the Dfsutil.exe /pktflush command), or
the
client is rebooted.
.. Site information has changed, but the old site information is still
cached
on the root server or domain controller in the target site cache, client
site cache, or site cost cache.
.. The DFS object is not up-to-date when the root server polls a domain
controller. This can be caused by Active Directory replication latency or
failure.
.. The Bridge all site links option is disabled. (This option is
available in
the Active Directory Sites and Services snap-in.) Turning off Bridge all
site links can affect the ability of DFS to refer client computers to
target
computers that have the least expensive connection cost. An Intersite
Topology Generator that is running Windows Server 2003 relies on the
Bridge
all site links option being enabled to generate the intersite cost matrix
that DFS requires for its site-costing functionality. If you turn off
this
option, you must create site links between the Active Directory sites for
which you want DFS to calculate accurate site costs. Any sites that are
not
connected by site links will have the maximum possible cost. For more
information about site link bridging, see Active Directory Replication
Topology Technical Reference.
.. Site awareness is not working correctly because the restrictanonymous
registry entry located at
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa is set to 2 on
Windows 2000 domain controllers. If this registry entry is set to 2, DFS
root servers that are not domain controllers (and are running either
Windows
2000 Server or Windows Server 2003) randomly sort the targets in a
referral,
regardless of the namespace type (stand-alone or domain-based), target
selection method, or client operating system.
.. Domain controllers do not consistently provide site-costed SYSVOL
referrals because the SiteCostedReferrals registry entry was not set on
all
domain controllers.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"andrew" <andrew@discussions.microsoft.com> wrote in message
news:90627F62-76C4-4A98-A49F-156107DC0ACA@microsoft.com...
DFS clients are finding that their default active server is often not
the
nearest. This is causing us all sorts of issues.
Our DFS share has 2 Root Targets, both on Windows 2003 servers. The
servers
are in different sites and subnets (File-1 in Site-1, File-2 in
Site-2).
They were initially set up in the same site and subnet and then File-2
was
moved to Site-2. The site move took place 2 weeks ago, so time has
elapsed
for the change to be registered, and the Dfsutil /view command list the
2
servers in different sites. All Domain Controllers are running Win2K3.
Does anyone know what might be causing this and what we can do to
change
it?
We need Site-1 users' active server to default to File-1 and Site-2
users
to
default to Site-2.
Thanks
|
|
|
| Back to top |
|
|
andrew
Guest
|
| Posted:
Mon Jan 24, 2005 3:47 pm Post subject:
Re: DFS - wrong active server |
|
|
Thanks for your help, Jill
"Jill Zoeller [MSFT]" wrote:
| Quote: | This value applies only to SYSVOL referrals, not to general DFS referrals.
Unfortunately I don't think this will solve your problem.
Your best bet is to work with Microsoft product support services to
troubleshoot this problem.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"andrew" <andrew@discussions.microsoft.com> wrote in message
news:E029784C-4F4F-428D-AE7D-D9DF33AA248A@microsoft.com...
The SiteCostedReferrals registry entry was not present at all in any of
the
Domain Controllers. I have added it in and will restart the DFS service
at a
suitable point. Should this entry be added by default, by what
application
and where?
Thanks
Andrew
"Jill Zoeller [MSFT]" wrote:
This is a tough type of problem to troubleshoot, especially if the
servers
are properly set up in their own sites. I'm pasting a list of potential
causes in hopes that one might apply to your case. Take a look and see if
anything rings a bell.
.. The same-site target is temporarily unavailable (due to server or
network
issues), and the client fails over to the next target, which could be
outside of the client's site.
.. DFS uses the IP address-to-site mappings in Active Directory to
determine
the site of a target. If a target's IP address is not mapped to its
current
site, DFS cannot properly order that target in a referral. Incorrect site
mappings can occur when subnets are not configured correctly or when a
server or domain controller is moved to another site in the Active
Directory
Sites and Services snap-in, but the server's or domain controller's IP
address still maps to the subnet of the previous site. Incorrect site
mappings often occur when domain controllers are not moved to the site
that
corresponds to their IP address or when domain controllers are left in
the
default first site or the site where they originally belonged.
.. If no same-site targets exist and a client unexpectedly chooses a
high-cost target, it might be caused by an incorrect site cost setting.
.. The client's IP address is not in a subnet that is defined in Active
Directory and so DFS cannot obtain site information about the client.
.. The target's IP address is not in a subnet that is defined in Active
Directory and so DFS cannot obtain site information about the target.
.. DNS lookup issues on the DFS root server are causing DNS name-to-IP
address mappings to fail. The problem might be caused by DNS issues or
when
a server has multiple IP addresses but not all of those addresses are
mapped
to sites in Active Directory.
.. The client is using a cached referral that has become outdated due to
target changes, site changes, or both. For example, a target was added or
removed from a link or root, or a target was moved from one site to
another.
The client will obtain an updated referral after the referral expires,
the
client's cache is cleared (using the Dfsutil.exe /pktflush command), or
the
client is rebooted.
.. Site information has changed, but the old site information is still
cached
on the root server or domain controller in the target site cache, client
site cache, or site cost cache.
.. The DFS object is not up-to-date when the root server polls a domain
controller. This can be caused by Active Directory replication latency or
failure.
.. The Bridge all site links option is disabled. (This option is
available in
the Active Directory Sites and Services snap-in.) Turning off Bridge all
site links can affect the ability of DFS to refer client computers to
target
computers that have the least expensive connection cost. An Intersite
Topology Generator that is running Windows Server 2003 relies on the
Bridge
all site links option being enabled to generate the intersite cost matrix
that DFS requires for its site-costing functionality. If you turn off
this
option, you must create site links between the Active Directory sites for
which you want DFS to calculate accurate site costs. Any sites that are
not
connected by site links will have the maximum possible cost. For more
information about site link bridging, see Active Directory Replication
Topology Technical Reference.
.. Site awareness is not working correctly because the restrictanonymous
registry entry located at
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa is set to 2 on
Windows 2000 domain controllers. If this registry entry is set to 2, DFS
root servers that are not domain controllers (and are running either
Windows
2000 Server or Windows Server 2003) randomly sort the targets in a
referral,
regardless of the namespace type (stand-alone or domain-based), target
selection method, or client operating system.
.. Domain controllers do not consistently provide site-costed SYSVOL
referrals because the SiteCostedReferrals registry entry was not set on
all
domain controllers.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"andrew" <andrew@discussions.microsoft.com> wrote in message
news:90627F62-76C4-4A98-A49F-156107DC0ACA@microsoft.com...
DFS clients are finding that their default active server is often not
the
nearest. This is causing us all sorts of issues.
Our DFS share has 2 Root Targets, both on Windows 2003 servers. The
servers
are in different sites and subnets (File-1 in Site-1, File-2 in
Site-2).
They were initially set up in the same site and subnet and then File-2
was
moved to Site-2. The site move took place 2 weeks ago, so time has
elapsed
for the change to be registered, and the Dfsutil /view command list the
2
servers in different sites. All Domain Controllers are running Win2K3.
Does anyone know what might be causing this and what we can do to
change
it?
We need Site-1 users' active server to default to File-1 and Site-2
users
to
default to Site-2.
Thanks
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in