Note As of May 2005, the previous list includes the products that
may deny these network requests. However, the previous list may not include
every possible product that performs application-level filtering and that can
deny network requests. Hardware and software from other manufacturers that
perform application-level filtering may also deny remote procedure call (RPC)
requests from computers that are running Windows Server 2003 Service Pack 1
(SP1) or Windows Vista.

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:

Method 1

You can disable RPC filters on firewalls and VPN products if the
network requirements make this possible.

Method 2

Important 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:

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.

Click Start, click Run,
type regedit, and then click
OK

Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Rpc

Click the Edit menu, point to
New, and then click DWORD Value.

Type

Server2003NegotiateDisable

as the name of the new DWORD Value

Right-click

Server2003NegotiateDisable

,
and then click Modify.

In the Value Data box, type
1, and then click OK.

Note This setting disables the bind time negotation and multiple
transfer syntax negotiation.

Quit Registry Editor. Restart the computer.

After the firewalls and VPN devices are compatible with RPC
on the computer, set the value for the

Server2003NegotiateDisable

entry in the registry to 0. Then, restart the
computer.

Windows Server 2003 Service Pack 1

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 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:

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.
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.

Windows Server 2003 Service Pack 2

Important 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:

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:

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.

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:

1862: “the local DC has not recently received replication
information from a number of domain controllers” (intersite)

1864: “the local DC has not recently received replication
information from a number of domain controllers” (intrasite)

2042: “it has been too long since this machine last
replicated with the named source” (TSL # of days)

If administrators do not have a monitoring solution, they can
use enterprise administrator credentials to run the following Windows Server
2003 REPADMIN command daily:

repadmin /showrepl * /csv >showrepl.csv

Administrators 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:

The 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.