<div>
This was not my problem but award the points for taking the time to answer and that may help someone else.<br />
<br />
Our issue was that within DFS Mgmt we did not have &quot;Clients fail back to preferred targets&quot; selected.<br />
<br />
This option is in the properties of the namespace on the &quot;Referrals&quot; tab.
</div>


This was not my problem but award the points for taking the time to answer and that may help someone else.

Our issue was that within DFS Mgmt we did not have "Clients fail back to preferred targets" selected.

This option is in the properties of the namespace on the "Referrals" tab.

<div>
<div class="content wysiwyg-content">
We have Windows Server 2003 terminal servers with Citrix XenApp 4.5 installed.<br />
<br />
On occasion the shared drives will get very, very slow - we have figured out that the reason is that the server is accessing the DFS share from a file-server in a remote site (across the WAN) as opposed to one in the same site.<br />
<br />
We have a DFS share (\\domain\shared\Users) that is on three servers:<br />
-Server1 (in SITE1)<br />
-Server2 (in SITE2)<br />
-Server3 (in SITE3)<br />
<br />
The terminal servers are in SITE1 so they should use Server1 - and they do 95% of the time. &nbsp;<br />
Every once in a while one or several servers will switch to using SITE2 even though Server1 is up and available. &nbsp;We do have site costing turned on and the Site-to-IP mapping is setup properly.<br />
<br />
Is there any logging I can turn on in the clients to record when and why the DFS active server is switched?<br />
<br />
How do we troubleshoot this?<br />
<br />
<br />
<br />

</div>
</div>


We have Windows Server 2003 terminal servers with Citrix XenApp 4.5 installed.

On occasion the shared drives will get very, very slow - we have figured out that the reason is that the server is accessing the DFS share from a file-server in a remote site (across the WAN) as opposed to one in the same site.

We have a DFS share (\\domain\shared\Users) that is on three servers:
-Server1 (in SITE1)
-Server2 (in SITE2)
-Server3 (in SITE3)

The terminal servers are in SITE1 so they should use Server1 - and they do 95% of the time.  
Every once in a while one or several servers will switch to using SITE2 even though Server1 is up and available.  We do have site costing turned on and the Site-to-IP mapping is setup properly.

Is there any logging I can turn on in the clients to record when and why the DFS active server is switched?

How do we troubleshoot this?





Why is DFS Failing Over

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).