Article ID: 899148 - View products that this article applies to.
Remote Procedure Call-based operations may fail if certain firewall and VPN products deny network requests. This denial occurs if the network requests come from Microsoft Windows Server 2003 Service Pack 1-based or Windows Vista-based computers. These network requests may fail on computers where you apply Windows Server 2003 Service Pack 1 (SP1) to a Windows Server 2003-based computer or your OEM or retail installation media includes SP1 updates. The following products may deny these network requests:
This issue occurs because Windows Server 2003 SP1 or Windows Vista add support for some new transfer syntaxes to the RPC implementation. These new transfer syntaxes are known as "multiple transfer syntax negotiation." They help 32-bit and 64-bit computers handle larger workloads. Additionally, they frequently help 32-bit and 64-bit computers work faster.
Specifically, firewalls and VPN products that do permit more than one presentation context to be present in a bound RPC protocol data unit (PDU) may cause either of the following symptoms:
To resolve this issue, if RPC-based operations on Windows Server 2003 SP1-based or Windows Vista-based computers fail across a VPN or a firewall immediately after you install Windows Server 2003 SP1 or Windows Vista, contact your firewall or VPN vendor to see if an updated version of their RPC filter is available. If RPC-based operations are being blocked by filters on Microsoft Internet Security and Acceleration Server (ISA) 2000, or ISA Server 2004 Standard Edition computers, see Microsoft Knowledge base article:
887222If RPC-based operations are blocked by filters on Check Point Software products, see Check Point Software SecureKnowledge article SK30784, or visit the following Checkpoint Software Web site:
(https://support.microsoft.com/kb/887222/ )The ISA Server RPC filter blocks RPC traffic after Windows Server 2003 Service Pack 1 is installed on a computer that is running ISA Server 2004 or ISA Server 2000
To work around this issue, use either of the following methods.
Method 1You can disable RPC filters on firewalls and VPN products if the network requirements make this possible.
Method 2Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
If you need RPC-based operations to function immediately and you cannot update firewalls and VPNs in a timely manner, install the hotfix that is described in this section and then follow these steps.
Important Windows Vista does not require a hotfix. However, you must follow these steps to modify the registry on Windows Vista-based computers.
Windows Server 2003 Service Pack 1A 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 this specific problem. 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=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. The 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.
Date Version Size File name Platform ---------------------------------------------------------- 05-03-2005 5.2.3790.2436 642,048 Rpcrt4.dll x86 05-03-2005 5.2.3790.2436 1,714,688 Rpcrt4.dll x64 05-03-2005 5.2.3790.2436 2,462,208 Rpcrt4.dll IA-64
Windows Server 2003 Service Pack 2Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
This problem was corrected in Windows Server 2003 Service Pack 2. For more information about Windows Server 2003 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
889100After you apply Windows Server 2003 SP2, you must follow these steps to modify the registry:
(https://support.microsoft.com/kb/889100/ )How to obtain the latest service pack for Windows Server 2003
When this problem is present, Microsoft Outlook clients cannot connect to the Exchange server. Therefore, administrators should evaluate whether RPC filter definitions in network infrastructure devices are compatible with the Windows Server 2003 SP1 or Windows Vista RPC traffic. An administrator should do this evaluation before deployment of firewall/VPN devices, Windows Server 2003 SP1, or Windows Vista in production environments where such network devices are deployed.
Evaluation is especially appropriate where firewalls can filter RPC-based replication traffic between domain controllers. Filtration of RPC-based replication traffic between domain controllers can cause a long-term interruption of Active Directory replication.
Specifically, administrators should try to use monitoring software to make sure that all domain controllers in a forest perform incoming replication within a rolling tombstone lifetime number of days. By default, a rolling tombstone lifetime number of days is 60 days. Domain controllers that cannot perform incoming replication of knowledge of each unique delete within the previous tombstone lifetime number of days will forever be inconsistent for those changes until an administrator intervenes.
Events in the Directory Service event log that indicate that Active Directory replication is failing on Windows Server 2003-based domain controllers include the following:
repadmin /showrepl * /csv >showrepl.csvAdministrators can view the Showrepl.csv file in a program like Microsoft Excel that parses comma-separated text. A high priority task includes resolving replication failures on destination domain controllers that have failed incoming replication for the longest time.
Repadmin.exe is located in the Support\Tools\ Suptools.msi file on the Windows Server 2003 installation media.
For more information about how to remove lingering objects, click the following article number to view the article in the Microsoft Knowledge Base:
870695For more information about programs from Checkpoint Software Technologies, visit the following Checkpoint Software Technologies Web site:
(https://support.microsoft.com/kb/870695/ )Outdated Active Directory objects generate event ID 1988 in Windows Server 2003
http://www.checkpoint.comFor more information about ISA Server, visit the following Microsoft Web site:
http://www.microsoft.com/isaserver/default.mspxMicrosoft is not aware of any router or switches that perform program–level filtering that would interfere with RPC-based operations in Windows Server 2003 SP1 or in Windows Vista.
The following error message is typically displayed by components when RPC frames with multiple transfer syntaxes are rejected by a firewall or a VPN generates Windows 32 error 1727:
This generic error code has multiple root causes and does not uniquely identify the blocking of RPC frames from Windows Server 2003 SP1-based or Windows Vista-based computers.
The remote procedure call failed and did not execute
For information about the DCE RPC specification, visit the following Opengroup Web site:
http://www.opengroup.org/onlinepubs/009629399/toc.htmFor information about multiple transfer syntax support in the DCE RPC specification, visit the following Opengroup Web site:
http://www.opengroup.org/onlinepubs/009629399/chap12.htm#tagcjh_17_06_04_03The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
Article ID: 899148 - Last Review: February 13, 2008 - Revision: 11.3