Share via

DFS Share and Azure Files - DFS Name Access Extremely Slow when WebClient service Running in Windows 10

Anonymous
2023-09-21T19:01:48+00:00

Here's the issue:

We just did a large on premises file share migration to Azure Files (serverless), and implemented a DFS namespace server (Windows 2022 with root consolidation) so all existing file share paths would be retained and it's less noticeable for our end users.

We mapped drives for everyone using the DFS namespace, and that works fine.

However, we found that when a user browses to the mapped Azure File share via Office Apps or even Adobe, the server says "contacting \dfsname\share...", and it takes 20-30 seconds before the folder structure appears on the screen. If we map the drive directly to the Azure Storage Account path, there is no delay when clicking on it.

After much searching, we found a workaround where if the WebClient service is stopped and disabled (it MUST be stopped AND disabled), the delay is completely gone, and the Azure File shares are appearing back to normal speed.

I understand the WebClient service is using WebDAV. But why would WebDAV be attempted first (I'm guessing it's trying to access the share via WebDAV, failing, and finally SMB access works)?

Seems like an issue with WebDAV functionality and DFS, but can't pinpoint the exact problem. We're trying to disable the WebClient service but also don't know if that will affect other workloads for our users.

All resources are behind private endpoints, and Azure File shares are only accessible via VPN.

Any help is appreciated.

Windows for business | Windows Server | Networking | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-09-22T07:34:18+00:00

    Hello CLO_979

    We appreciate your engagement here in the Microsoft Community. For assistance with your Azure-related matters, we recommend reaching out to Microsoft Q&A. This platform is dedicated to addressing advanced users' technical inquiries and providing expert guidance.

    Feel free to share your concern on the Microsoft Q&A section by following the "Introduction to Q&A" link:  Microsoft-supported products in Q&A | Learn with Microsoft

    Thank you for your understanding and collaboration.

    Regards,

    Karlie

    0 comments
  2. Anonymous
    2024-03-18T04:38:07+00:00

    After migrating to Azure file storage and implementing DFS-N across our site-to-site VPN tunnel to Azure, our users were experiencing frustrating delays of approximately 23 seconds.

    However, I stumbled upon a post that provided an instant solution! Although Microsoft couldn’t explain why this worked, I’ve directed them to this post for further investigation. They’ll determine whether this solution is optimal or if it might introduce other issues.

    I’ll keep you all updated once I hear back from Microsoft this week.

    Special thanks to CLO_979 for posting this valuable information. Without it, I would have remained stuck in Sev A troubleshooting mode indefinitely. At one point, I was even considering rolling back to our previous on-prem config!

    Kudos to Clo_979—I greatly appreciate your contribution!

    -KH_0869

    0 comments
  3. Anonymous
    2024-03-18T13:43:05+00:00

    After migrating to Azure file storage and implementing DFS-N across our site-to-site VPN tunnel to Azure, our users were experiencing frustrating delays of approximately 23 seconds.

    However, I stumbled upon a post that provided an instant solution! Although Microsoft couldn’t explain why this worked, I’ve directed them to this post for further investigation. They’ll determine whether this solution is optimal or if it might introduce other issues.

    I’ll keep you all updated once I hear back from Microsoft this week.

    Special thanks to CLO_979 for posting this valuable information. Without it, I would have remained stuck in Sev A troubleshooting mode indefinitely. At one point, I was even considering rolling back to our previous on-prem config!

    Kudos to Clo_979—I greatly appreciate your contribution!

    -KH_0869

    Glad this worked out for you and thanks for the Kudos. We still have the WebClient disabled and never received resolution from Microsoft. For now, it is not affecting our clients in a negative way.
    I have another thread open with the Azure community as suggested, DFS Share and Azure Files - DFS Name Access Extremely Slow when WebClient service Running in Windows - Microsoft Q&A. I don't believe there was an update though...please keep us posted if MS gets back to you with a firm resolution!

    1 person found this answer helpful.
    0 comments