RE: Questions about RPC over HTTP

  • From: "Michael B. Smith" <michael@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 4 Mar 2005 11:29:00 -0500

once you get to the point where http://<servername>/rpc is throwing the
correct error, it's generally easy after that.
I'm not sure how that works unless your SSL key is for your internal
server name.
I agree - it's time for you to call PSS.
We all have our opinions and we all know how it works in our environment
- you need someone to walk through your environment, step by step.


From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx] 
Sent: Friday, March 04, 2005 11:25 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Questions about RPC over HTTP



I will re-add the owa. (SSL external FQDN) back to the validports for
rpcproxy. But first I want to throw the monkey wrench into the pot. If I
setup a local client to use RPC over HTTP and check the connection by
running "outlook /rpcdiag" the client is able to connect to the exchange
server without any problems using HTTPS. Which if I am correct suggests
to me that its working on the inside but just not on the outside??






From: Michael B. Smith [mailto:michael@xxxxxxxxxx] 
Sent: Friday, March 04, 2005 11:01 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Questions about RPC over HTTP

This doesn't include your SSL/external FQDN: 



Have you looked at Tom's website? I know next to
nothing about ISA or setting anything up through ISA.



List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx 

Other related posts: