XWEB: OWA Uses Client RPC Binding Order to Establish Communication (235683)
The information in this article applies to:
- Microsoft Outlook Web Access 5.5
- Microsoft Outlook Web Access 5.5 SP 1
- Microsoft Outlook Web Access 5.5 SP 2
- Microsoft Outlook Web Access 5.5 SP 3
- Microsoft Exchange Server 5.5
This article was previously published under Q235683 SUMMARY
Microsoft Exchange Server uses remote procedure call (RPC) built into Microsoft Windows NT to establish
connections among the Exchange Server processes, such as connections between Exchange Server message transfer agents (MTAs), and to connect Exchange clients and Exchange Server computers in the network. Exchange Server can use RPC over named pipes, TCP/IP, NetBIOS, and IPX/SPX. When Exchange Server uses RPC, it proceeds through the list of the protocols above and establishes RPC binding. The preference order of the transports is defined by the "RPC BINDING ORDER," which by default is Local RPC, TCP/IP, SPX, named pipes, and then NetBIOS, in order of preference.
Outlook Web Access (OWA) uses the Outlook/Exchange client RPC binding order to establish RPC communications to the Exchange Server, the same way that an Exchange or Outlook client does.
RPC_Binding_Order is located in the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider
Modification Type: | Minor | Last Reviewed: | 4/28/2005 |
---|
Keywords: | kbinfo KB235683 |
---|
|