RPC over HTTPS problem - Mail connects over HTTPS yet Directory only connects over TCP/IP
We are having a problem with our RPC over HTTPS setup. The symptom is that when we connect inside the LAN using the /rpcdiag switch, it connects, the Mail entries in the diag window show as being made over HTTPSbut the Directory entries are connected via TCP/IP. This of course makes it fail when you are outside the LAN. We have checked everything, we have an SSL certificate from a third party company and the test of the rpc directory does not give a certificate error, just the 401.3 error as expected. The setup is a single Exchange server and OWA is working properly. I am fresh out of ideas, anybody seen this specific behavior? TIA J.
January 8th, 2008 5:50pm

Same problem here. I've double checked everything. Someone can help us? Thanks Tiz
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2008 7:46pm

Same problem here as well. Have checked everything and torn it out and redid the RPC and directory still only connects using TCP/IP Hope someone has an answer!
February 16th, 2008 7:27pm

For Outlook Anywhere environment, your directory information should be proxied via NSPI through your mailbox server. Is port 6004 open on your back ends? Also, is your client profile set to always try to use RPC over HTTPS even if there is a fast network available?
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2008 7:38am

Is your back-end Exchange server in cluster configuration? I had the same problem in a cluster environment and it was a name resolution problem. When I tried to connect from the LAN, My Connection status showed me a TCP connection for the directory service to the CLUSTER NODE NAME that hosted the exchange service instead of a HTTPS connection to the CLUSTER NAME of Exchange. This because my DNS wrongly return me the node name instead of the cluster name of Exchange. Try to remove your DNS configuration and add only your RPC over HTTP server to your hosts file. If this solves the problem you can concentrate to name resolution problem (in my case it was not a problem because the connection should be from internet with a different DNS configuration that works correctly) If not try to recheck these registry key: http://technet.microsoft.com/en-us/library/aa998910(EXCHG.65).aspx http://technet.microsoft.com/en-us/library/bb124159(EXCHG.65).aspx
February 18th, 2008 12:43pm

Got it working. I discovered that any DC that holds the GC and that Exchange or Outlook can talk to has to be 20003 server. I had 2 other DC's that hold the GC that have 2000 server in the same site as the Exchange server and they were causing the directory connection so fail as they do not support RCP over HTTP. I simply removed the GC from them, rebooted and all is good. Hope this helps someone.
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2008 3:41pm

I discovered that any DC that holds the GC and that Exchange or Outlook can talk to has to be 20003 server. I had 2 other DC's that hold the GC that have 2000 server in the same site as the Exchange server and they were causing the directory connection so fail as they do not support RCP over HTTP. I simply removed the GC from them, rebooted and all is good. This was the solution for us as well. Does not seem to be prominently documented anywhere.
February 22nd, 2008 6:40pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics