We recently deployed folder redirection for a few individuals in the office. We are using a DFS Namespace share on a Server 2012r2 VM. We are redirecting Desktop and My Documents only. Clients are running 8.1 and 7.

When using Word/Excel 2013, there is a popup that says "trying to connect to: \\DFSNAME\userfolder" and its stays there for 1-5 minutes before the browse window opens. This also occurs when trying to attach a file to an email in outlook. There are no delays if the file is double clicked on their desktop.

We've tried the following solutions (whcih seemed to describe our problem perfectly aside from the version):

The only thing that is different about this deployment of Folder Redirection is permissions. Instead of following the standard checkbox of exclusive access we used this ancient guide from microsoft - http://support.microsoft.com/kb/288991/. Could our permissions be causing these weird issues?

  • Does this occur when opening existing Word files, or also when starting just Word?
    – Daniel
    Feb 27 '15 at 19:47
  • Creating the new document doesn't have any lag, it's only when saving that document. It occurs on both new and existing.
    – pxed
    Feb 27 '15 at 19:49
  • I had a similar problem once. The reason probably is unrelated, but the troubleshooting could help you. I managed to find a solution running Sysinternal's Process Monitor on the client, aswell as the file server. Try filtering for RESULT != SUCCES, or try more narrow filters. On the client you should be able to see what word.exe is trying to access in detail, and on the server why exactly that fails. Good luck!
    – Daniel
    Feb 27 '15 at 19:55
  • We've had this happen too, Windows gets quite grumpy when My Docs responds slowly. Oddly on DFS shares a \\domain\<root> seems to work where a \\domain.com\<root> tends to stall. It wasn't consistent across the board, but check to see if the shares are accessible when Office is having issue. We never found a good solution except to remove the .com from the mapping for My Doc and Desktop.
    – MikeAWood
    Feb 27 '15 at 22:41
  • Any progress on this? Did you see something weird using the Sysinternals tools? Oh, and how many DFS targets do you currently have set up for "\\DFSNAME\userfolder", and are they all reachable from the client computer?
    – Daniel
    Mar 2 '15 at 9:09

Maybe you have to turn off the File Validation Feature? I've seen it many times with Office 2003 and Office 2007, but I suppose it is still part of Office 2013. You should enter the following in the user's registry:

REG_DWORD: EnableOnLoad 
Value: 0

Did you ever manage to get to the bottom of this? We're having this same issue with Server 2016, Office 2016 Pro Plus. Using folder redirections with a DFS namespace pointing to the location.


Using \\servername instead of \\domainname doesn't make a difference, however if you delete the DFS namespace suddenly \\servername works perfectly. But obviously we can't use \\domainname without the DFS namespace.

I found that changing the DFS mode from 2008 to 2000 made some difference initially, but it is just as slow as 2008 mode now.

  • Welcome to Server Fault and for your interest in it. However, your post does not answer the question that was asked and so should not be posted as an answer. If you have a different question, you can ask it by clicking Ask Question. See also: How to Ask.
    – Mr Shunz
    Feb 1 '19 at 13:52

try to turn off option in Internet properties -> Connections -> LAN Setings -> Autmaticly detect settings (CHECK BOX need to be unchecked)

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.