• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3873
  • Last Modified:

DFS Fileshares and offline files

We currently have issues with our Windows fileshares. We map several network drives through group policy. All network shares are within the same DFS namespace, \\domain\shares
In the same setup, we also redirect users Documents folder to a folder in the same DFS namespace. This folder is called \\domain\shares\redirect
I am aware of the issue with offline files and dfs namespaces, so I have configured slow link mode as follows:
\\domain.com\shares\* Latency=32000
\\domain.com\shares\redirect\* Latency=100

This however does not seem to work. Even on our local LAN, the root namespace \\domain.com is often taken offline on client computers. Then after some minutes, it is online again. Event viewer on client computers show, that it is offline files that offline the root dfs namespace.
All domain controllers, and DFS servers are Windows Server 2012 R2. All client computers are running Windows 8.1

Have I missed something in my configuration?
0
jnoergaard
Asked:
jnoergaard
  • 2
  • 2
1 Solution
 
MaheshArchitectCommented:
The "Offline" situation may not be caused by Slow Link but something else such as server restart, network connection, DNS issue

Have you checked client computer subnet is mapped to appropriate AD site, because DFS is site aware application and if domain.com get resolved to another location in case of multi site DFS, it might cause issues.
The Offline Files feature does not distinguish DFS paths from UNC paths. This can cause the Vista / Windows 7 client to interpret the entire namespace as unavailable if a target is down when a Vista / Windows 7 client attempts to access it.
One solution I can see, Use the NetBIOS Name or FQDN of the Target Server for mapping the Offline Files Share

Also try below hotfix on Win7 Computers
Its not the exact solution to your problem, but you can try
http://support.microsoft.com/kb/2705233

Mahesh
0
 
jnoergaardAuthor Commented:
The only solution was to not use the DFS namespace for the offline files share, but instead pointing this directly to one of the DFS servers.
0
 
jnoergaardAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for jnoergaard's comment #a39998378

for the following reason:

Only solution I could find.
0
 
MaheshArchitectCommented:
So, that is what the workaround I have suggested in my last comment

Please check my last comment:

One solution I can see, Use the NetBIOS Name or FQDN of the Target Server for mapping the Offline Files Share

Mahesh.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now