RPC over HTTP Proxy

Dan

unread,

Aug 28, 2003, 2:56:32 PM8/28/03

to

I cant seem to get this working....
Installed RPC over HTTP PROXY on the host running Exchange 2k3
Installed the update to Win XP
Outlook 2k3 RTM on client
Configured for RPC over HTTP
Block in router between host and client
Packit dumps on the client show that the connection is working but still
requires some connection via port 135 on the server.
The server log indicate that the connection is reciving responces of 200.xx
as apposed to 4001 or 500 returns.
I am stumped.
Help?
--
Dan

Marc Nivens [MSFT]

unread,

Aug 29, 2003, 6:06:31 AM8/29/03

to

If a netmon shows that Outlook is trying to hit the endpoint mapper, it
means that the HTTPS connection has failed and it is defaulting to TCP. A
few things to check:

- Make sure you have the RPC\RPC Proxy key set on the RPC Proxy Server
- Make sure you have a certificate assigned to the web site hosting the
/rpc virtual directory
- Make sure the name on the certificate matches the FQDN that you're using
on the Outlook side
- Make sure that the issuer of the certificate is in your local Trust list

You can test the cert problems by hitting OWA on the RPC Proxy server. If
you get any certificate warnings, you will need to clear these up for
RPC/HTTP to work.

--
Marc Nivens
Enterprise Messaging Support

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Dan

unread,

Aug 30, 2003, 2:58:39 AM8/30/03

to

I am using etherreal, and I will check all of this for accracy.
Can anybody point me to a white paper on this???? or any docs?

"Marc Nivens [MSFT]" <ma...@online.microsoft.com> wrote in message
news:PXbGyUhb...@cpmsftngxa06.phx.gbl...

Dan

unread,

Aug 31, 2003, 2:28:59 AM8/31/03

to

OK I was able to get the cert for the FQDN and was able to connect without
error from IE.
When I try from outlook it fails.
IIS log indicate that it sent two 401 errors then a 200 series
However the connection never worked. I get an error that outlook was not
able to open a window.
One note, I have 135 (UDp,TCP) blocked in both directions in front of the
client.
If one of the MVP or other informed persons would like to work with me I
would appresiate it. However I would want to take it off the NNTP server as
some of the information might be sensitive..
drpet...@es.net
--
Dan

"Marc Nivens [MSFT]" <ma...@online.microsoft.com> wrote in message
news:PXbGyUhb...@cpmsftngxa06.phx.gbl...

Dan

unread,

Aug 31, 2003, 2:19:46 PM8/31/03

to

I would like to add that the logs show that the connection was made then the
server tried to talk back to the client on a destination address of 135,
this is where it failed.
--
dan

"Dan" <drpetersonat3gems.com> wrote in message
news:Oi6urk4b...@TK2MSFTNGP10.phx.gbl...

Ivan

unread,

Sep 4, 2003, 8:19:36 PM9/4/03

to

What do you mean by RPC\RPC?

>.
>

Dan

unread,

Sep 10, 2003, 2:18:43 PM9/10/03

to

Ivan,
That is a good question. Now I wonder what the means as well
This tread seems to have dried up.

--
Dan

"Ivan" <iv...@stentor.com> wrote in message
news:249701c37343$637c00e0$a401...@phx.gbl...