RPC over HTTP Problems

By Ray Gun ·
I am trying to setup RPC over HTTP.

I have configured the FE server and the BE server as specified in the microsoft documents for our network.

The BE server is not a GC.

The FE server has certificates installed, and OWA works fine. The RPC Site is setup for Basic Authentication only.

Test clients are setup for Basic Authentication.

When Outlook is started it requests a UN and PW and then fails to connect.

Outlook diag shows that its trying to connect to RPC but it never succeeds.

RPCdump from the Windows 2003 Res Kit does not show the Information store listening on port 6001, nor does it show the DS Referal or proxy server listening on port 6002 and 6004 respectively. I suspect this is the cause of why outlook is not connecting, but I have no idea how to fix it nor can I find any documentation on how to force these protocol settings to listen.

We also temporarily opened the firewall up completely to eliminate it as a source. Same problem.

Any ideas anyone?

This conversation is currently closed to new comments.

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

All Answers

Collapse -

RPC over HTTP Problems Fixed - mostly

by Ray Gun In reply to RPC over HTTP Problems

System Attendant on the FE server was down. Valid ports entry in registry was empty.
Started System Attendant and the valid ports populated in seconds.
As soon as the valid ports reg entry was populated RPC over HTTP started working, mostly. The only problem we are still having is when running outlook.exe /rpcdiag it reports that it cannot connect to the directory. We can send and receive email, but that lack of directory connectivity is bugging me.

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

Related Discussions

Related Forums