Long pause when accessing DFS namespace. Well, we finally appear to have resolved this issue in our environment. For the benefits of others, heres what we discovered and how we fixed the problem To try and gain further insight into what was occurring beforeduringafter the delays we used Wireshark on a client machine to captureanalyse network traffic whilst that client attempted to access a DFS share. Does your explorer take a long time also opening Devices and Printers What about folders without that many files I second this question, too. Make-File-Explorer-to-open-This-PC-Windows-10-step1.png' alt='Windows Explorer Long Delay Opening Files' title='Windows Explorer Long Delay Opening Files' />These captures showed something strange whenever the delay occurred, in between the DFS request being sent from the client to a DC, and the referral to a DFS root server coming back from the DC to the client, the DC was sending out several broadcast name lookups to the network. Firstly, the DC would broadcast a Net. BIOS lookup for DOMAIN where DOMAIN is our pre Windows 2. Active Directory domain name. Adobe Dreamweaver Cs4 Serial Number on this page. A few seconds later, it would broadcast a LLMNR lookup for DOMAIN. This would be followed by yet another broadcast Net. Bios lookup for DOMAIN. After these three lookups had been broadcast and I assume timed out the DC would finally respond to the client with a correct referral to a DFS root server. These broadcast name lookups for DOMAIN were only being sent when the long delay opening a DFS share occurred, and we could clearly see from the Wireshark capture that the DC wasnt returning a referral to a DFS root server until all three lookups been sent and 7 seconds passed. So, these broadcast name lookups were pretty obviously the cause of our delays. Now that we knew what the problem was, we started trying to figure out why these broadcast name lookups were occurring. After a bit more Googling and some trial and error, we found our answer we hadnt set the Dfs. Dns. Config registry key on our domain controllers to 1, as is required when using DFS in a DNS only environment. When we originally setup DFS in our enviroment we did read the various articles about how to configure DFS for a DNS only environment e. Microsoft KB2. 44. KB2. 44. 38. 0 says The DFSDns. Config registry key must be. Computer Configuration Policies Administrative templates Windows Components Remotes Desktop Services Remote desktop Session Host Security Always prompt for password. Update news for GoodSyncs Windows file sync and backup software. Key Command Command id K D Windows, Linux CtrlK D Compare a dirty file with the version on disk workbench. WithSaved Backspace Windows. File Explorer, previously known as Windows Explorer, is a file manager application that is included with releases of the Microsoft Windows operating system from. Back in the day I could use Microsoft Binder to bind together all the Office files I needed for a given task. After a reboot. I could just reopen the binder or. Many thanks It helped me as well. From the very beginning the sharrpoint was working fast in both IE and Windows Explorer WE Total commander. DFS namespace for. We thought this meant that the registry key has to be set on the DFS namespace servers only, not realising that it was also required on the domain controllers. Who Want To Be A Millionaire Flash Game Free Download. Fs2004 Ground Environment. After we set Dfs. Dns. Config to 1 on our domain controllers and restarted the DFS Namespace service, the problem vanished. Obviously were happy with this outcome, but I would add that Im still not 1. Windows Explorer Long Delay Opening Files' title='Windows Explorer Long Delay Opening Files' />I wonder if adding Dfs. Dns. Config1 to our DCs has only worked around the problem, rather than solving it. I cant figure out why the DCs would be trying to lookup DOMAIN the domain name itself, rather than a server in the domain during the DFS referral process, even in a non DNS only environment, and I also know I havent set Dfs. Dns. Config1 on domain controllers in other admittedly much smaller simpler DNS only environments and havent had the same issue. Still, weve solved our problem so we are happy. I hope this is helpful to the others who are experiencing a similar issue and thanks again to those that offered suggestions along the way.