RPC over HTTP

[testman1]

I am setting up RPC over HTTP for the first time. To test it, I have tried it over the LOCAL LAN, but the Outlook 2003 client will only connect TCP/IP not HTTPS. I have verified that my SSL certificate works, and that the configuration is ok. I have made registery changes with no luck.
I have read many technical articles about how to do it, but it still doesn't work.

Any help would be appriciated.

 

[ShackDaddy]

You don't want to test it on the local LAN. If you HAVE to test it on the local LAN, you need to set up a forward lookup zone in your internal DNS that matches the external DNS, but uses internal IP addresses. So, for example, if you are trying to get a connection to owa.yourdomain.com and your internal domain is 'yourdomain.local' then you want to set up a new forward lookup zone for yourdomain.com on the internal DNS server and create an A-record for "owa" and give it the internal IP of the server.

If you've already done that and are still having trouble, please post the actual errors you are getting.

Dave Shackelford
MCSE, CCNA, Microsoft MVP: Exchange
Shackelford Consulting

 

[testman1]

I didn't try the exact test from the LAN that you stated.

From the WAN using outlook.exe /rpcdiag I get the box to enter my username and password. It accepts them, but I get a error message "The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action."

FYI:

https://mydomain.com/exchange

works from the Internet.
If I connect to https:mydomain.com/rpc my username and passwords fail and I get an http Error of 401.3. In some articles, it says this is ok and in other articles they are looking for a different code.

From the Exchange Server 2003, I have tried to use rpcping. I was able to ping successfully with rpcping -t ncacn_tcp_ip, but I was NOT successful with rpcping –t rpc_http. There are a lot of switches with rpcping. I may not have been using it correctly.

I have literally read 20 articles on how to configure rpc over http. This is a bear.

Thanks for your help.