RPC over HTTP Outlook 2007 Exchange 2003

I use Outlook 2007 with Exchange 2003 SP2, and yesterday RPC over HTTP just stopped working all of a sudden. I started getting Security Alerts for autodiscover, pointing to myregisteredsite.com. So I changed our DNS so there were no wildcards thinking this would help. I even removed the split-DNS our server was using just to see if it made a difference, but it hasn't helped. The server is SBS Standard with SP2.

I've run the Internet Connection Wizard several times, removed and replaced the Outlook profile, removed and replaced the cert, which is a 3rd party cert from GoDaddy, and I get as far as /rpcdiag showing the Directory connecting fine with HTTPS but the Mail or Public Folders not showing up at all.

All of my registry entries are correct. As I mentioned, everything was working fine for almost a year, then it just stopped this past Monday. Nothing on the server has changed, nothing on my Outlook has changed - just whammo.

On the test site, I'm assuming I'm using the Outlook 2003 test even though I'm using Outlook 2007 because I'm not using Exchange 2007? It fails pinging 6001, even though the registry entries are correct under the Rpcproxy key.

Just an addendum - When I do the same launch of Outlook 2007 from my home PC, with the exact same setup, it prompts for a username and password, meaning it's actually contacting the Virtual folders in IIS I'm assuming? Once I log in, it just shows as Disconnected down at the bottom. Again, RPCDIAG shows 4 or 5 connections to Directory as HTTPS, but no Mail or Public Folder connections.

Upon testing within the environment with RPCDIAG, all connections are made but show up as TCP/IP and not HTTPS.

Then I tried using www.testexchangeconnectivity.com and it comes back saying it failed on the certificate, HOWEVER, the failure is not on the cert name, but on the trust, and comes back with the error "The certificate chain has errors, Chain status = PartialChain ".

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Ok, after further testing, I went to look at the IIS logs and noticed that all of the RPC_IN_DATA and RPC_OUT_DATA showed successful connections, ending with the 200 0 0 on ports 593, 6001, and 6002. However, there are no 6004 connections anywhere to be found. So I went and double checked the port assignments in the registry, and unfortunately they are all set correctly for the server netbios name, the server fqdn, and the outside proxy fqdn.

I am also getting the same error from testexchangeconnectivity, and am also using Go-Daddy certificate. I get no errors from the certificates as well. Autodiscover stopped working. Manual configure does work though for Outlook Anywhere.
This seems to be an issue with GoDaddy certificates, but for the life of me I cannot find out why.

Featured Post

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Recipients >> Sha…

In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Mail Flow…