Article ID: 2603586 - View products that this article applies to.
Consider the following Scenario:
In this Scenario you encounter an Error Message when you try to access the Link the First time.
The Error Message states:
The network name cannot be found."
When you instead try to access the WebDav Path (i.e. \\Servername\Shared Documents) directly you will notice a slight delay during the first access but the content of the Share is displayed.
Afterwards the DFS-Link works as well until the next restart.
When accessing the UNC WebDav Path directly the System determines, that it requires the WebClient Service in order to access the UNC Path provided.
Therefore it starts the WebClient Service and then access the WebDav path successfully.
When accessing the DFS Link, the System determines that it requires the DFS Client to resolve the Link into the UNC path and access it.
In this Case the WebClient Service is not started and therefore the access to the WebDav Path fails unless the WebClient was already running.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2603586 - Last Review: December 26, 2012 - Revision: 2.0