Microsoft KB Archive/309648

= &quot;Error Code 0x10fe ERROR_FILE_OFFLINE&quot; Error Message When You Redirect the My Documents Folder to a Distributed File System Share =

Article ID: 309648

Article Last Modified on 11/27/2007

-

APPLIES TO


 * Microsoft Windows 2000 Advanced Server

-



This article was previously published under Q309648





SYMPTOMS
When you apply a Folder Redirection Group Policy that redirects the My Documents folder to a Microsoft Distributed File System (DFS) share, you may receive an error message similar to the following error message:

Error code 0x10fe [ (decimal 4350) == ERROR_FILE_OFFLINE]

You receive this error message even though the DFS share is online.



CAUSE
This problem may occur if the Mrxsmb.sys component does not correctly resolve the UNC path of the target shared folder. In this situation, the Mrxsmb.sys component may incorrectly report the DFS share where the folder is redirected as offline. This problem may occur if all the following conditions are true:
 * The client has turned on the Offline Files feature.
 * The Folder Redirection Group Policy is configured to redirect the My Documents folder on the client to a DFS root share, for example, \\Server1.Lab\DfsRoot
 * The DFS root share points to a single DFS replica share. For example, the DFS root share, \\Server1.Lab\DFSRoot, points to the DFS replica, \\DC1\DFSRoot Replica1. This is equivalent to \\DC1.Server1.Lab\DfsRootReplica1
 * The caching option is disabled at the shared folder level. For example, caching is disabled on DFSRoot and DFSRootReplica1.

The Mrxsmb.sys component keeps track of the physical shares (such as the DFS replica share in this example, DFSRoot Replica1), but does not keep track of the virtual shares (in this example, the DFSRoot share ).

In the scenario that is mentioned in the &quot;Cause&quot; section of this article, the UNC path (\\Server1.Lab\DfsRoot) is not resolved correctly to \\DC1.Server1.Lab\DfsRootReplica1. The Mrxsmb.sys component links a server name (\\DC1.Server1.Lab), to a DFSRootName (Server1.Lab), and then appends the share name that it is looking for (DFSRoot) to the server name. The resulting path is \\DC1.Server1.Lab\DFSRoot. However, this path does not exist because the server named DC1 handles the DfsRootReplica1 share and does not directly handle the DFSRoot share. The UNC path is incorrectly resolved as \\DC1.Server1.Lab\DFSRoot instead of \\DC1.Server1.Lab\DfsRootReplica1.



WORKAROUND
To work around this problem, use the same name for the DFS root share and the DFS replica share where the DFS root share points.

Note Only use this workaround if the problem that you are experiencing occurs under the specific conditions that are mentioned in the &quot;Symptoms&quot; and &quot;Cause&quot; sections of this article.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
For more information about DFS in Windows 2000, visit the following Microsoft Web sites:

http://technet.microsoft.com/en-us/library/Bb727150.aspx

http://technet2.microsoft.com/windowsserver/en/library/007e4e66-af67-4bfe-bf70-780412aeed6f1033.mspx

http://www.microsoft.com/windows2000/docs/dfsnew.doc

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/default.mspx?mfr=true (from the Distributed Systems Guide in the Windows 2000 Server Resource Kit Supplement 1)

Keywords: kbnofix kbbug kbnetwork KB309648

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.