RPC over HTTP still not working --- but close..

  • From: "Andrew English" <andrew@xxxxxxxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 2 Mar 2005 22:37:45 -0500

I want to mention a few things just in case their the reason for RPC
over HTTP not working. 

Originally I wanted ton conquer OWA with SSL, so I configured the
default site on Exchange to do it. And it works flawlessly. 

Then I wanted to conquer RPC over HTTP. First I must tell you that my
Exchange Server is one box only, it is also running in Native Mode, and
the AD has also been raised, both the forest and domain to 2003 Native

I have the proxy and gc configured as to what Microsoft and Tom says it
should; which are identical. The clients FQDN is a .local one, while
their owa web access is owa.clients-site.com. The Cert reflects the .com

I have installed the CA on my local machine thanks to Tom's handy work
with ISA Server 2004 and have tested again the clients OWA site which no
longer prompts me to accept the Cert before giving me the FBA page. 

When I look at ISA's logs when I am attempting to connect via Outlook
2003 SP1 and Windows XP Sp1 I see the following:

443  https  Allowed Connection  Publish OWA and RPC/HTTP Web.. 
(my IP)  anonymous (client username)  External

443  https  Failed Connection  Publish OWA and RPC/HTTP Web
(my IP)  anonymous (client username)  External

This also shows up for ports 6004, and 593 in the same format. I have
tried adding 6002 to the rpcproxy for argument sake and restarting the
WWW service afterwards, I have also tried Michael's suggestion to add
the owa.clients-site.com 6001 & 6004 to the rpcproxy and got the same
results. I have gone made sure my host file is setup correctly on my
test machine for the exchange.clients-site.local.. So I am open to

What happens after it goes through all this is I get a message saying
"your exchange server is unavailable". 


Other related posts:

  • » RPC over HTTP still not working --- but close..