Symptoms
KB 2089874 and KB 2102154. Notes
Assume that you define a static TCP port on which the NTDS service listens and responds to incoming remote procedure calls (RPCs). In this situation, Active Directory replication may fail with an RPC issue. This issue may include all symptoms in-
For more information about restricting Active Directory replication traffic and client RPC traffic to a specific port, click the following article number to view the article in the Microsoft Knowledge Base:
224196 Restricting Active Directory replication traffic and client RPC traffic to a specific port
-
The NTDS interface is also known as the DRS interface. Using a static port lets the administrator constrain communication for an activity (such as Active Directory replication) to a known port. This lets firewalls be configured to allow traffic to only that port.
Cause
When the static port for the NTDS service is successfully registered with the endpoint mapper, a dynamic port is also registered. However, the static port is not always returned by the endpoint mapper as first priority. If a dynamic port is returned and is also blocked by the firewall, it may cause the issue that is described in the "Symptoms" section.
Resolution
To resolve this issue in Windows 8.1 or Windows Server 2012 R2, install update 2955164. For more information about update 2955164, click the following article number to view the article in the Microsoft Knowledge Base:
2955164 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: May 2014 To resolve this issue in Windows 7 or Windows Server 2008 R2, install the hotfix that is described in this article.
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 website:http://support.microsoft.com/contactus/?ws=supportNote 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.
Prerequisites
To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global 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
-
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.1.760
1.22xxxWindows 7 and Windows Server 2008 R2
SP1
LDR
-
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" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7 SP1
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Ntdsa.mof |
Not Applicable |
227,765 |
05-Nov-2010 |
01:54 |
Not Applicable |
Ntdsai.dll |
6.1.7601.22526 |
2,023,424 |
27-Nov-2013 |
02:01 |
x86 |
For all supported x64-based versions of Windows 7 SP1 and Windows Server 2008 R2 SP1
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
19,968 |
27-Nov-2013 |
04:05 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
58,486 |
27-Nov-2013 |
04:01 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
796,672 |
27-Nov-2013 |
03:54 |
Not Applicable |
Report.ad.xml |
Not Applicable |
25,550 |
27-Nov-2013 |
03:43 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
8,368 |
27-Nov-2013 |
04:03 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
24,064 |
27-Nov-2013 |
04:08 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
61,684 |
27-Nov-2013 |
04:03 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
880,640 |
27-Nov-2013 |
03:55 |
Not Applicable |
Report.ad.xml |
Not Applicable |
24,069 |
27-Nov-2013 |
03:44 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
7,695 |
27-Nov-2013 |
04:06 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
19,968 |
27-Nov-2013 |
02:30 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
54,286 |
27-Nov-2013 |
02:29 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
788,992 |
27-Nov-2013 |
02:29 |
Not Applicable |
Report.ad.xml |
Not Applicable |
22,929 |
27-Nov-2013 |
02:30 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
7,255 |
27-Nov-2013 |
02:30 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
23,552 |
27-Nov-2013 |
04:07 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
60,800 |
27-Nov-2013 |
04:02 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
879,616 |
27-Nov-2013 |
03:55 |
Not Applicable |
Report.ad.xml |
Not Applicable |
24,503 |
27-Nov-2013 |
03:43 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
8,031 |
27-Nov-2013 |
04:05 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
24,064 |
27-Nov-2013 |
04:07 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
61,502 |
27-Nov-2013 |
04:02 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
893,952 |
27-Nov-2013 |
03:55 |
Not Applicable |
Report.ad.xml |
Not Applicable |
24,821 |
27-Nov-2013 |
03:43 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
8,168 |
27-Nov-2013 |
04:05 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
19,456 |
27-Nov-2013 |
04:06 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
58,156 |
27-Nov-2013 |
04:01 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
839,680 |
27-Nov-2013 |
03:54 |
Not Applicable |
Report.ad.xml |
Not Applicable |
25,482 |
27-Nov-2013 |
03:43 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
8,284 |
27-Nov-2013 |
04:04 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
20,992 |
27-Nov-2013 |
04:06 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
58,590 |
27-Nov-2013 |
04:01 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
868,352 |
27-Nov-2013 |
03:54 |
Not Applicable |
Report.ad.xml |
Not Applicable |
24,090 |
27-Nov-2013 |
03:43 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
8,177 |
27-Nov-2013 |
04:04 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
12,800 |
27-Nov-2013 |
04:06 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
40,580 |
27-Nov-2013 |
04:01 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
562,176 |
27-Nov-2013 |
03:54 |
Not Applicable |
Report.ad.xml |
Not Applicable |
23,027 |
27-Nov-2013 |
03:44 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
8,891 |
27-Nov-2013 |
04:04 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
13,312 |
27-Nov-2013 |
04:07 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
40,034 |
27-Nov-2013 |
04:02 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
535,040 |
27-Nov-2013 |
03:55 |
Not Applicable |
Report.ad.xml |
Not Applicable |
23,790 |
27-Nov-2013 |
03:44 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
8,293 |
27-Nov-2013 |
04:05 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
22,528 |
27-Nov-2013 |
04:06 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
63,530 |
27-Nov-2013 |
04:01 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
849,408 |
27-Nov-2013 |
03:54 |
Not Applicable |
Report.ad.xml |
Not Applicable |
23,900 |
27-Nov-2013 |
03:43 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
7,839 |
27-Nov-2013 |
04:04 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
21,504 |
27-Nov-2013 |
04:06 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
58,990 |
27-Nov-2013 |
04:02 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
849,920 |
27-Nov-2013 |
03:54 |
Not Applicable |
Report.ad.xml |
Not Applicable |
24,779 |
27-Nov-2013 |
03:43 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
8,332 |
27-Nov-2013 |
04:04 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
22,016 |
27-Nov-2013 |
04:08 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
57,834 |
27-Nov-2013 |
04:03 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
843,264 |
27-Nov-2013 |
03:55 |
Not Applicable |
Report.ad.xml |
Not Applicable |
24,297 |
27-Nov-2013 |
03:44 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
7,821 |
27-Nov-2013 |
04:06 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
23,552 |
27-Nov-2013 |
04:06 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
60,310 |
27-Nov-2013 |
04:01 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
865,792 |
27-Nov-2013 |
03:54 |
Not Applicable |
Report.ad.xml |
Not Applicable |
24,922 |
27-Nov-2013 |
03:43 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
8,115 |
27-Nov-2013 |
04:04 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
20,992 |
27-Nov-2013 |
04:08 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
57,258 |
27-Nov-2013 |
04:03 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
823,296 |
27-Nov-2013 |
03:56 |
Not Applicable |
Report.ad.xml |
Not Applicable |
27,906 |
27-Nov-2013 |
03:44 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
10,526 |
27-Nov-2013 |
04:06 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
21,504 |
27-Nov-2013 |
04:07 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
59,230 |
27-Nov-2013 |
04:02 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
799,232 |
27-Nov-2013 |
03:55 |
Not Applicable |
Report.ad.xml |
Not Applicable |
24,062 |
27-Nov-2013 |
03:44 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
7,623 |
27-Nov-2013 |
04:05 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
18,944 |
27-Nov-2013 |
04:06 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
54,780 |
27-Nov-2013 |
04:01 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
790,528 |
27-Nov-2013 |
03:54 |
Not Applicable |
Report.ad.xml |
Not Applicable |
23,889 |
27-Nov-2013 |
03:43 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
7,635 |
27-Nov-2013 |
04:04 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
9,728 |
27-Nov-2013 |
04:07 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
34,782 |
27-Nov-2013 |
04:02 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
438,272 |
27-Nov-2013 |
03:55 |
Not Applicable |
Report.ad.xml |
Not Applicable |
22,757 |
27-Nov-2013 |
03:44 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
7,024 |
27-Nov-2013 |
04:05 |
Not Applicable |
Ntdsbmsg.dll.mui |
6.1.7601.22526 |
9,728 |
27-Nov-2013 |
04:04 |
Not Applicable |
Ntdsctrs.ini |
Not Applicable |
36,464 |
27-Nov-2013 |
04:00 |
Not Applicable |
Ntdsmsg.dll.mui |
6.1.7601.22526 |
446,464 |
27-Nov-2013 |
03:53 |
Not Applicable |
Report.ad.xml |
Not Applicable |
22,781 |
27-Nov-2013 |
03:43 |
Not Applicable |
Rules.ad.xml |
Not Applicable |
7,059 |
27-Nov-2013 |
04:02 |
Not Applicable |
Ntdsa.mof |
Not Applicable |
227,765 |
05-Nov-2010 |
01:54 |
Not Applicable |
Ntdsai.dll |
6.1.7601.22526 |
2,749,952 |
27-Nov-2013 |
02:32 |
x64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
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