I am beginning to go out of my mind over this one. We have been running Exchange with an RPC over HTTPS scenario for over 2 years, and after patching the servers and firewall over the weekend, it has now stopped working and I have no idea why.
My deployment scenario is as follows:
I have a clustered Exchange Server 2003 configured as a backend RPC over HTTP server (call it mail). On the same network are 3 separate domain controllers, one of which is GC server (call it GC). In our firewall DMZ I have a server with IIS and Exchange Server 2003 configured as a Frontend RPC over HTTP server (call it web).
Now as I said the only thing that has changed was we patched everything up over the weekend to the latest MS patches. And the firewall which is a watchguard was upgraded graded to version 10 of the firmware.
So web is our RPC Proxy server. And I have checked all the settings on it the RPC virtual directory is correctly configured and when tested responds in the correct way (prompts for credentials 3 times and then reports 401.3 error on the ACL)
The firewall ports are still open correctly between the front end and back end server.
The only difference I can see in the clients is that when prompting for credentials it used to say please enter username and password for web, now it says please enter user name and password for mail.
Running an outlook.exe /rpcdiag on an external outlook client, shows the connection attempting to be made to mail via HTTPS then it drops without connecting. I do see Directory connection attempts to GC also, but these never seem to work either.
I really don't know what to do at this point because it seems everything I try doesn't change anything. I have even removed the RPC over HTTP proxy on web and redeployed to no avail.
Start Free Trial
