Select the product you need help with
RODCs unnecessarily open many RPC connections to RWDCs on a computer that is running Windows Server 2008 or Windows Server 2008 R2Article ID: 976449 - View products that this article applies to. On This PageSYMPTOMSOn a Windows Server 2008-based or a Windows Server 2008 R2-based read-only domain controller (RODC), the number of TCP connections keeps increasing. Finally, all TCP ports are used up. Note If you run the command netstat -b by using an administrator account, the results indicate that most connections are opened by the Lsass.exe process. The Foreign Address column indicates that most IP addresses are from one or more read/write domain controller (RWDC). CAUSEWhen an RODC that is running Windows Server 2008 or Windows Server 2008 R2 performs an Active Directory replication with an RWDC that is running Windows Server 2008 or Windows Server 2008 R2, the RODC tries to replicate user passwords. If a user account is not configured to cache a password on this RODC, its password is not replicated, and the RWDC returns an error code. However, the RWDC returns an incorrect error code. Because of the incorrect error code, the RODC unnecessarily starts a remote procedure call (RPC) connection. When the number of user accounts that are not configured to cache their passwords on the RODC increases, the number of unnecessary RPC connections also increases. After a while, all TCP ports are used up on the RODC. RESOLUTIONTo resolve the issue, apply the hotfix on all Windows Server 2008-based and Windows Server 2008 R2-based RWDCs in the current domain. After the hotfix is applied on the RWDCs, you have to restart the RODCs to clean up the connections and to prevent any new connection attempts. 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: http://support.microsoft.com/contactus/?ws=support 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, the computer must be running one of the following operating systems:
Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfix.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2008 file information notesImportant Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
For all supported x86-based versions of Windows Server 2008Collapse this table
For all supported x64-based versions of Windows Server 2008Collapse this table
Windows Server 2008 R2 file information notesImportant 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.
For all supported x64-based versions of Windows Server 2008 R2Collapse this table
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONFor more information, click the following
article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesAdditional file informationAdditional file information for Windows Server 2008Additional files for all supported x86-based versions of Windows Server 2008Collapse this table
Additional files for all supported x64-based versions of Windows Server 2008Collapse this table
Additional file information for Windows Server 2008 R2Additional files for all supported x64-based versions of Windows Server 2008 R2Collapse this table
PropertiesArticle ID: 976449 - Last Review: December 23, 2010 - Revision: 4.0 APPLIES TO
|
Back to the top
