Outlook to Exchange vi RPC over HTTP: I'm stuck.

[jkellington]

Well, after much research and configuration time spent, I'm still no closer to getting my Outlook 2003 client to talk to Exchange 2003 via RPC over HTTP.

Here's a brief breakdown of what I have going

Stand-alone Exch2K3 on Win2K3Sp1, dedicated server in a Widnows 2003 Forest running in Windows 2003 native mode. 2 DCs (neither of them is the Exch server).

My Exchange server has been configured under the "How to Deploy RPC over HTTP for the First Time on Exchange Server 2003 SP1, No Front-End Server" scenario located here:

http://www.microsoft.com/technet/pr...03d-64c2-470f-9561-6de9003effe4.mspx?mfr=true

I am using SSL with a valid certificate installed on the Exchange Server, and I have set it up to use NTLM authentication only. However, when I open Outlook, I get prompted for my username and password, which shouldn't happen if NTLM is working properly as far as I understand.

If I switch to Basic authentication, it prompts me again for credentials (which is correct, by my understanding). However, when I enter the credentials, it brings up Outlook, but according to the connection status window fromthe Outlook system tray icon, I'm connected via TCP/IP, and it shows two failures to connect in the Req/Fail column. If I attempt to reconnect, 2 more failures are added to the total.

I'm assuming that because I can connect to the SSL site in my IE browser and because I get prompted for credentials that the RPC and HTTP(s) portions are working, and what I am experiencing is an authentication issue.

Can anyone provide any insight into this situation? Any help would be greatly appreciated. If I haven't provided some piece of info you need, let me know and I'll provide it to the best of my ability.

Thanks,
Jason

 

[Zelandakh]

Check OWA works without a cert problem.

Then review

http://www.gillott.co.uk/nick/RPCoverHTTP.pdf

http://www.msexchange.me.uk/rpchttpsproblems.htm

See if they help.

 

[jkellington]

OWA works fine, I can browse to

https://name.domain.local/rpc/rpcproxy.dll

and I get the blank page with the SSl 'yellow lock' like I should. Unfortunately, neither of the two links provide any moer than I already know or have tried.

Any other ideas?

 

[jkellington]

I'm thinking that my problem may be communciation between my exchange box and the two DCs/GC server. I read somewhere that I should be able to telnet to the GC on port 6004, and I can't do that. I understand that there may be a registry entry that needs to be changed, but any instructions on this have been unclear on exactly which type of configuration it needs to happen under (As stated before, I have a stand-alone Exchange Server on a Windows 2003 native forest with 2 separate DCs) Also, I've never been able to clarify whether the registry change happens on the DCs/GC or the Exchange box. Would anyone like to clarify this for me?

Thanks,
Jason

 

[pgordemer]

You will need to tell the DC to use 6004 and to make some regedits to tell Exchange where they are.

This article is one of the best I have seen to do the setup and it works.

http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm

Phil Gordemer
ARH Associates

 

[jkellington]

So, on what machines do I make the "ncacn_http:6004" registry addition?

 

[jkellington]

Also, do I need to include my GCs in the ValidPorts keystring on the Exchange box?

 

[Zelandakh]

The Exchange server gets the ncacn_http and the validports entries.