rpc over http exchange2003 member server

[eric romero]

Hi all,

I cannot make RPC over HTTP work.

The problem: internet users using XP+SP1+outlook2003 cannot create the
outlook profile I got the following error while "check name".

"The connection to the microsoft exchnage server is unavailable Outlook must
be online or connected to complete this operation"

I have 1 W2003 domain 2DCs which are GCs also, 1 windows2003member server
running exchange2003.

This is what I have done,

1) Before SP1 I have installed the HTTP proxy component and I have made the
RPCPROXY registry
"ExchangeServer:6001;ExchangeServerFQDN:6001;ExchangeServer:6004;ExchangeSer
verFQDN:6004" mod suggested in "Exchange Server 2003 RPC over HTTP
deployment scenarios" May 28, 2004. ..rpc over http did not work..I hav
echange ExchangeServer for the name of my server.

2) After SP1 release , I have installed SP1 and selected the back-end
option.*

3) I can confirm that OWA works ok, using the same PC and same dial-up
connection which blocks port 135.

4) We do not use SSL.

5) as you see we do not use any front-end back-end email configuration.

all this time the only port open at the firewall for the email server is
port 80.

*the documentation states that I will receive a message saying that the
registry keys are going to be modified I have never received that message.

thx,

 

[neo [mvp outlook]]

Hi Eric,

Client requirements:
Windows XP (SP1) + patch mentioned in KB 331320
Outlook 2003

Server:
Windows 2003 DC/GC
Windows 2003 + Exchange 2003 (any sp is fine)

RPC over HTTP/S does not require a front/back end solution. RPC/HTTPs works
fine for single server sites.


Now for the below...

1) I see you made the modifications to the RPC Proxy registry key on the
Exchange server. Did you remember to add the necessary NTDS registry value
to your DC/GC servers? (This is covered in the Exchange deployment paper.
I think it is page 180.)

2) I have SP1 installed here and my RPC-HTTP has the first radio button
selected. (Not part of an Exchange managed RPC topology.) I don't remember
this tab being available pre Exchange sp1. Have never changed it, so it
must be the default. (and yes, rpc/https is working here.)

3) cool... owa works, but it doesn't use rpc over https calls either.

4) This is a problem area. Microsoft doesn't recommend the use of rpc over
http for production environments, so the default configuration doesn't allow
the connection when SSL is missing.
http://support.microsoft.com/default.aspx?kbid=833003 covers some of this.

Since you are running a Windows 2003 network, do not forget that you can
establish an internal CA and issue your own certificates. This will help
you implement SSL. Just remember that each user's workstation must have a
copy of the signing CA in their trusted root certificate store. (Outlook
2003 will reject the RPC/HTTPs connection if it can't verify the certificate
back up the chain and not throw a single error message.)

5) Again, no sweat. RPC over HTTPs works great in a single server
environment. Microsoft just happens to recommend front/backend solutions
because most tend to implement 2 or more Exchange servers (e.g. OWA & RPC
over HTTPs tend to be the front ends to servers that are mailbox and/or
public folder servers.)

Hope this puts you back on track...
/neo