Question

Locked

DCOM using RPC over HTTP

By ian.page ·
I am trying to use RPC over HTTP to connect a DCOM client on XP SP2 to a 2k3
SP2 server. If I only select the Tunneling TCP/IP protocol, the client always
fails with 800706ba, The RPC server is unavailable, and the event viewer
message "DCOM was unable to communicate with the computer xxxxxx using any of
the configured protocols". If the Connection-oriented TCP/IP protocol is
selected as second priority, then the connection is made using this and the
server is activated successfully.

When only Tunneling TCP/IP is enabled, there is not even an initial
connection made to port 80 on the server. If I configure Outlook 2003 on the
client machine to use RPC over HTTP to connect to the Exchange server via the
same proxy server, then I see connection being made to port 80 with the
expected

RPC_IN_DATA /rpc/rpcproxy.dll?xxxxxx:6002 HTTP/1.1
Accept: application/rpc
User-Agent: MSRPC

Are there any configuration changes that need to be made to get DCOM to make
the RPC call over HTTP?

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Share your knowledge
Back to Networks Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums