Microsoft small business knowledge base

Article ID: 2285823 - Last Review: August 31, 2010 - Revision: 2.0

Hotfix Download Available
View and request hotfix downloads

On This Page


Consider the following scenario:
  • You join a computer that is running Windows Server 2008 R2 into a domain.
  • You install the Distributed File System (DFS) Namespace services on the computer. 
  • The domain controller that plays the Inter-Site Topology Generator (ISTG) role in the same site is down.
In this scenario, the DFS Namespace service becomes inaccessible. This causes some DFS shares to be unavailable.


This issue is caused by the DFS Namespace service. It incorrectly contacts the domain controller that plays the ISTG role to obtain the topology data directly. The topology data contains the information for different destination file servers and the requesting clients. If the domain controller is not available, the DFS namespace service fails. Therefore, this issue occurs. In fact, the DFS Namespace services can obtain this information from any domain controller in the domain.


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: (
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must be running Windows Server 2008 R2 with the DFS Namespace service installed.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix. To avoid a restart, stop the DFS Namespace service before you install this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Dfsn-serverservice-ppdlic.xrm-msNot Applicable3,02116-Jul-201011:04Not Applicable


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  ( ) Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_77b6080d8dd55edb9f26ebc38011ba6f_31bf3856ad364e35_6.1.7600.20756_none_577c4a01914d5f81.manifest
File versionNot Applicable
File size710
Date (UTC)16-Jul-2010
Time (UTC)19:57
PlatformNot Applicable
File nameAmd64_microsoft-windows-dfsn-serverservice_31bf3856ad364e35_6.1.7600.20756_none_4bad449776a867d0.manifest
File versionNot Applicable
File size48,622
Date (UTC)16-Jul-2010
Time (UTC)11:42
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,096
Date (UTC)16-Jul-2010
Time (UTC)19:57
PlatformNot Applicable

  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2285823
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support