Hi, Our Windows 7 clients take a long time (on average 3 minutes) to access domain-based dfs shares (\\domain\dfs). When these shares are mapped as drives there are no delays. Also when accessing the shares via unc server paths there are no delays (\\server\share). XP clients have no problems accessing these either through drive letters or unc paths. Tried so many suggestions from various forums but without much luck. Whilst we get by with accessing the files through the mapped drives, it's company policy to not send attachments to emails when the files are in the network. These are instead hyperlinked. Windows 7 clients have a long wait when attempting to open files in this manner. Our servers are all Windows 2003 R2 with the latest service packs and updates. Thanks to anyone who can help.

Hi, May I know where the hyperlink is, in the email? In Windows 7, please try the following commands in an elevated command prompt in Windows 7: netsh interface tcp set global rss=disabled netsh interface tcp set global autotuninglevel=disabled netsh int ip set global taskoffload=disabled Hope this helps. Thanks. Nicholas Li - MSFT

Hi, We have exactly the same issues as Booldeeker: Windows 7 clients taking forever to access domain-based dfs resources when done via UNC or as hyperlinks in documents or emails. Mapping the resources to drives works fine, as do all other clients (XP and Vista) using either mapped drives or UNC. I tried your suggestions above without luck. Also tried some registry settings suggested in other forums, with the same results. We have 5 computers running Windows 7 in our Windows 2003 domain, with the intention of rolling out the former to the rest of the users. At this point, we'll have to put this back until we resolve this issue.

Fixed the issue! We were using the domain controller as the only namespace server. We then created a new namespace using a different namespace server, and added target folders, and found that these can be accessed by our Windows 7 clients without any delay (either via UNC or as hyperlinks within emails or documents). I'm not sure what the DC in its capacity as a namespace server had against the Windows 7 computers (worth an investigation at some point!), but we've now changed all our namespace servers to point to member servers. If you're going to do this, I recommend waiting until there are no open files.