RE: RPC-HTTP Setup Questions/Problems

  • From: "Simon Butler" <simon@xxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 28 Feb 2006 18:25:30 -0000

As far as I am concerned - RPC over HTTP REQUIRES SSL. Any other tests
without SSL are null and void. Therefore I would enable SSL and then
start again. 

You don't need those additional ports open on your firewall - the only
port that is required is 443 - that is the whole point of this feature. 


Simon Butler
MCP, MCSA, MVP:Exchange
Amset IT Solutions Ltd.

e: simon@xxxxxxxxxxxx

----Original Message-----
From: Mike [mailto:mjin23@xxxxxxxxx] 
Sent: 28 February 2006 18:11
To: [ExchangeList]
Subject: [exchangelist] RPC-HTTP Setup Questions/Problems


Here's my current setup. 

I have a FE/BE Exchange 2003 SP2 with a separate DC/GC server in the 

I've followed the RPC-HTTP using KB from Microsoft and I've setup the 
RPC setup on the System manager to designate the FE/BE structure.  I
haven't enabled SSL yet because I want to test the basic functionality
the RPC/HTTP Outlook before I enable SSL.

I've opened up the necessary ports on the firewall.  (The RPC Proxy is 
sitting behind the firewall)  So I opened up ports 6001, 6002, 6004 
along with the 80/443 for the Proxy server.

On the Outlook client, I've unchecked the "Connect using SSL only" box. 
 I hit OK and OK and when I click on the "Check Name" box, I get the 
Connecting to my BE server with a username and password box.  I put in 
my username and password (both FQDN name and email address) and it does 
not authenticate. 

Here is what I'm seeing on the IIS log on my FE box. 

2006-02-28 17:20:55 W3SVC1 RPC_IN_DATA /rpc/rpcproxy.dll 80 - MSRPC 401 2 5 
2006-02-28 17:20:55 W3SVC1 RPC_OUT_DATA /rpc/rpcproxy.dll 80 - MSRPC 401 2 64 
2006-02-28 17:24:04 W3SVC1 RPC_IN_DATA /rpc/rpcproxy.dll 80 - MSRPC 401 2 5 
2006-02-28 17:24:04 W3SVC1 RPC_OUT_DATA /rpc/rpcproxy.dll 80 - MSRPC 401 2 64 

Any help would be appreciated.  Thanks!


List Archives:
Exchange Newsletters: 
Visit for more information about our other sites:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to info@xxxxxxxxxxxxxx

Other related posts: