RPC over HTTP problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am running an exchange 2003 server in a mixed mode environment (both
Exchange and domain environments) and one of the DCs is a windows 2003 DC. I
follow the instructions from Microsoft web site to set it up and could not
make it to work as it connects only to TCP/IP instead of HTTPS. The only
things I could think of probably because I am running in a mixed mode windows
2000 ? or is it because I havenot converted my Exchange 2003 to native mode?

Regards
Steven
 
Are all of your DC/GCs Windows 2003? (This is a must.)

Are you using a certificate from an internal CA or 3rd party to secure the
web/rpc proxy server? If internal, does the client machine have a copy of
the CA's certificate installed? (Outlook 2003 will need verify the
authenticity of the web certificate all the way back to the signing CA.)

Last but not least, the client workstation must be Windows XP (SP1) + patch
Q331320, Windows XP (SP2), or Windows 2003.

/neo

ps - being in mixed mode for domain/exchange is fine.
 
I have 2 DCs, one of them is a windows 2000 DC which I had taken off from
becoming a GC and another one is a windows 2003 DC and DC. Is if a problem,
do I have to upgrade my windows 2000 DC to a windows 2003 DC?.
My client is already an Windows XP (SP1) + patch Q331320.

Thanks, Sopheat.
 
As far as I know, all DC/GCs must be Windows 2003 server and properly
configured to accept rpc proxy connection to NTDS. You might be able to get
around this by going into ESM and specifying exactly which DC/GCs Exchange
will refer clients to rather than letting Exchange auto-detect environment.
Just remember that if you take away the auto detection ability, any changes
to the environment will require someone to visit ESM and make changes.

Outside of that, you still didn't mention if you are using an Internal or
Public CA to secure the IIS web server hosting the RPC Proxy virtual folder.
While the connectivity might be called RPC over HTTP, it *must* make the
connection over HTTPS and be able to verify the web certificate back to the
signing CA.
 
Hi Neil,

It is now working internally and I am using the internal certificate which I
installed on my Exchange server. It does not work from the Internet though. I
have installed the certificate on the my Exchange 2003 server and exported
and then imported to my ISA 2000 server and then I trusted it then
web-published it. When connect externally it just could not make a connection.

Thanks
 
Back
Top